Stronghold resolved-binding original attempt, 2026-11-04

The sole fresh attempt proved actual page compilation, original Module transfer, and owning slot 0/thread 1/endpoint 1 identity, then continued through personally reviewed title, main menu and Custom Game activation. Preset activation remains unproved: the first natural arrival capture showed “Not available in the demo”. The unchanged route rejected it and ended the attempt. No runtime retry occurred.

Evidence: scratch/runs/20261104-stronghold-resolved-binding-native/. Fresh box bx_7z5qca2h was healthy and fully hydrated at 16:19:22.691Z, before runtime preparation. Closed source bx_8kfdtfgw was never accessed or resumed. Runtime preparation verified all 2,415 inherited pins, retained the original source/modules/media, and staged only the published d2c0776b9 successor and small run-specific inputs. The exact local source reference was 3fa8bdb170ab10b6b5ac46181d38bbf8940bd995; the runtime pin manifest also records inherited identities. Concurrent local D3D changes were not staged.

Normal module SHA-256: 4417305d70322467441aef51e888b0fe66451d9c60da0c734eeb23f5a22c0a6b. Compatibility module SHA-256: 07fb4e75d05177271097dcd67d84e2629272b50073074bbdea8825ce10b4ed34. Media remained at the inherited test/binaries/candidates/stronghold-crusader-demo/installed/App_Executables/Stronghold Crusader multiplayer demo.exe, SHA-256 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f. Git SHA, relevant binary diff and the new note patch are the source archive; no source tree archive or module/media copies were created.

The focused published successor test passed after exact SHA-verified restoration of its compressed 3,908-byte observer input. Actual runtime composition checked all 30 retained helpers, Puppeteer CJS/ESM, executable Chrome 151.0.7922.108, and 164 HTTP body pins including both modules. Those responses had no-store, isolation and appropriate MIME headers. All 1,058 successful live served-file pins matched. Five nonfatal 404 responses are retained separately. No code was changed, so no new full build was required.

Chrome PID 19357 launched once at 16:19:53Z, with original absolute deadline 16:25:53.586Z (360 seconds). Actual first-script preload completed in script 3, context 1, at 16:19:54.788Z. The owning target was 0063557820E1E607FD34EAC64AD80938, original session 33F78DAB6B879D6C906E3298EB9BFF68.

At frozen step 0, the read-only binding receipt verified the single compiled normal Module and its original init transfer. The raw constructor URL lib/guest-worker.js?v=dev resolves against the actual page http://127.0.0.1:37677/index.html?debug&candidates&frozen to the exact CDP Worker URL, preserving origin/path/query. The Worker's receipt and instantiation both identify slot 0; pre-instantiation installation had no entry error. Only after those binding checks did identity exports report thread 1, slot 0, endpoint 1. No guest-state read, input or trace preceded this qualification. The actual preset attachment begin was not exercised because preset was never reached; this receipt does not claim that later gate passed.

Commands 0–4 each completed 2,048 observation steps. I viewed their captures: loading art, two media-loading dialogs, a black transition, and Enter Your Title. Command 5 separately published, fetched, personally viewed and acknowledged fresh title and main-menu captures, then returned success after the original balanced Enter pair. Command 6 separately reviewed main menu and Crusader hover before its balanced press. Commands 7–9 reviewed ChooseType twice and the fresh Custom Game hover. Command 10 completed the original balanced Custom Game press, returning arrival at 10,880 navigation steps/320 route steps.

Command 11 advanced the first 256 natural arrival steps. At 16:23:15.509Z, the unchanged recognizer reported demo-selection-unavailable at 11,136 navigation steps/576 route steps and rejected it. I personally viewed the terminal route-native-boundary-7.png: shield and swords, “Not available in the demo”, three numbered preset circles, and absent complete setup controls. The cause of this different natural scene remains unknown. It is not evidence of completed setup or preset application. A follow-on arrival submission was locally rejected by the terminal operator latch before upload; no command 12 was sent. No preset press, Start, install-native, settings/gameplay gesture, passive trace, recognizer relaxation or restart followed.

All 174 transport ACKs completed exactly 64 steps and consecutive totals through 11,136. Final input queue, active/last input and mouse mask were empty/zero. Native callback/application history is unknown; the passive observer never started and cannot establish absence of native activity.

Recovery verified 266 unique files/19,097,477 bytes by full SHA-256 and size; the second inventory matched all 265 stable files. Chrome closed normally at 16:23:15.618Z with exit 0. Its PID was absent and HTTP 37677/CDP 41073 were closed. Custody returned at 16:23:47Z with the assigned box RUNNING (API state=idle), healthy and hydrated, expiry 16:57:37.368Z. No subsequent box access occurred; coordinator exclusively owns snapshot and shutdown.

Next work is offline diagnosis of the recovered unavailable scene and exact input/transition evidence before any separately authorized fresh attempt. The closed original must never resume. No implementation repair is justified by a scene label alone, and this worker makes no activation or gameplay claim.