Stronghold game-output freshness repaired; observer arming is the next boundary
The demonstrated title freshness false failure is repaired and tested. The sole original run passed title Enter and Crusader, then stopped at the personally reviewed Custom Game hover before its press. Observer arming failed on a closed Worker CDP session at 2026-11-04T09:43:10.227Z. Chrome closed normally at 09:43:15.136Z. Original Custom Game dispatch/callback ID/scene request, preset, Start and world progress remain unobserved. No production defect is established.
Evidence: scratch/runs/20261104-stronghold-game-area-freshness/. Predecessors: native callback observation, 7a87781d16c4677b22c25a06445669c9e3c181ed; consumed press cause; hover recognizer.
Repair and captured regression
Own small title-driver.cjs, navigation.cjs and route-driver.cjs use freshness.cjs with the existing measured presentation inspector. They compare every RGBA pixel of the entire owned output rectangle, measured as x10,y194,width860,height668 in this qualified layout. This includes all game pixels, borders and letterboxing. There is no mask or excluded region inside the game. Geometry, viewport, frozen tick, HWND/window ownership, page session/time origin, renderer/host/canvas object identity, source version, canvases and Worker instance records are part of the exact identity. Unsupported geometry or occlusion rejects. Personal review still requires the exact full-PNG SHA and scene, and full screenshots remain preserved.
freshness.test.cjs replays the predecessor's exact title-boundary0/1 PNGs, whose only differences are the documented57 host-clock pixels outside the game. Both the clock-only change and identical-image control pass freshness and reach a deliberately failing offline keyboard stub. Wrong review rejects before input. Mutated game pixels at every output corner, an interior point and the formerly tested850850 point reject, as do changed tick, HWND, host, renderer, canvas, Worker ID, session and geometry. 20 controls pass. State/input in these regressions are modeled. The unchanged full screenshots are the regression inputs, not substituted cropped images.
The own route integration also passes 12 captured-image/production DOM transport modes, with modeled ACKs: normal route, wrong title/label/description/map, missing hover, game-pixel freshness change, foreign queue/input, incomplete ACK, old y291 coordinate and absent personal review. Initial ChooseType remains strict. Native coordinates, balanced press/release, queue ownership, ACK/drain and readiness guards remain intact. Native Start implementation is unchanged.
Preflight before the sole browser
The detached launcher completed the checked offline suite and actual runtime preflight before Chrome. The retained actual WASM/original EXE executed callback argument3 negative and argument2/requested-scene20 positive fixtures in the actual Worker/broker, with observation installed before instantiation, same-instance exports and pure JS translation. These explicit offline fixture calls are separate from the original browser route; no forced guest call/write/scene occurred in that route. Recovered actual-worker-result.json SHA is d1b6663de794a8ae12505fa3536c6b3ab87cad03f52a926b3a04965c02276d8d.
Preflight verified 2415 retained runtime pins, actual transitive helper imports, own title/route dependencies, 98 page /12 Worker cache graph, CommonJS/dynamic ESM/Puppeteer imports, syntax and five SHA-pinned HTTP responses with isolation headers. Existing observer negatives, original instruction audit, captured postpress controls, successor/DOM/integer tests, launch sequencing and16 native Start negatives passed. launch-preflight.log, complete-helper-closure.json and dependency records preserve the exact inputs. The detached execution survived beyond60 seconds and closed normally; no second browser or reload occurred. Only small run inputs were staged; media/modules were referenced in place by path/SHA.
Actual route and first failure
I personally viewed the loading captures, Firefly logo, original title, main menu, Crusader hover, strict ChooseType and exact Custom Game hover. Two initial loading descriptions were imprecise; append-only corrections identify the actual file-loading dialogs. Balanced Enter at10240 reached main menu at10368. Native 304144 Crusader movement/press reached strict ChooseType at10560. The integer CSS move queued native 543292, ACKed/drained, and reached the exact Custom Game hover at 10624.
Reviewed full hover PNG SHA: 571962c557a2a00561b597d7cef3b34f7a1e3ad7d631eeb5018b9b768d6f24d0. It visibly shows Choose type of Crusader game, left map, right towers, Custom Game and Customize your own Crusader game. The review receipt triggered observer arming before the fresh pre-press capture. That operation raised TargetCloseError: Protocol error (Runtime.evaluate): Session closed. Most likely the worker has been closed. No native543292 down/up followed. Quit was the next and final mailbox command, about five seconds later.
actual-evidence-check.json verifies 166 complete ACKs /10624 steps, 1032 matching served-pin records, six paused-before-start Worker preload receipts, one runtime failure, the exact mailbox sequence and final empty queue/null active/null last/zero mask. Final-state records show two closed Worker sessions. The arming loop could have armed earlier instances before failing; it did not publish a complete report or mark the recording window active. Live callback coverage, per-instance errors/drops and pre/post ACK observations are unqualified. No absent-callback inference is made. The live hover freshness recapture/press was never reached, nor were preset67491, Zephyr, Start718569 or ordinary gameplay.
Offline repair after the terminal failure
The actual browser-tested driver is preserved separately in recovered-extra/successor-driver.cjs (SHA fd499b73370d9f436f5caa18a7839b18ccafa7b7f4482a7fe77a9e2d615b1d73). Own revised observer-control.cjs records Target.detachedFromTarget, retires those sessions from live control, and retains their identity, active-window status and missing-final-report limitation. It persists partial reports/errors before rejecting; an empty/missing instance, failed live session, read error, dropped row or retirement during the recording window remains terminal. Successful arming requires every live instance. Reports explicitly leave callback-absence qualification false. Existing observer imports, broker forwarding, signatures, same-instance binding, pure JS translator and smallest trace 0x430e10..0x430f15 remain unchanged.
The revised driver wires that control and closes on its first command failure. 22 offline CDP controls pass, including a closed predecessor session retired before arming, live retirement during recording, unknown closed-session failure, exception, missing instance, read error, drop and empty coverage. These are modeled CDP sessions, not a second runtime validation. No browser was reopened; the repair's actual-game validation remains outstanding. Production code is unchanged, so the production full-build gate does not apply.
Recovery, provenance and custody
The immutable closed snapshot recovery SHA-verifies 228 logical files /14,541,191 bytes, completed by09:43:54, before09:57. Already reviewed identical captures are referenced rather than recopied. Unique actual-Worker results, log and the exact tested driver were recovered separately. Chrome 21513 exited0; driver and Chrome are absent, and private HTTP 37501 is closed. No box lifecycle operation occurred.
exact-git-sha.txt, relevant binary diff, owned new-file patches, tested/repaired helper versions and artifact manifest preserve recovery through Git plus small inputs; no source snapshots/archives, scratch/docs/test-binary tarballs or repeated media/module copies were made. Retained source Git is 1188e9bf57ef35bd3363fb88b7ca0da442ce696d. Original EXE SHA remains 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f; normal/compat WASM SHAs remain cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee / 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3. Full path/SHA records remain in predecessor retained-module-media-path-sha.json and retained runtime pins. Only this note is committed; ignored run-helper patches contain the tested repairs.
Assigned bx_7c5nxxz7 remains RUNNING /API-idle, healthy and hydrated, expiry 2026-11-04T10:02:53.948Z. Custody returns to the coordinator, who owns shutdown. No lifecycle/allocation/sourcebox/subworker/successor/local heavy browser/HeroesII/deployment action occurred. Next work requires separate authorization: validate the repaired live-session observer at the original reviewed Custom Game boundary, then obtain actual dispatch/callback/request evidence before any guarded preset/Start/world progress. This single assignment stops here.