Stronghold current-request native replay: setup stable, preset hover rejected

The sole original native replay passed the current-request publication barrier and reached the complete Custom Game setup. The candidate and three further input-free 256-step captures passed both complete-layout recognizers. A timely fresh personal review permitted preset routing. The first concrete failure was command17: moving over preset1 enlarged its hover artwork, so the unchanged physical driver rejected route changed before press. No preset press, native Start, world or visible gameplay followed.

This uses the tested helpers from current-review publication, commit 7e58e56fa, and the unchanged split-gesture predecessor. Evidence is in scratch/runs/20261104-stronghold-current-request-native/. Only this note is committed. There are no production edits, rebuilds, source archives, module/media copies, second Chrome, reloads, retries, forced callbacks, guest register/argument writes, repaint or fault clearing.

Before Chrome, the assigned fork executed successfully with no Chrome or replay driver. All2415 retained runtime pins passed. Actual wrapper setup, CJS/ESM/Puppeteer imports, HTTP isolation,98 page/12 Worker cache entries, and a32-file recursive helper/JSON/preload closure passed. Lazy route/title/layout imports and required non-module companions were included. Original runtime source remains 1188e9bf57ef35bd3363fb88b7ca0da442ce696d; canonical WASM remains cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee, companion 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3. Media paths and hashes are recorded without transferring media.

The three replacement review helpers match their tested SHA identities exactly: review_publication.py cc468020cc9c4b1d00f8a1cb4ea50c6d2e23c562d71078dc8fa02d27b267843f, review-request.py 88f69c3692604cb5ede16e2a8805ef1947eafba38ad020e4341091f332d3e478, and ack-review.py 5fa3686da584cfe9f527fafccadfa425ab4571955cedde44f6406b0879d249d7. The staged state machine, operator, wrapper, physical route and supporting helpers are unchanged. The authorized small runtime_io.py binds allocation to this assignment and bx_3gvchvrj. Release JSON retains the wrapper's required predecessor compatibility label and adds the actual assignment, fork, expiry and deadlines.

Chrome11899 recorded identity at12:20:22.405Z; its original absolute deadline was12:26:09.658Z. Five completed and timely inspected input-free commands reached10240 steps. Command5 separately reviewed the title and resulting main menu around balanced Enter. Command6 separately reviewed main menu and Crusader hover before its balanced press. Command7 reviewed original ChooseType and installed the single route driver. Command8 separately reviewed ChooseType. Command9 fetched its current hover request, received personal VIEW and capture-bound ACK, and completed successfully. Command10 executed the balanced Custom Game press. The publication failure from the predecessor did not recur.

Commands11–12 reached the complete setup candidate after512 cumulative arrival steps. Commands13–15 supplied three further256-step stability captures, with768 cumulative stability and1600 total route steps. Command16's fresh personally viewed setup at12288 navigation steps completed in time and advanced to preset permission. One immutable evidence queue and physical driver were retained throughout; no counters or deadlines were reset.

Command17 reviewed the fresh setup again, then emitted only the preset1 move to client(84,733). Its capture at12352 navigation steps showed the enlarged red1 button. The original whole-rectangle setup SHA changed from f156657d1308d2e3af2b59793a1184cb4c12619cfc1aebec2acd195914135e0c to cee938f27d78daa6d2260bad96d60852ac92d4289730a46cc4a21d3697b4c0ac. Offline reproduction confirms both exact complete-layout recognizers reject that hover; all11678 changed pixels lie within x26–147/y678–796, the preset1 artwork. The physical driver requires its original scene label after moving and rejected before requesting hover review or pressing. This is a concrete run-helper recognition limitation. The mandated unchanged physical route was preserved; the next repair needs an explicitly recognized preset-hover state and its separate fresh review, with rejection controls for foreign/stale layouts, before another authorized replay.

Command17's rejected reply was inspected before its original deadline. A subsequent fetch saw the terminal cursor and rejected without granting permission. Quit18 was submitted NEXT after the command lock released. Chrome had already closed normally at12:25:09.278Z, exit0,286873ms after identity; quit18 was consequently unprocessed and its missing reply timed out. The terminal latch never reopened. The first concrete reason remains in reply17 and the immutable first-failure log; the existing operator's later quit-timeout cursor text is retained as produced.

actual-result.json verifies193 complete64-step ACKs/12352 steps,1052 matching served pins, six paused-before-start Worker preloads, nine personal reviews, timely inspected successes0–16, no preset press/Start and drained final input. hover-diagnosis.test.cjs reproduces the exact recognition failure using recovered PNGs. Original PNG bytes are retained; decoded full RGBA is saved without generating derived PNGs. No guest raw-pixel dump or gameplay screenshot was produced or claimed.

All319 immutable closed artifacts/32548370 bytes were recovered and fully SHA verified, with unique driver log, review receipts, terminal latch and all19 submitted mailbox files recovered separately before12:27. Final2415 pins pass, Chrome/driver are absent and HTTP37313 is closed. Both predecessor seals remain unchanged:234 files/170021 bytes and323 files/14995403 bytes. Exact checkout Git SHA, relevant binary diff, owned new-file patches and an artifact seal preserve provenance.

Custody returned at12:27 with bx_3gvchvrj RUNNING (API idle, health ok, hydrated), expiry 2026-11-04T12:56:17.203Z. The coordinator accepted custody and subsequently reported a normal stop request at12:28:44.725Z, operation stop_d88ed11aec659d89; completion is not independently claimed here. This worker performed no lifecycle action or further runtime work and stops after this note's commit and one strict pull/push publication.