Return Fire optional font bundle fallback and audio, 2026-11-05

The run-specific font-fallback monitoring remedy passed offline and in the sole original. The original accepted the genuine optional bundle 404 only after all five individual font HTTP bodies completed and matched their preserved pins. It then stopped at an existing, unpinned system-data TLB request before Play readiness or audio API observation. No second original ran, and no audio engine defect or production audio change is established.

The published input is e2cfd9ad95b136e4d6110bf63f437b84e9141ca6, docs/re-notes/return-fire-implicit-request-audio-20261105.md, and preserved scratch/runs/20261105-return-fire-implicit-request-audio/ evidence. Its sole original stopped on dynamic font /__bundle HTTP 404 before guest startup; five individual font body receipts were cancelled during normal browser close. Existing individual files and server sends do not establish completed original fallback. Prior used drivers, results and pins remain unchanged.

Source audit: host.js _prefetchBundled explicitly treats a refused bundle as an unavailable optimization, sets _bundleUnsupported, and leaves each caller to loadFiles' ordinary individual fetch. Its boot-font caller requires all five fonts. test/static-server.js has no dynamic bundle route. lib/file-bundle.js documents the same optional optimization and WAB1 format. This run does not invent a bundle response or alter those production sources.

The amendment accepts only HTTP 404 for the exact canonical five-font bundle GET query, with no existing bundle file/pin and with every constituent font matching the five preserved prior pins before launch. The bundle receipt stays pending until all five individual HTTP bodies have registered after that bundle request and verified against their pinned SHA-256 values; accepted fallback is a distinct policy and does not claim a verified bundle body. The existing two-second body settlement bound also bounds this fallback dependency. Other statuses or bundle queries, malformed URLs, missing/corrupt fonts, unpinned resources and cancelled or unresolved bodies remain failures. Immutable first failure, synchronous pre-close persistence and truthful terminal/final-pin artifacts are preserved.

Small executable amendments and evidence belong to scratch/runs/20261105-return-fire-font-fallback-audio/. Source recovery uses exact Git SHA and relevant binary diffs/new-file patches. Existing media and modules are referenced by path and SHA only. There are no production audio, MDK, Stronghold or Heroes II edits, source snapshots, archives or media/module copies. Box ID/state/expiry: N/A; coordinator retains shutdown ownership.

A permitted light HTTP fixture executes the unchanged actual host class, loadFiles and _prefetchBundled over the real static server. It passes with exactly six requests: genuine bundle 404 followed by five pinned individual font bodies, each also verified in the resulting VFS mounts. WebAssembly access, compilation/instantiation and public/native process spawning are forbidden; zero compiled modules or Chrome run. This qualifies the font fetch behavior, not the full changed driver composition or original guest/audio.

Both prerequisites released before full composition tests, the build or original: MDK0200 71985c4506f6dd6caa374357e5812350cf1ced1d and Stronghold0205 ac635964f52d222b99d04b0750601a2eee081f44, each FINAL runtime AND file RELEASE ALLBUILDSFINISHED. Fresh releases-verified.json independently checks the prior actual normal Chrome exit, exact PID/startticks absence, refused ports, absent profile/users, no other local browser/heavy runtime, free runtime/build locks and disk headroom. The messageboard was reread before proceeding.

The required full flock /tmp/wine-build.lock bash tools/build.sh passed. The unchanged eight audio boundary scenarios, four identity/source/clock/peak negatives, serialized page/Worker preload, all 58 original files, 37 PCM effects and nine loaded instruction pins passed. Existing worklet routing, mixer, recovery and owning API observer tests also passed. Eighteen policy/persistence cases reuse the prior sixteen and add missing/corrupt preserved font-pin cases. Nineteen new fallback cases reject malformed URLs/paths, changed/duplicate/ unclassified queries, wrong method, bundle 200/500, real individual HTTP 404/500 and corrupt bodies, rejected/unresolved/omitted bodies and cancellation. They assert immutable first failure before close and actual terminal/final-pin files. Public Puppeteer launch and native ChildProcess spawn prohibitions are independently exercised, with zero Chrome.

The complete positive driver entry passes 2,036 real filesystem/HTTP sends, including actual host fallback and all five mounted font bodies, paused Worker attach wiring, balanced trusted-input APIs, default audio/defaultViewport:null and normal close. Its audio events are fixtures, not original guest execution or listening evidence. full-entry-mock.json seals input hashes and the exact served closure before the original. Prior used drivers, results and pins match the 22 pre-test baseline hashes; original media mappings remain unchanged.

