Stronghold scene20 advances naturally; strict preset anchor rejects the result

The original request is not stuck rendering ChooseType. The sole browser reproduced callback ID2/request20 and current20 with ChooseType still visible at10880. After 256 additional input-free steps, the actual image at11136 showed the three numbered preset buttons, “Not available in the demo”, Human/Lord Crusader, Deathmatch Game, gold fields and the player list. The unchanged exact preset recognizer returned unknown, and the first-failure guard immediately closed Chrome. No preset, Zephyr, Start or world input followed.

Evidence: scratch/runs/20261104-stronghold-scene20-natural-render/. Predecessor: original callback/request proof, commit 43054cef4e9eff118dadcb09156d826f3f25681e. No production file changed. No production defect or repair is claimed.

What the observation establishes

I personally viewed both closed captures. At10880, route-native-boundary-5.png SHA cfe61da3bbb4988710024fb2b6cb6a99c73cc60544c35f564710556858f589c9 still shows the original ChooseType/Custom Game hover. At11136, route-native-boundary-6.png SHA d5988593af17dbc13e0a4ed3cb2c79460d991fbef7830e162d7d1834edc22bba shows the preset selection layout described above. Four complete64-step ACKs separate these captures; no input occurred between them. The exact latency within that256-step interval was not sampled.

The natural result differs from the retained village custom-skirmish.png reference. Both preset recognition regions were compared byte-for-byte in preset-region-comparison.json:

Thus the earlier stop was before a subsequent natural rendered update; this run's stop is an exact-image readiness mismatch. The evidence does not establish whether these extra panels are a stable normal layout, an initialization stage, or a rendering difference. It does not establish a fade mechanism, missing repaint, broken initialization, or a production rendering defect. The recognizer was not relaxed after failure. Rendered selection controls are visible, but strict preset readiness, Zephyr and world progress remain unqualified.

Controller and verification

Small run-owned helpers reuse the tested predecessor controller/observer. The only observation extension accepts the already recognized Custom Game hover as a bounded waiting image after the original balanced press. It performs at most12 groups of four64-step ACKs, checking readiness, exact input telemetry and held controls around each step and capturing after each group. The existing4096-step physical-route budget remains. The first non-hover result must satisfy the unchanged preset recognizer; any other image or existing guard failure is terminal. No raw post-route step command, forced call, guest write, scene substitution, repaint, reload or second browser was used.

Before Chrome, the 27 observer controls,20 game-output freshness controls,12 route controls, original instruction audit, predecessor route/native negatives and launch sequencing passed. Actual retained normal WASM/original EXE argument3-negative and ID2/request20-positive fixtures ran in the actual Worker/broker. All 2415 retained pins, exact driver/transitive helper hashes, actual CommonJS/dynamic ESM/Puppeteer imports, syntax, 98 page/12 Worker cache graph and five pinned HTTP/isolation responses passed. The detached driver survived the external60-second execution limit. Three additional modeled natural-observation cases passed: delayed transition, persistent-hover exhaustion and unexpected-image termination. Those additional tests finished after launch, before the Custom Game press; they are not reported as pre-Chrome controls. Their initial test expectation failure and corrected final result are retained.

actual-evidence-check.json validates 174 complete ACKs /11136 steps, 1052 served-pin matches, six paused-before-start Worker preloads, four live armed instances throughout recording,18 observer reports, two explicitly recorded pre-recording retirements, zero observer errors/drops, and eight rejecting proof mutations. Callback absence remains unqualified. Slot0 again records the original native (543,292) down/callbackID2/branch/request20/release order. Its last boundaries retain current/requested20/20. No additional trace range or observer write was introduced.

Personal-review corrections are retained: the2048 loading image has artwork and a bottom progress bar, not a centered dialog; the Crusader-hover description reads “Skirmish with enemy lords…”, not linked games. Review scene identities were correct. The menu command was placed in the sequential mailbox before the title command's final reply; execution remained serialized and both the title-result/main-menu and menu-hover reviews completed before the guarded mouse press. No parallel guest commands executed.

Cleanup, provenance and custody

Sole Chrome 19167 ran from10:07:54Z to 10:10:48.659Z, exit0. First failure was first unexpected natural scene: unknown at 10:10:48.409Z. All controls are balanced; final queue empty, active/last input null, mask0. Driver/Chrome are absent, actual private HTTP 35421 is closed, and all2415 retained pins remain unchanged. The inherited recovery helper also checked the predecessor port33127; actual-http-closed.json separately checks the actual port.

All 252 immutable closed files /18,499,589 bytes were recovered and SHA-verified by10:11:04Z, with unique actual-Worker result, exact tested driver and driver log recovered separately. Exact Git SHA, relevant binary diff, owned-new-file patches and artifact hashes preserve provenance. Git is the source archive; no source archive, source-tree copy, media copy or module copy was created. Original EXE SHA remains 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f; runtime source commit remains 1188e9bf57ef35bd3363fb88b7ca0da442ce696d, normal WASM cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee. Existing module/media path references are retained separately. Bounded original scene-manager disassembly is supporting static context only, not live execution proof.

This note alone is committed; no production-code/full-build claim applies. Publication outcome is recorded separately. The next evidence needed is qualification of this actual preset layout and its initialization stability before any preset input; the mandatory first-failure closure prevents continuing this browser.

Assigned bx_g5fcu9qz is left RUNNING /API-idle, healthy and hydrated, expiry 2026-11-04T10:31:12.262Z. The coordinator owns shutdown and receives custody. No lifecycle/allocation/sourcebox/local-heavy-browser/subworker/successor/HeroesII/deployment action occurred. This single assignment stops with natural rendering proved and the remaining readiness gap preserved.