Balanced original Stronghold menu transport: title-release prerequisite stopped runtime

The run-specific menu transport now derives native (304,144) internally from the actual viewport and executes separate physical move, press and release with per-event complete guest ACKs and input drainage. Actual DOM-handler testing also exposed and repaired a transport mismatch in the published route adapter: a DOM press emits WM_NCHITTEST followed by WM_LBUTTONDOWN, whereas its earlier modeled queueMouseInput fixture emitted only the down event. Both repairs pass focused offline tests using production renderer handlers and host input imports. The one actual browser did not reach the main menu, ChooseType, Start, world or an ordinary gameplay interaction.

Evidence is scratch/runs/20261104-stronghold-balanced-menu-route/. Only this note is committed; ignored small helpers are recoverable from owned-new-helpers.patch. No production code changed and no full build was required. This is a failed runtime attempt with a concrete input prerequisite, not gameplay success.

Source, preparation and transport repair

Preparation Git SHA was b07e2e08c3446cc8e244da6f72c2acbde1a63a38, including the requested prior notes. Retained runtime source remains 1188e9bf57ef35bd3363fb88b7ca0da442ce696d, with the predecessor constructor repair and 2,415 runtime pins referenced in place. source-reference.json, empty relevant current relevant-source.patch, individual staged helper hashes and owned new-file patches record provenance. Git holds source history; no source archive, scratch/docs/test-binary tarball, module copy or repeated media copy was created.

Original EXE SHA-256 is 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f at the retained installed multiplayer-demo path. Canonical module is cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee, companion 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3. All retained pins matched before and after execution. Actual installed Puppeteer CommonJS and dynamic ESM imports, five pinned HTTP responses with COOP/COEP, constructor telemetry, bounded ACK/queue/capture/cleanup fixtures and small-stage installed hashes passed before Chrome. Runtime used Workers and original Canvas/DirectDraw presentation.

menu-driver.cjs uses the unchanged native geometry/projector/readiness checks and strict original mainToCrusader recognizer. It qualifies and personally reviews a fresh exact main-menu capture, recaptures before move, computes browser (337.3375,360.4433333333333) internally, then separately checks the actual owned event sequence and drains each physical operation. A separate fresh personal hover review precedes press; the strict unhovered recognizer is not relaxed to recognize hover pixels. Unknown output still rejects through unchanged assertTransition. The obsolete atomic-click mailbox action rejects. A failed owned press gets only its release, without further execution.

The small route-driver.cjs correction preserves the published adapter's controller, scene signatures, native route points, aggregate bounds, personal-review boundaries, immutable queue and handoff policy. Only its pending-event validation changes: down requires exactly ordered [132,513], same HWND, native coordinates, masks and packed lParam; the hit-test companion alone requires wParam zero. Missing, reordered, foreign or corrupted companions reject. Browser routeDispatch still owns the queue directly, without nested boundary.run. Separate unchanged NativeStartDriver and guardNativeCommands remain mandatory after strict Zephyr handoff. None of these route/Start paths was installed live.

bash scratch/runs/20261104-stronghold-balanced-menu-route/run-tests.sh is the final fail-fast focused suite. The changed actual browser-driver VM test passes 17 checks through its real mailbox, state, capture, personal-review and queue closures: menu gesture, single-attempt lock, both route gestures, handoff and separate unchanged Start construction/capture with zero Start calls. The production DOM renderer handlers and host check_input imports run; page responses, scene transitions and ACKs are modeled. The menu uses 256 modeled steps; both route gestures use 512 modeled steps, including actual button-hold/drain behavior. Eight route negatives cover missing/reordered/foreign/corrupt companions, bad ACK, missing telemetry and drainage exhaustion. Menu negatives include the actual retained-key-up prerequisite with zero mouse events. The published adapter's existing 203-check fixture suite, real constructor regression and unchanged strict native-start suite also pass. Earlier exploratory failures are retained; they are not final passing tests or live gameplay evidence.

One actual browser and first missing boundary

Chrome 38079 opened at 07:07:18.612Z and closed normally at 07:08:47.626Z, approximately 89 seconds, with deadline 07:22:18.611Z, below fifteen minutes and before 07:25Z. There was one registered selector/Launch and no reload/retry.

Personally reviewed actual captures:

After personally viewing that last picture, the operator submitted the guarded menu-crusader command. It was premature: the image itself did not qualify a menu. The driver rejected input not drained before capture recognition or any mouse operation, and only quit/recovery followed. No guessed click occurred. The operator should have stopped on the unexpected picture without submitting that command; the positive input prerequisite prevented it from advancing.

The recovered final state independently records one still-queued Enter WM_KEYUP, {type:"key",hwnd:0,wParam:13,msg:257,lParam:3223060481}, with active input null, last input null and mouse mask zero. Enter down and its WM_CHAR had drained by step 10304. The following complete 64-step ACK advanced to 10368, but did not consume the release. Thus the first missing boundary is drained title release plus a fresh recognized main menu, earlier than the previous attempt's Crusader activation. ACK completion is not input drainage. The evidence does not establish why the guest had not yet polled that release or whether further bounded execution would have completed the transition. No additional execution was attempted to find out.

Neither prior click discrepancy is individually proved causal, and this attempt cannot validate the repaired mouse transport live because it issued zero in-game mouse events. ChooseType (543,292), preset 1 (67,491), strict Zephyr, separate scenario review, native Start (718,569), world review and meaningful ordinary gameplay remain unexecuted.

Recovery and handoff

verification.json passes 14 sequential replies, the expected prerequisite rejection at command 12, 162 complete 64-step per-guest ACKs / 10,368 actual steps, all 1,005 served-file pin receipts, zero in-game mouse transport events, the retained pending title release and normal browser cleanup. This verifies the failed attempt, not gameplay.

The immutable closed snapshot recovered 208 logical files / 6,196,838 bytes, with full SHA-256 verification and reuse of already recovered identical captures. recovery-closed-verified.json maps every logical file to its unique local recovery path; recovered/closed/snapshot-manifest.json SHA-256 is ce1ced2baf257da2827f3d564cd00fe84fae23ded00f89e4a263ec27e56d827c. The first recovery request raced snapshot publication; the later request recovered the completed immutable snapshot without runtime activity.

Actual exec at 07:10Z confirms Chrome 38079 and driver 38063 absent, private HTTP 35051 closed and all 2,415 pins unchanged. Assigned bx_87cqdcba remains RUNNING / API-idle, healthy and hydrated, expiry 2026-11-04T07:43:10.325Z. Shutdown ownership returns to the coordinator. No allocation/resume/stop/delete, source-box access, second browser, guest writes/calls, forced scene, synthetic gameplay, Deathmatch fallback, local heavy runtime, other game, subworker/successor or deployment occurred.

Next technical requirement is explicit bounded drainage after each title key half, followed by a fresh recognized and personally reviewed main menu before installing the repaired menu transport. That is a diagnosis, not an additional runtime authorization or successor task. This single-task worker stops with gameplay unfulfilled and the closed evidence recovered before 07:30Z.