Stronghold repaired capture onward, 2026-11-05

The single authorized original stopped at its first command failure: command 14, input-free route-arrival, rejected incomplete frozen ACK at 01:54:05.013Z. The owning Worker logged the native observer error draw clock/update/return history missing at 429b0e phase 3. No command 15, second original, preset, Start or world control followed. Ordinary gameplay and complete setup remain unproved.

This follows published 7c73cca3087d661e6aba1f57df082970705fe129. Evidence: scratch/runs/20261105-stronghold-repaired-capture-onward/. actual-evidence-summary.json, audit.log, draw-branch-replay.json and cleanup-verification.json record the actual outcome and its limits.

Both required final runtime AND file releases preceded any shared mutation, full build or original: MDK2 3c0035701 and Return Fire 94d1d6236, with all builds finished. Independent read-only checks confirmed their exact normal Chrome exits, Chrome/Node/flock PID/starttick absence, all five HTTP/DevTools ports refusing connections, profiles absent with no users, and free runtime and build locks. Shared changes began at 01:46:58Z. The original acquired exclusive /tmp/wine-local-runtime.lock at 01:49:05Z; no other Chrome existed.

Only the released local helper, its focused test and this note changed. The helper amendment names this assignment, the 03:10Z cutoff/03:13Z cleanup, the exact dual predecessor gates and published capture-repair provenance. The 720s runtime, 60s bootstrap, 40s command/review, 180s cleanup reserve, frozen 16ms cadence, full-rest/input guards, native history and all existing navigation/route/arrival caps remain unchanged. Seven behavior functions, including capture/fault handling, composition, scene diagnostics and review/ACK, match the published repair exactly. No MDK2 or Return Fire files were edited.

The historical 2,429-row manifest is unchanged. The ledger retains its five named amendments with historical, prior-binding and current SHA-256 values; all 1,856 media rows and retained helper identities remain enforced. The final locked full build passes and reproduces canonical modules e620f3ad… and 66b37bd7…. The local suite passes 43 release-contract negatives, capture/fault lifecycle cases and the actual full composed entry: 2,429 filesystem pins plus 2,429 HTTP responses, plain Puppeteer injection, independent public/native spawn prohibitions and zero Chrome. Route checks, 24 independent passive-host structural negatives and nine public-entry negatives pass. Current real release rows were used for the final composed preflight.

All 25 fresh original captures were personally viewed. Title entry, Crusader, ChooseType review and Custom Game hover followed successful review/ACK ordering; command 8 ACKed before command 9. The balanced ordinary Custom Game gesture ACKed before bounded input-free arrival observations. All 1,058 actually served responses match exact pins. The compiled and slot-0-delivered module is the canonical e620f3ad… module. There are 168 complete contiguous 64-step ACKs, ending at step 10,752. The failed partial ACK was not persisted; its count and exact stopped instruction are unknown.

The last fresh image, browser/route-native-boundary-8.png, was personally viewed at step 10,624. It still shows “Choose type of Crusader game”, towers, “Custom Game” and its description. SHA-256: 86c6119acf9499cff88cef2369fde1d218bf2b0d0ce520d46537dfedb3ec1728. No fresh partial setup or available preset/Start was established. Screenshots alone are not playability evidence.

The published capture repair works in this original: the first host report is running, frame zero, no fault, with capture explicitly deferred. Subsequent ordinary renderer returns support three screenshot brackets at frames 597, 601 and 605. No frame or renderer call was synthesized. These brackets do not prove fresh game pixels, operation-to-upload identity or readiness. The host observer first reports owner replacement during terminal cleanup, after the command failure; that later cleanup report does not replace the first error.

Native report prefixes remain intact across 105 retained reports. The last retained report has 37,712,185 boundaries, one original callback/request-20/setup return chain, one completed draw and a second draw pending at phase 3. Its last ACK has fade 22, direction -3, refresh 0 and input suppression 1. No surface operation was recorded. The native fault report itself was not recovered before Worker detachment; the console error and preceding pending frame are retained. A completed draw or a changed fade grants no setup or gameplay readiness.

Offline cause work began only after exact normal cleanup. Disassembly of the existing original executable shows 0x429770 -> 0x429af5 when refresh is zero, and 0x429723 -> 0x429b04 on another condition. Both can bypass the late clock at 0x429ae8/0x429aee before reaching 0x429b0e. The observer instead requires the late-clock phase unconditionally. The existing draw fixture explicitly jumps 0x4293c2 -> 0x429ae8, excluding these paths. A scripted boundary replay through the unchanged production observer passes the late-clock control and reproduces the exact phase-3 fault on the bypass. It executes no guest instructions. The actual bypass branch taken remains unknown; this establishes a coverage gap and a sufficient failure mechanism, not an emulator defect or permission to invent the missing clock/history. Next prerequisite: qualify these ordinary native branches conservatively before another authorized run. No observer repair, clock forcing, load forcing or readiness change was made.

Normal Browser.close was requested at 01:54:05.037Z. Chrome 1653904/startticks 189055631 exited code 0, null signal at 01:54:05.200Z. Independent cleanup at 01:54:13.371Z proves that Chrome, Node 1653890/startticks 189055439 and flock 1653889/startticks 189055439 are absent; HTTP 34601 and DevTools 35261 refuse connections; the exact profile has no users and is removed; the external runtime flock is free. Local heavy ownership was released at 01:54:23Z. Box ID/state/expiry: NA; coordinator retains shutdown ownership. No boxes were stopped, resumed or deleted.

Git is the source archive: exact commit identity, relevant binary diff and owned new-note patch are retained. Existing inputs, media and modules are referenced by path and SHA-256. No source snapshots, tars, copied media/modules, npm, worktrees, subworkers, boats, deployment or successor launch were used. This assignment ends with one tested publication and final runtime/file release; publication identity is recorded in publication.json.