The one original began at 02:52:35Z under the exact parent's exclusive /tmp/wine-local-runtime.lock. It retained defaultViewport:null, default audio, the registered indexed8 route and the existing ordinary Play/H/W sequence. The 90-second readiness, 180-second overall and maximum 30-second post-readiness caps are unchanged. The first post-Chrome fault ended the attempt; there was no live driver amendment, second original or subsequent guest/browser run. The 05:25Z runtime, 05:28Z cleanup and 05:40Z finish cutoffs were not approached.

Actual runtime source identity is dd83d9aa7642f31c8118c3a289c9ac776211d36b, with zero relevant tracked uncommitted hunks and the existing untracked runtime-dependency new-file patch. All 1,529 final path/size/hash pins remain unchanged with no read errors. Canonical modules remain e620f3adfc2850580004e204bc1fea495844e942806866f8ada24c215212e412 and 66b37bd76da5a7b49c063b4eb0d44c898aaf00ff41e000a6fbd87c01edc136c8.

The original's bundle receipt is explicitly optional-fallback, with five verified constituent path/size/SHA256 records. Their sizes are System 13,456, MSSansSerif 20,128, Fixedsys 5,264, Courier 4,816 and Terminal 5,168 bytes. This is observed completed original HTTP fallback, unlike the previous run's cancelled individual receipts. The bundle body itself is not labeled verified.

At 02:52:39.221Z the immutable first failure was served-pin-mismatch for test/binaries/tlbs/stdole2.tlb: an existing 15,088-byte file with SHA256 db456130e4b131aff27a6a3179464a28c9452f06eb6f2081d2aea38128d31895, absent from the pinned closure. The server guard refused it before adding a successful send. Its later HTTP 500 receipt is cancelled/unverified during close. There are 151 actual response receipts: 147 verified 200 bodies, two accepted optional absences, one completed font fallback and that cancelled 500. Global receipt completeness is false. Server successful sends total 399, including preflight; neither count is the offline composition's 2,036 sends.

Offline source audit establishes this new harness boundary. The pin collector includes test/binaries/dlls/, but omits test/binaries/tlbs/. lib/process-boot.js declares SYSTEM_DATA_FILES, and lib/browser-shell.js fetches this shared list on the local non-deployed route before guest boot. It is a local compatibility aid whose absence the host can handle; this particular existing file still requires an accurate pin and verified response. The next remedy should discover this boot-resource list and pin existing files, preserving strict status/body checks. No change to that policy was made here.

tlb-boundary-fixture-v2.cjs replays the exact used driver and real FS/HTTP request, changing only the mock evidence destination. It reproduces the same missing-pin first failure and HTTP 500, asserts final artifacts, and launches zero Chrome. The first offline fixture's premature HTTP-result assertion is preserved; the corrected fixture separately waits for its navigation promise after mock finalization. This fixture wait does not amend the used driver.

The owning original Worker was attached paused before instantiation; module receive/instantiate, API binding and diagnostic configuration are recorded. The page compiled/instantiated the pinned canonical module and sent it to that Worker. No original loaded-instruction identity, selected audio API return, PCM load/Lock/Unlock, guest sound-enable/device gate, populated ordinary Play, voice/source delivery, context clock, gain/mute or analyser evidence was reached. Native Play readiness, trusted controls and a post-readiness window remain unobserved. No fresh screenshot was produced, so there is none to personally view or mark reviewed. Host delivery and audible output remain unobserved; there is no audio, gameplay quality or playability claim.

The immutable failure file precedes normal-close request at 02:52:39.222Z. Protocol Browser.close completed normally at 02:52:39.414Z: Chrome PID 1785019/startticks189436628, exit 0/null. Node 1784994 and parent flock 1784993, both startticks189436499, exited 1 truthfully. Independent cleanup at 02:52:56.258Z verifies all three exact identities absent, HTTP 46775 and DevTools 39531 refused, the exact launch profile removed, no Chrome/profile users and external runtime flock free. All adopted Chrome children exited 0/null; no kill fallback occurred.

Actual driver-result.json, immutable first-failure, runtime result, terminal, receipts, driver-final and final-pins artifacts all exist and agree. The post-original audit verifies prior inputs, sealed run inputs and used driver unchanged, the completed constituent font receipts and exact normal cleanup. Only this note is committed; run inputs/evidence remain in the ignored run. No production source/helper/test or audio engine file was changed. The next separately authorized observation needs the boot-resource pin-closure remedy; this assignment stops after publication and final release.