Stronghold main-menu recognition and one original onward attempt, 2026-11-04

The demonstrated original main-menu mismatch is repaired against its sealed original reference. Evidence: scratch/runs/20261104-stronghold-menu-recognition-onward/.

The original 220×30 patch at (190,344) differs by29 of6600 pixels and464 maximum-channel error in the actual prior menu capture. Every pixel contributes to the comparison: limits40 changed pixels/650 error, with every20×15 tile limited to20 pixels/350 error. No shifts, rescaling, excluded pixels or new accepted capture hashes. The full original reference SHA-256 is checked first. The original title limits remain500/6000 and50×50 tile100/1800.

The original title helper and original menu driver share the repaired classifier. A composed loader retains the original per-file SHA checks across30 helpers and substitutes only the sealed navigation classifier source. Historical evidence, menu gestures, presentation identity, whole-game freshness, personal review, Worker target/nonce, original slot0/endpoint1/thread1 and complete64-step ACK guards are retained. Following menu/preset classifiers were inspected offline; no demonstrated defect justified changing them. Preset/Start remain unavailable.

The local contract is renewed for THIS assignment only, actual hostname, boot, PID/start ticks, run, candidate/module manifest and fresh random nonce. Absolute Chrome cutoff19:00Z, cleanup19:03Z, finite360s browser/60s bootstrap/40s command and full360+180 start reserve remain. No remote allocation/API/SSH or guest writes. Box ID/state/expiry NA; coordinator owns future boxes/shutdown.

Offline real-capture tests accept the original and actual menu while shifted, cropped, wrong-scene, stale tick/pixels, bad review and foreign Worker captures reject before original input. Concentrated tile mutation rejects. The original title tests, local contract guards and both-module owning fixtures pass; locked full build passes. Source recovery uses Git SHA and relevant binary diff only.

The one fresh attempt used NEW shared main 1b35ea11b4eb7d49e9c2cbf157abaabcf59c9b70 plus the recorded owned patches. Both existing module paths and hashes were retained, without copies:

Module SHA-256
normal 78a0b1d61b23428a1ae909d739440ae0de059bbbd84a69a2ad3e4c37471ad664
compatibility 99b579cd17b57f94145df92ae6d28110f24fc284d13a1b2c0ebe3596bd10a77f

Actual filesystem pins2428, independent full-body HTTP pins164 and all1038 runtime served-file pins passed. All1856 original media references match, including original EXE 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f. The inherited sole local flock was acquired after GL's17:51:56 normal release; no Chrome overlap. The original observer preload was installed before first script. Compile/send evidence shows the actual pinned module and original slot0.

I personally viewed all14 fresh PNGs, including each requested review before dependent input. Original input-free startup reached the title at7424. Original balanced Enter256/258/257 reached the main menu7552; repaired title and menu recognition accepted. Original Crusader move at native(304,144), separate fresh hover review, and balanced down/up reached7744 with drained controls.

The first new blocker is the unchanged following classifier: the screenshot visibly shows Choose type of Crusader game, while its exact420×35 patch at (235,340) returns unknown. Original expected crop SHA-256 1d414967a82a43f7f0b9a5228e1ca6f3c73595f2e3159e6436941e21c09b3fed; actual 5bcbf6bb25cc02fa535caa4207a273671d60f18f698c6ea34a9f4c4408a0b602. The sealed original reference differs by20 pixels/1041 maximum-channel error; geometry is identical. The original driver stopped with first unexpected menu state: unknown; expected crusader-type. No retry, route installation, Custom Game gesture, callback arming, preset, Start or guest writes followed. The new blocker is preserved as a rejecting regression. No visible gameplay is claimed. Earlier offline static inspection retained the following exact classifiers; historical fixture recognition does not establish that a fresh renderer will produce the same pixels.

121 consecutive complete64-step ACKs reach7744. The original slot0/endpoint1/ thread1 owning observer, balanced543,292 Custom Game gesture, exact historical shell RGBA gate, first plus at most3 further256-step input-free samples, and navigation16384/route4096/arrival3072 limits remain, and were not reached.

Chrome850713 exited0 normally at17:56:16Z; Node850639 is gone, HTTP34483 refused a fresh connection, and the inherited flock was free. The board released the local heavy slot at17:56:38Z for MDK. The driver's old boxLeftRunning field is legacy; explicit local closure proof records box ID/state/expiry NA. The closed Chrome profile was removed. The driver's duplicate evidence snapshot was compared byte for byte against canonical browser files; its manifest was preserved and only verified duplicates removed. No source archive or media/ module copies were made.

Focused final tests pass with the fresh actual title/menu positives and fresh ChooseType rejection. Shift/crop/wrong-scene and stale/foreign negatives still reject through the original drivers before input. The local contract suite rejects30 bad contracts plus an actual foreign child process, and checks the composed entry. Both-module executable owning fixtures, historical shell regressions and locked full build pass.

Next: diagnose the demonstrated following ChooseType recognition mismatch offline before any separately authorized fresh attempt. This finite assignment ends after the tested main-menu repair and this first onward blocker.