Return Fire captured browser bodies and gameplay, 2026-11-05

The sole authorized original stopped before Play at a browser transport failure for optional build-info.js. Actual page Fetch capture and unchanged continuation worked for the pinned HTML body. Worker coverage, game-art consumption, menu, gameplay and audio delivery remain unobserved. No second original ran.

The exact published 69a5ea89d collector and composition helper are unchanged. The reused historical entry is scratch/runs/20261105-return-fire-system-data-audio/used-composed-driver.cjs, 24,589 bytes, SHA-256 90f4d8f6d182b28aefe07744148452d5deb8590aaf12801a0313e137ca13b008. Its first-failure artifact retains SHA-256 36714e00ab3f73679e6b1932f665cea6a71c4166353d3d76d94b676b523f9e48. All 1,466 baselined predecessor artifacts remain unchanged.

Evidence and the named fresh binding are in scratch/runs/20261105-return-fire-captured-body-gameplay/. Source-only drafts preceded the ordered Stronghold0620 release 23d773990dcedcdf2df551f1e105ec39f529a045 and D3D7strided0635 release 4683c73ca889ff4f84d809e2fb7fd3d06432f7c3. Both published FINAL runtime AND file RELEASE ALLBUILDSFINISHED before executable checks. Independent release verification checked exact process identities, required normal exits, seven absent profiles, fifteen refused ports, free locks and the disk floor. The Stronghold predecessor's explicitly nonnormal leaked fixture remains labeled historical nonnormal evidence; it is not relabeled as a passing normal exit.

The fresh binding changes only RUN, the mock-only assertion to allow this single named original, and the obsolete startup cutoff to this task's 15:00Z deadline. The existing 180-second total, 90-second readiness and 30-second observation caps remain. Pin/hash/size policy, system-data ledger, exact font fallback, immutable first failure, ordinary controls, default viewport/audio and final artifacts remain intact. The reused generic lifecycle helper requires a direct run directory; the fresh binding uses that directory, without module/media copies or any other-game investigation. Git SHA plus relevant binary diffs and new-file patches provide recovery. The source reuse audit names thirty released source/module amendments and 1,502 unchanged old pins. Historical ledgers are not rebound or edited.

flock /tmp/wine-build.lock bash tools/build.sh passed. The focused collector suite passed 27 cases, and test/test-return-fire-body-driver.js passed all 22 published composed-entry cases. The fresh binding passed the same 22 cases. Those negative fixtures use a 100 ms collector deadline; a separate positive pass executed the exact fresh original entry with its default 2,000 ms deadline. Both public Puppeteer and native process-spawn guards were exercised before spawning in every composed suite: zero Chrome and no guest execution. These synthetic CDP/real FSHTTP results do not establish browser gameplay or audio. The exact-entry seal binds the composed source hash and existing input paths.

The original started at 08:12:53Z on tested Git fe17426859d17589a0883adbf42d3271c9f5f6cb under its exact parent exclusive runtime flock after a fresh independent release/cleanup proof. Existing modules are canonical SHA-256 3361c1289e540ba1107c788905ab5a70ace7f4d003cfd05e1264c54bfc65267b and compat d33d98564db864ce8a1a7a4abad0554c4934331b36074bdb854c1ab96e458008. No guest module load was observed in this original. Launch retained default audio policy and contained no mute/autoplay override. No input gesture occurred.

Actual owning-page Fetch interception captured index.html HTTP 200: 183,083 bytes, SHA-256 fa81b9ebfd01d3fbfa2852bfec4503a87d4b5ce47cf4522cd4c134ac82cfb11c. Its pin receipt verified, Fetch continuation completed unchanged, and matching owning-session Network HTTP 200/loadingFinished events were observed. This is actual browser body evidence for this page only. The exact optional build-info.js GET/404 then completed its optional-absence policy and unchanged continuation; no 404 body is labeled verified.

At 08:12:55.965Z, the same optional request emitted Network.loadingFailed, net::ERR_ABORTED, canceled=true, network ID 2527387.2. The immutable first failure is browser-body-collector, state network-loading-failed, session 9DF451F705F8195473792A7B3CEC82D6, target 9E7561AB6B5620DD82F3E2D7F9193E1B. It precedes the recorded page close. The existing rule rejects raw loading failures even for a policy-accepted optional 404. No cause of that cancellation, body-collector remedy or permission to ignore it is established. Both Fetch rows continued, but overall collector completeness remains false because of this first fault. Failure/driver/result/ terminal/collector artifacts agree, and all 1,532 final pins remain unchanged.

No Worker attached, no Play readiness or input was reached, and there are no fresh image captures to inspect personally. No menu or gameplay claim follows. Audio API returns, PCM activity, context state/clock, host source delivery, analyser signal and physical audible output are unobserved. Offline PCM and synthetic audio fixtures are not substitutes for these observations. The previous missing-art-body boundary was not reached.

Normal Browser.close completed: Chrome PID 2527247/startticks191358381, exit 0/null; entry PID 2527223/startticks191358258 and parent flock 2527222/startticks191358257 exited with the truthful failing outcome. Independent cleanup proves those identities absent, HTTP 44437 and DevTools 42177 refused, no profile users/heavy runtime, and both locks free. The owned fresh profile was removed only after normal exit and identity checks; no kill fallback ran. Box ID/state/expiry N/A; coordinator retains shutdown ownership.

Only this note is committed. No production collector/audio change is warranted by this bounded observation. The next prerequisite is separately authorized offline qualification of the optional-404 cancellation boundary while retaining strict rejection of genuine transfer faults, followed by fresh authorization for any original. This assignment stops without a browser retry.