Stronghold first-title native attempt
The sole fresh attempt eliminated the predecessor's unnecessary observation after title first appeared. It reached the original Custom Game setup, then completed all three required stability captures. The original 360-second browser timer closed before setup review. Preset selection, native Start, world and gameplay remain unverified.
This uses the exact tested hover split from
preset hover recognition,
2b5b3b07e, and consumed-request publication repair from
hover-reviewed native world,
943dce309. The immediately preceding
successor attempt,
11acfe967, supplies the runnable preparation and recovery recipe. Its sealed
inputs remain read-only. All fresh evidence is in
scratch/runs/20261104-stronghold-first-title-native-world/; only this note is
committed. No production source, renderer, module or media was changed.
Assigned box bx_bgtujwj8 became healthy and fully hydrated before any runtime
execution or transfer. Its expiry is 2026-11-04T14:22:06.665Z, guest cutoff
14:09Z, recovery deadline 14:14Z and coordinator stop checkpoint
14:18Z. Launch at13:47:54 left room for the full360-second browser interval
and recovery. The worker performed no lifecycle operation and returned custody
with the box RUNNING, API state idle, healthy and fully hydrated.
Preparation SHA-checked all36 dependencies, including explicit predecessor
sibling paths, then staged three allocation inputs: transport, release and
cache checker. Allocation and path guards were regenerated for this assignment.
All39 staged identities passed on the assigned box. The actual wrapper,
relative imports and required JSON, CJS/ESM Puppeteer, executable access,
98 page/12 Worker cache entries and five pinned HTTP isolation responses passed
without Chrome. All2415 original runtime pins passed before launch and after
closure: source 1188e9bf57ef35bd3363fb88b7ca0da442ce696d, canonical WASM
cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee, companion
580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3.
Original media was used at its existing pinned paths; no module/media copies
or source archives were created.
Fresh offline controls passed25 actual-driver cases,25 layout negatives, actual driver/wrapper/separate fetch/ACK transport,18 operator controls, six review, four transport, six split, nine bounded-route and three positive/ 48 negative retained layout controls. Actual wrapper setup, operator entry, exclusive locking and reply inspection also passed. The multi-review regression reproduced the old consumed-request return and passed with the exact repaired publication helper. Four additional negatives and all ten publication controls passed, including the original40-second timeout measured at40.142 seconds. These fixtures granted no live input permission.
Compressed historical fixture inputs initially caused missing-file failures before launch. Read-only gzip restoration into the owned run, with recorded SHA and coordinator roundtrip-manifest verification, resolved those prerequisites; compressed originals were retained. Two original historical RGBA files were also restored into this run against their recorded fullSHA and compressed identities. A Node test was initially invoked with Python and then corrected. No runtime helper repair resulted from these preparation errors. The tested runtime driver, exact full-rectangle and independent column recognizers, physical input guards and publication helper remained unchanged.
Chrome13342 recorded identity at 13:47:55.432Z, version
151.0.7922.108, with absolute deadline 13:53:54.557Z. Commands0–4 each
completed2048 observation steps with timely inspected success. Each screenshot
was personally viewed in a completed tool call before deciding the next command:
2048 showed loading art,4096 and6144 showed media loading,8192 showed Firefly,
and10240 showed Enter Your Title. The next command was title-enter;
there was no extra observation, reset or predecessor continuation.
Command5 fetched the current title request, received personal VIEW and separate ACK, executed balanced Enter, then independently fetched/reviewed/ACKed its new main-menu request. Its final success was inspected before its original deadline. Command6 likewise separately reviewed main menu and Crusader hover, then completed the balanced Crusader press and timely success. These are live two-review commands using the repaired publication helper, with unique request IDs under each unchanged command deadline.
Command7 personally reviewed original ChooseType and installed the single
route. Command8 separately reviewed ChooseType. Command9 emitted the original
Custom Game MOVE and separately fetched/reviewed/ACKed the actual hover.
Command10 executed the balanced Custom Game press, returning arrival with
320 route steps. Command11 advanced256 arrival steps to the retained earlier
layout; command12 reached exact setup at512 cumulative arrival steps.
Both results and their fresh captures were inspected. Commands13–15 each
completed256 further stability steps; each successful reply and capture was
inspected before deciding the next command. The final capture, personally
viewed, shows Human/Lord Crusader, map, Deathmatch Game,10000/10000 gold,
Crusader Demo row and the three preset circles. Its exact complete layout passed
both unchanged recognizers. Final continuation was review, stability768 and
route1600. This is stable setup evidence, not preset selection or gameplay.
The browser deadline left insufficient time for setup review and the dependent
preset/Zephyr/Start sequence. No such command was submitted. Chrome closed
normally at 13:53:54.725Z, exit0,168ms after its original timer deadline,
359.293 seconds after browser identity. The tested closed-session guard then
observed this normal closure and reported noCommandSubmitted: true; no quit
mailbox command or missing-reply timeout was created. The guard's fresh tests
cover normal closure without command, open session with one original quit and
three abnormal closure rejections. No second Chrome, retry, reload, deadline
extension, counter reset, forced callback, guest write, repaint or fault clear
occurred. The first-failure latch remained clear.
actual-result.json independently verifies190 complete64-step ACKs with
strictly consecutive steps through12160,1052 matching served pins, seven unique
personal reviews, all16 timely inspected successful replies, drained final
input and the bounded normal closure. Original navigation16384, route4096,
arrival3072, stability768 and command40-second bounds remained intact.
Captures are original host PNGs. No derived live PNG, guest raw-pixel dump,
native world state or gameplay claim is made; historical RGBA remains explicitly
historical.
Recovery fully SHA-verified300 immutable closed files/27059089 bytes and24 unique control files. The second control inventory was identical. Chrome and the replay process were absent, HTTP41281 was closed and final2415 pins passed before custody return at13:54Z. Coordinator lifecycle ownership and expiry remain as stated above. There are no further box operations after return.
The concrete remaining prerequisite is a fresh allocation with enough time
inside the same360-second interval for the mandatory setup review, MOVE-only
route-next, separate current preset-hover fetch → personal VIEW → separate
ACK and timely final success, then separate balanced preset press. Fresh
Zephyr handoff and unchanged separate native-Start guards still follow. The
successful early-title change does not authorize resuming this closed attempt,
changing any visual identity, increasing bounds or skipping reviews. Tool and
personal inspection latency must fit the original interval; no demonstrated
runtime helper defect justifies another repair here.
Provenance records initial checkout Git SHA
11acfe967e520b3f2dce52fc58b0b0bd1791f269, final test SHA, relevant binary diff,
owned new-file patches, small helper deltas and a full artifact seal. Git is
the source archive. The current corpus manifest has no matching Stronghold
candidate, so evidence stays in this investigation note without an unrelated
dashboard result or gameplay badge. No full-build result is claimed for this
documentation/run-helper-only task. This single bounded assignment is finished.