Return Fire boot system data pins and audio, 2026-11-05

The run-specific system-data pin closure passed both offline and in the sole original. The original then stopped before Play/audio because Chrome could not provide a pinned game-art response body to Puppeteer. No second original ran; no audio engine defect is established.

The run-specific amendment discovers the entire actual SYSTEM_DATA_FILES declaration in lib/process-boot.js and verifies the browser shell fetches that shared list on the local, non-deployed route. It adds every existing declared file to the served pin closure. No production source or audio engine change is needed for the previously demonstrated missing pin.

The published input is c617c4255bafca2e71a28bef0ce54de607035669, docs/re-notes/return-fire-font-fallback-audio-20261105.md, and preserved scratch/runs/20261105-return-fire-font-fallback-audio/. That sole original completed genuine five-font fallback, then stopped before Play/audio at the existing unpinned TLB. It did not establish an audio defect. Historical drivers, results and pins remain unchanged, covered by a 652-file baseline in this run.

The new explicit system-data-ledger.json records the whole discovered list, its VFS targets/local-only flags, declaration/fetch-source hashes and exact existence, sizes and SHA-256 values. Currently there is one declared file: test/binaries/tlbs/stdole2.tlb, 15,088 bytes, SHA-256 db456130e4b131aff27a6a3179464a28c9452f06eb6f2081d2aea38128d31895. This is a list-derived closure, not a filename exception or permission to skip existing TLBs. An existing file requires pinned HTTP 200 and an exact body size and hash. The full ledger is checked before pin collection and at finalization. Changed declarations, disappearance, new appearance and mismatched bodies fail.

For a genuinely absent declared file, only its exact canonical GET without a query and HTTP 404 can be optional, including the host's exact .part000 probe. Existing split fragments require explicit pin coverage and are rejected by this amendment. Undeclared paths, other statuses/methods, missing pins for existing files, cancelled or unresolved bodies remain faults. The current real TLB exists; no missing-file exception applies to it. Synthetic absence tests do not remove or conceal that real file.

The existing completed font fallback policy remains intact: only the exact five-font bundle GET/404 followed by all five pinned individual bodies can complete it. Immutable first failure, synchronous persistence before close, receipt completion and truthful terminal/final pin artifacts remain required. The amendment also checks pinned body sizes in addition to hashes. Before accepting Play readiness it requires a verified browser body receipt for every existing declared system-data file; a successful server send alone is insufficient.

The permitted light fixture executes the actual browser system-data boot block and actual host fetch method over the real static server, verifies all declared body sizes/hashes, and rejects ten altered-ledger/absence classifications. WebAssembly access and public/native process spawning are forbidden, with zero WASM compilation/instantiation or Chrome. This does not claim guest execution.

Evidence and small run inputs belong to scratch/runs/20261105-return-fire-system-data-audio/. Git SHA, relevant binary diffs and owned new-file patches provide source recovery; existing module/media paths and SHA values are referenced without copies or archives. Box ID, state and expiry are N/A; the coordinator owns shutdown.

Both prerequisite final runtime AND file releases preceded the composed tests, build and original: MDK0235 cd4b2e74174231b62ab3aa0affc2d1b1bb077efd and Stronghold0250 666b5ee4c211d20baa5c7927b07bc04084b1683f, each with ALLBUILDSFINISHED. The board was reread, and fresh independent checks verified their normal exits, all six exact PID/startticks identities absent, five ports refused, exact profiles absent, free runtime/build locks and no competing heavy work. Other queued workers retained source-only priority restrictions.

The 31 composed policy cases passed, including 13 system-data cases: omitted browser receipt despite real HTTP success, missing pin, wrong pin hash/size, wrong body, existing-file 404, 500, rejected/unresolved body, cancellation, unclassified query/method and undeclared path. Every failure is persisted before close and agrees with result/terminal artifacts. The missing-pin cases explicitly reject before launch. Missing browser receipt rejects Play readiness even when all observed receipts individually completed. Public Puppeteer and native ChildProcess spawn guards are exercised independently, with zero Chrome. All 19 preserved font-fallback rejection cases also passed.

The complete positive driver entry passed 2,038 real filesystem/HTTP sends, including verified system-data and all five actual host font fallback bodies. It checked pre-instantiation paused Worker wiring, default audio, defaultViewport:null, balanced input APIs and normal mock close. Its audio events are fixtures, not original guest execution or listening evidence. The required flock /tmp/wine-build.lock bash tools/build.sh passed. Unchanged prior audio boundary/preload, original inventory/PCM, routing/mixer/recovery/API observer results are reused by exact artifact hashes and unchanged composed source dependencies; their prior build and module evidence remain preserved.

