Return Fire repaired collector original, 2026-11-05
The sole fresh original passed the optional classic-script 404 boundary, then
stopped before Play because the paused guest Worker's CDP session rejected
Fetch.enable: the method was not found. The original was not retried. There
are no fresh screenshots, input gestures, gameplay or audio-delivery claims.
Evidence is in scratch/runs/20261105-return-fire-repaired-body-gameplay/.
Preparation remained source-only until Stronghold prompt-review's final release
d319ebcd17424e574675ba573dbd5a1dacc13670, followed by D3D secondary-target's
fbc8051625bca534bc8a8534cf8e641d9ada393e. Independent verification checked
28 predecessor process identities absent, four normal Chrome exits, four absent
profiles, 24 refused ports, both free locks, no heavy runtime and the disk floor.
The selected entry composes the retained system-data-audio used driver, SHA-256
90f4d8f6d182b28aefe07744148452d5deb8590aaf12801a0313e137ca13b008,
with the published repaired composition helper and collector from 7b958cd967.
The fresh binding changes RUN, the single named original assertion and the
startup cutoff to 16:00Z. Existing 180-second total, 90-second readiness,
30-second observation and default 2,000 ms collector deadlines remain intact.
Required bytes, absence/fallback policy, methods, redirects, owning sessions,
detachment, immutable first failure, ordinary input, readiness and personal
launcher-image review guards remain intact. The exact composed source SHA-256 is
cad3bb900902d7ca290a090da3fc4c57d1bcc78a3eee89d9ba01612889127aca.
Preflight passed the 62-case collector suite, the 32-case published composition,
the 32-case fresh named composition and two exact default-timeout positives.
These use synthetic CDP with real filesystem and loopback HTTP bytes. Both
public and native process-spawn guards reject once in each composed suite;
zero Chrome and no original guest execution occur in these fixtures. The exact
selected source's default-timeout positive hash matches the original entry seal.
All 1,532 pinned files are checked over actual HTTP, as are 252 discovered
requests. The required flock /tmp/wine-build.lock bash tools/build.sh passed.
These fixture results do not establish real Worker CDP capability.
The tested Git SHA is 25d94fc3df77f798f2338c19545c390a72f0393c.
The run records relevant binary diffs, owned new-file patches, input seals and
existing module/media paths with hashes, without source snapshots or media/module
copies. Relative to the preceding original's pins, 1,526 are unchanged and six
released source/module amendments are explicitly named in the fresh reuse audit.
All 2,623 baselined historical artifacts remain unchanged; the prior transcript
and its first failure are not reinterpreted as passing.
The one original started at 10:12:38Z under its exact parent exclusive local
runtime flock, after the independently refreshed release/cleanup proof. It kept
the default viewport and audio policy, with no mute or autoplay override. Its
canonical module body was captured and verified in the owning page: 2,159,447
bytes, SHA-256
05f4f99c47f46138bc599e0b588d0ab29ef87a5c8c0e22ded9e3ac9ac3fd3ffb.
The existing compat module is 2,162,062 bytes, SHA-256
67b702236abced4946b31906c901440f0d0607b99f74cd4b327a6dd0c9a18ca6;
no compat-module consumption is claimed. Page observation records module
compilation and instantiation, without establishing original guest readiness.
The owning page captured, verified and continued 134 HTTP 200 responses,
including the original guest-worker script body. The 137 individual receipts
also include two accepted absences and the exact font-bundle fallback. The
optional build-info GET/Script/404 carried the explicit identity-bound absence
acknowledgment and matching owning Network chain; its canceled ERR_ABORTED was
retained and classified optional-absence-script-rejection. This establishes
the repaired boundary in the actual browser. It does not verify a 404 body.
At 10:12:42.905Z, collector attachment to paused target
2319CA3554A8C5D39A31C0458A74B53C, session
31602C413B846DDCB37EA88A8EBB0705, failed at Fetch.enable with
ProtocolError: Protocol error (Fetch.enable): 'Fetch.enable' wasn't found.
The target URL is /lib/guest-worker.js?v=dev, with
waitingForDebugger=true. This is the immutable browser-body-collector,
enable-failed first failure, sealed SHA-256
befa084bc27b5438d9bfbbf984b2899b10486f61a296e3fb1db27bf963777a7d.
Collector, driver, result and terminal artifacts agree. Overall receipt and
collector completeness remain false despite the accepted individual page rows.
No bypass, alternate body channel or forced Worker resume was introduced.
No instrumented Worker report, native Play readiness, game-art consumption, menu, input event or screenshot was reached. There are no images to inspect or acknowledge. Guest audio API returns, populated PCM, host delivery, AudioContext clock progression, analyser signal and physical audible output remain unobserved. The synthetic fixture's audio events do not qualify this original.
Normal Browser.close exited Chrome PID 2660401/startticks 192076946 with code 0/null. Entry PID 2660376/startticks 192076800 and parent flock PID 2660375/startticks 192076800 exited with the truthful failing result. Independent cleanup verifies those identities and all ten test/build runner identities absent, HTTP 40987 and DevTools 43365 refused, no profile users or heavy runtime, both locks free and all final pins unchanged. The fresh profile was removed only after normal exit; no browser kill fallback ran. No boxes were assigned: ID/state/expiry N/A; the coordinator retains shutdown ownership.
Only this note is committed. No production remedy was inferred from a synthetic CDP implementation accepting a method that the actual Worker session lacks. The next prerequisite is offline qualification of an actual owning Worker body transport while preserving required-byte verification and all failure guards. Any subsequent original needs separate authorization and a fresh binding and preflight. This assignment stops without a second original or held-work changes.