Stronghold callback observation stopped at title freshness

The sole original run stopped before sending Enter. Custom Game guest dispatch, callback ID and scene request remain unobserved. The first runtime failure was Error: stale title review at 2026-11-04T09:31:13.572Z, frozen step 10240. The next command was quit; there was no settling, retry, reload or second browser. Production and all route/Start guards remain unchanged. No production defect or causal repair is claimed.

Evidence: scratch/runs/20261104-stronghold-native-callback-observation/. Predecessors: consumed press cause, 8f11decb4855b9bf714bcc9bb7d0903199506474, and hover recognizer, 7dbf713d61ae53d78bdfded14806e402d47c7860.

Actual terminal boundary

I personally viewed the five bounded startup captures, including original castle loading artwork, a dark Firefly Studios fade at8192, and the original Enter Your Title / Lord Crusader / Start Game screen at10240. The title driver requested review of PNG 575e7d124364a83a5d9e8b9b2e7c22af92391602baeafaff785293a01cfac62d. The review was acknowledged at09:31:12.319Z. Its unchanged full-PNG freshness check then rejected the fresh capture before keyboard down.

I personally viewed recovered title-boundary-1.png. Pixel comparison with title-boundary-0.png finds 57 changed pixels, all within inclusive rectangle [1161,883,1168,890], the host taskbar clock changing from10:30 to10:31. All other pixels and the frozen tick state are identical; both images satisfy the original title recognizer. This establishes why this attempt failed freshness, not a game input/callback defect. No clock masking, crop substitution, stale-image admission or guard relaxation was applied.

title-clock.test.cjs replays these exact captures through the unchanged title helper. The clock-only change rejects before key/step; an identical-image control passes freshness and reaches a deliberately failing input stub; a wrong review rejects. State and input in this regression are modeled, not another runtime run. An initial test-loader Buffer/Uint8Array cloning error was corrected before this regression passed.

actual-evidence-check.json verifies 160 complete ACKs / 10240 steps, 1003 matching served-pin records, four paused-before-start Worker preloads, exactly one runtime failure, and mailbox sequence five bounded observations → title-enter → quit. Final input queue is empty, active/last input null and physical mask0. No Enter event or route gesture was delivered. Crusader304144, strict ChooseType, native543292 move/hover/press, preset67491, Zephyr, nativeStart718569 and gameplay were never reached.

Observer integration and preflight

The retained observer.cjs and observer.test.cjs were read without editing. Own observer-preload.js embeds the same observer function and wraps existing WebAssembly.instantiate before the actual guest Worker instantiates its module. It preserves the original import object and broker functions, binds the exports getter to the returned same instance, and resolves translation through actual self.memUtils.g2w, never the WAT translator. The preload is injected while each Worker is waiting for the debugger, before resume. No production source is replaced.

Own driver integration would start the observer only after the existing personally reviewed exact Custom Game hover. It uses existing diagnostic exports set_api_log(1) and set_trace_esp(1,0x430e10,0x430f15), adds synchronous pre/post ACK state samples, and exports bounded instance reports including slot/thread, synchronous stack/MSG/state, errors, drops and explicit coverage limits. No wide upstream trace, guest writes, forced calls or forced scene is part of live observation. The unchanged route helper owns the single balanced press and its terminal behavior.

Before Chrome, launch.py ran the helper/observer suite and complete runtime preflight using subprocess.run(..., check=True). The actual retained WASM was instantiated in the actual retained Node guest Worker with its actual production broker. The original EXE was loaded and unmodified original callback instructions executed with explicit offline fixture registers/stack: argument3 produced the callback row/EAX3 and no ID2 branch; argument2 produced the ID2 branch and the original manager store of requested scene20. These fixture writes/calls belong only to the isolated preflight, not the original browser/game route. recovered-extra/actual-worker-result.json contains both cases, SHA-256 d1b6663de794a8ae12505fa3536c6b3ab87cad03f52a926b3a04965c02276d8d. This qualifies synchronous observation in that tested Worker/instance, not original Custom Game execution or complete live coverage.

The retained observer suite passed wrong pin/base/signature, unmapped read, overflow, immutable report, full memory nonmutation, detach and hover/press separation controls, actual broker forwarding/quiet-log behavior, and real host dequeue without guest-proof controls. Captured-image hover, postpress, successor, route DOM, integer-coordinate, launch sequencing and 16 native Start negatives passed. Own copied navigation/route/integer helpers also passed their focused tests. All production guards and helpers used for the live title route remained unchanged.

At09:29:25Z the actual preflight verified 2415 original runtime pins at source Git 1188e9bf57ef35bd3363fb88b7ca0da442ce696d, exact actual helper dependencies, 98 page / 12 Worker cache graph, CommonJS/dynamic ESM/Puppeteer imports and syntax, and five full-SHA HTTP responses with isolation headers. Only small run-specific inputs were staged. Existing EXE/media/modules were referenced in place by path/SHA; see predecessor retained-module-media-path-sha.json and this run's dependency/pin records. The original EXE SHA remains 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f; normal/compat module SHAs remain cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee / 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3.

Coverage limit: the live run failed before activation. There are no live observer rows or exported per-instance reports; live trace arming, errors/drop counters and all-instance callback coverage therefore remain unqualified. Preload receipts alone do not establish those facts. No absent-callback inference is warranted.

Recovery, publication and custody

Sole detached execution began 09:29:25.765Z. Chrome 14520 closed normally, exit0, at 09:31:27.016Z, well within15 minutes and the09:52 hard close. Driver 14504 is absent; private HTTP 38455 is closed. All2415 retained pins still match. An immediate recovery attempt preceded publication of the closed snapshot and returned ENOENT; the subsequent immutable snapshot recovery passed full SHA for 200 logical files / 6,119,804 bytes, manifest SHA f052d85f760cb93819b0d1bfe153996624ad4c83c5e68e9f5a5e1d1d0625e0b1, before09:57. Already reviewed identical captures are referenced rather than duplicated. Extra unique preflight result and driver log were recovered separately.

exact-git-sha.txt, relevant binary diff, own new-file patches and artifact manifest preserve provenance. Git is the source archive; no source-tree/archive, scratch/docs/test-binary tarball, repeated media or module copy was made. Only this report is committed; production code is unchanged, so no production full-build gate applies.

Assigned bx_7c5nxxz7 remains RUNNING, API state idle, healthy/hydrated, expiry 2026-11-04T10:02:53.948Z. Ownership returns to the coordinator, who owns shutdown. No lifecycle/allocation/sourcebox action, local heavy browser/game, subagent/worker/successor, HeroesII or deployment occurred. Next unresolved work requires separate authorization: obtain the original Custom Game dispatch/callback/request records after the unchanged title freshness and subsequent route guards actually pass. This single assignment stops here.