The only changed historical production pin is the separately authorized, published Stronghold predecessor helper. source-reuse-audit.json explicitly records its old/new size and SHA, while all other 1,528 historical pins match. The new TLB pin brings the current closure to 1,530 files. No historical pin ledger is modified. Before the original, failed development fixtures were retained separately: the missing-pin negative prompted the pre-launch ledger check; source-wrapper anchor/import routing mistakes were corrected in the new run only. All final tests passed before launch.

The sole original started at 03:28:11.731Z under the exact parent exclusive /tmp/wine-local-runtime.lock, using source Git 1bcfd0de488d7ecbf80dd4eb73904ec1f8c46897 plus the recorded relevant binary diff and existing untracked runtime-dependency patch. The used composed driver and 19 sealed inputs remain unchanged. The registered indexed8 route, default audio, defaultViewport:null, ordinary Play/H/W controls, 90-second readiness, 180-second overall and maximum 30-second post-readiness caps were unchanged. The 08:00Z dependency, 08:40Z runtime, 08:43Z cleanup and 09:00Z finish cutoffs were not approached.

The actual original TLB response completed at 03:28:15.747Z with HTTP 200, 15,088 bytes and the exact ledger SHA. The genuine font bundle 404 completed as a distinct optional fallback after all five preserved individual bodies verified; no bundle body is labeled verified. This closes the previous system-data pin boundary in an actual original, not just in a fixture.

The immutable first failure at 03:28:15.851Z is http-receipt-error for test/binaries/candidates/return-fire-demo/RFIRE/ART/1PSCREEN.~CR: HTTP 200, expected SHA 6594b50825cea56d6b2d2591a4737b26757a0ee2e9c51fd76efb76f66fd9ab39, Puppeteer error Network.getResponseBody: No data found for resource with given identifier. The server guard had verified the existing 308,280-byte file and recorded a send, but that does not establish a completed browser body. Its receipt remains rejected/unverified. There are 163 response receipts: 150 verified, two optional absences, one completed font fallback, one rejected body and nine cancelled during close. Global receipt completeness is false.

The owning Worker was attached paused before instantiation. The page compiled and instantiated canonical module e620f3adfc2850580004e204bc1fea495844e942806866f8ada24c215212e412, sent it to the bound Worker, and Worker instantiation/API binding/diagnostic configuration are recorded. The compat module remains 66b37bd76da5a7b49c063b4eb0d44c898aaf00ff41e000a6fbd87c01edc136c8. The last observation is populated-play-unobserved. Selected audio API returns, loaded original instruction identity, PCM Lock/Unlock, ordinary Play, voice/source delivery, audio context clock, gain/mute or analyser samples are unobserved. No readiness, controls or fresh captures exist, so there are no images to personally inspect. Host audio delivery and audible output are unobserved; no sound-quality, playability or audio defect claim follows.

Offline body-rejection-replay.cjs uses the unchanged used driver, a real FS/HTTP 200 file whose SHA matches, and the exact injected body-reader error. It verifies the same rejection boundary and immutable first failure before close, with truthful terminal/final pin artifacts and zero Chrome. This replays the guard's response to the error; it does not independently reproduce or explain Chrome's missing body/request identifier. The installed Puppeteer source retrieves bodies through that request's CDP session and propagates this error. No production remedy or relaxed body verification is justified here. A future separately authorized observation first needs a qualified body-evidence remedy; there was no second original or live driver amendment.

Normal Browser.close completed with Chrome PID 1827762/startticks189650186, exit 0/null. Node 1827741 and parent flock 1827740, both startticks189650062, exited 1 truthfully. Independent cleanup at 03:28:38.565Z confirms those identities absent, HTTP 38203 and DevTools 44181 refused, the exact profile removed, no profile users/Chrome, and external runtime flock free. All adopted Chrome children exited 0/null; no kill fallback occurred. All 1,530 final pins remain unchanged, with no read errors. First-failure, driver result, runtime result, terminal, receipts, driver-final and final-pins artifacts agree; the 652 historical artifacts and sealed inputs remain intact. Only this note is committed. The assignment stops after publication and final runtime AND file RELEASE ALLBUILDSFINISHED.