Return Fire current transport recovery — 2026-11-05

The sole original stopped before native Play at 15:20:22.347Z: the owning page Network session reported required RFIRE/ART/ART.CAR canceled with net::ERR_ABORTED. Its HTTP 200 body had already been captured, verified and continued. This is a retained transfer failure, not a missing-media or byte mismatch finding. No screenshot, player input, deployment, movement, audio or FPS observation was reached. No original retry or production change occurred.

Evidence: scratch/runs/20261105-return-fire-transport-recovery/. The capacity-terminated ReturnFire1410 preparation remains unchanged and UNEXECUTED; its model-capacity exit was not a platform rejection. Historical launcher/deployment/movement acceptance does not qualify this observation.

Entry and prerequisites

This worker remained source-only until Lords1355's 14:37:47Z, Stronghold1425's 14:49:14Z, then formats1430's 15:11:01Z exact final runtime/file releases with ALLBUILDSFINISHED. Independent checks found 158 predecessor PIDs absent, 11 profiles absent, 19 ports refusing connections, four locks free, no heavy runtime and over 9 GB free. The scratch checker was corrected to inspect profile-object path fields before claiming the note or running tests/build.

The separate explicit original binding uses the retained scratch/runs/20261105-return-fire-system-data-audio/used-composed-driver.cjs, SHA-256 90f4d8f6d182b28aefe07744148452d5deb8590aaf12801a0313e137ca13b008, and the published cf5e9c163 collector/composition. The production helper's generated-only guard is unchanged. The binding names only this fresh run, updates the cutoff to Nov06 02:00Z, and passively snapshots WinePerf only if already enabled. Required-byte policy, owning Worker startup binding, immutable first failure, personal launcher-review gate, ordinary Play/H/W controls and 180-second overall / 90-second readiness / 30-second observation / 2-second collector limits remain. Selected source SHA-256: 26dfa47d8a65e6d3ddb76a92fc778c9419ffb77120b3d2b31dc95f186a4ac20f.

Before the original:

The tested Git SHA is fb8725bbfd1280298229f0caa4627f6eccda64cb; the runtime code includes released ddc9e0e511. Relevant tracked files were clean. The run records the Git SHA, relevant binary diff and own new-file patches. The reuse audit names 30 source/module amendments from historical pins, with 1,502 unchanged; all 4,895 baselined historical artifacts remain unchanged. No source archive or duplicate media/module was made.

Canonical module: build/wine-assembly.wasm, 2,173,299 bytes, SHA-256 10462bd9693cf4f51d382d33767674b736b84e74346f328306d59e35c5e60031. The actual page captured this body, compiled/instantiated it and sent that module to the owning Worker, which instantiated it with the observation installed. The compat module is 2,175,945 bytes, SHA-256 eb59d32227cc18233f93c7b757e0700f9558f0a31af7e3d38090669d4fc15158; no compat consumption is claimed. Original entry: test/binaries/candidates/return-fire-demo/RFIRE/DEMO.EXE, 323,072 bytes, SHA-256 b3407ec82d5e8d181116d2bb7a4998ff180773f3b6f91e98e7156979f3859a63. The pin ledger references 60 media/manifest entries in place.

Actual first blocker

The one original began at 15:20:17.576Z under its exact parent exclusive local-runtime flock, after refreshed release/cleanup verification. Headful Chrome used the retained executable, fresh profile and default viewport/audio policy; no mute or autoplay override was supplied. Puppeteer is 25.7.0. Installed Chrome package metadata is 151.0.7922.71-1; no live browser-version query was recorded, so this is not asserted as the running browser version.

The page selected Fetch. The paused owning Worker encountered the exact Fetch-method absence, passed the Network sentinel capability check, installed observation and resumed. Its startup row was collected in that Worker session: 72,774 bytes, SHA-256 1a444957d8d4220443ce39fc11e5b90217ec2a22f234d2a9635bf9fee9d738e1. Target/request ID 16947959FD5C81A8800D38887FA1B5A3, Worker session 0FEC8AC574E26C98018AEEB608710082 and explicit parent session 2CE9E8CAD21C8215AD24A18C8DBDFEA1 match the recorded startup binding. Worker bytes matched the independently verified parent Fetch receipt; parent bytes were not substituted. This advances the previous Worker-capability blocker in the actual original, without establishing readiness or gameplay.

Required ART.CAR request 3004770.258, Fetch request interception-job-157.0, belongs to the page session. It requested GET at 15:20:22.263Z, paused HTTP 200 at .281Z, captured at .320Z and continued at .345Z. Captured size is 1,932,903 bytes; SHA-256 abcfc5c3efacf817c82f482458d95bb63fc0d76da5dfa297f3218066b1640b8a matches the existing canonical media. The Network response was HTTP 200 at .345Z, followed at .346Z by loadingFailed, type Fetch, canceled=true, net::ERR_ABORTED, before cleanup began. The first failure was sealed at .347Z, SHA-256 bfc438fad8a6173442ba8867f276bc948a4812de2f7b5093bebd24ab15ee5f78. The run retained 169 verified response receipts, two accepted absences and one exact font fallback; overall receipt and collector completeness remain false.

No emulator/host mismatch or cancellation cause was demonstrated. Required 200 cancellation was not reclassified as optional, ignored, or worked around. No state patch, forced frame, second original or additional runtime experiment was performed. Native Play readiness was never recorded; no images exist to inspect or acknowledge. Guest audio returns, populated PCM, host delivery, AudioContext/analyser activity, physical audible output and FPS remain unobserved. The last observer snapshot has no errors and classifies populated play as unobserved; it predates the terminal transfer failure.

Cleanup and next step

Normal Browser.close exited Chrome PID 3004662/startticks 193922794 with code 0/null. The original returned exit 1 with the retained first failure. Independent cleanup verifies all 14 unique recorded browser/entry/runner/test identities absent, HTTP 36155 and DevTools 32973 refusing connections, no profile users or heavy runtime, free locks and unchanged final pins. The fresh profile was removed after normal exit; no kill fallback ran. No box was assigned: ID/state/expiry N/A, shutdown ownership remains with the coordinator.

Only this note is committed. The next prerequisite is an offline generated reproduction of the captured-and-continued required-200 cancellation, preserving all byte/session/failure checks, before any newly authorized original. Current sustained play, audio and FPS remain open. Held investigations and public deployment remain untouched; no platform/tool approval rejection occurred.