Return Fire required-200 cancellation — 2026-11-05
Actual generated Chromium execution reproduced the retained terminal signature:
required GET 200, verified Fetch.getResponseBody, successful
Fetch.continueResponse, then net::ERR_ABORTED, canceled=true. Independent
JavaScript consumers nevertheless received every generated byte. The same
cancellation also occurred without Fetch interception or any CDP body read.
The collector is therefore not necessary to produce this signature. Its
contribution to the original ReturnFire1435 failure remains unproven;
the original has no independent consumed-byte witness. No collector or host
change is justified, and neither cancellation was ignored or accepted.
Evidence: scratch/runs/20261105-return-fire-required200-cancellation/.
This is a generated transport investigation, not a game launch or gameplay
result. No original retry occurred. The predecessor's immutable failure remains
SHA-256 bfc438fad8a6173442ba8867f276bc948a4812de2f7b5093bebd24ab15ee5f78.
Input requested main is 7e3bf7788b229993266bb30b0f1d7b813163e04a;
see the retained recovery.
Generated browser experiment
Source-only preparation ended after Lords1450 15:35:30Z, Strong1500
15:51:00Z, then countselector1520 15:59:04Z exact FINAL runtime/file
releases with ALLBUILDSFINISHED. Independent checks verified 21 recorded PIDs
absent, four ports refusing connections, two profiles absent, four free locks,
no heavy runtime and over 9 GB free. No shared edit, executable test, build,
browser or module pin preceded that gate.
Tested main: f6b122eb429cbecf7e481cce798cf3419d146cb0. The selected collector,
composition, tests, host and byte-provider tracked diff was empty. Provenance
records their hashes and relevant binary diff; own generated helper sources
are recoverable as new-file patches. No source archive, original media copy or
module copy was made.
One local headful browser ran for 7.007 seconds under the local-runtime flock,
with a fresh profile and a 120-second browser deadline. Live Browser.version
reported Chrome/151.0.7922.108; Puppeteer is the installed pinned 25.7.0.
The fixture served only generated HTML, a generated dedicated Worker and a
generated ART.CAR. It imported the unchanged production collector directly.
The generated body is 1,932,903 bytes, with byte i equal to
(i * 31 + (i >>> 8) * 17 + 53) & 255; SHA-256 is
19346dc34617036349024d6e4c273a1f8cc0bfd43119640369953ef52e555619.
Node policy checks captured bytes against that generated input. Separately,
page/Worker code consumes the actual response, checks every byte against the
formula and computes WebCrypto SHA-256. No CDP bytes are supplied to a consumer.
The 24 cases cover page and actual dedicated Worker requests, arrayBuffer,
stream-reader and XHR consumption, each with no Fetch interception,
continue-only interception, or the production collector. Four additional page
cases compare six concurrent arrayBuffer/stream downloads with and without
the collector. Two cases exercise actual AbortController cancellation.
All 42 non-aborting consumer reads returned HTTP 200, the exact length/hash,
and no byte mismatch. That does not convert failed Network terminals into
successful required transfers.
Worker cases retain exact parent/session/target/startup identity. Chromium
selects the existing capability-checked child Network transport; startup and
asset bytes are read independently in that child. Parent Fetch and owning
Worker Network asset receipts both exist and remain separate. For example,
case 11 startup target/request C9FD366F8BFB39DEE4F427C21A624871 belongs to
Worker session E5FDE33E905D7A700C109AFDA7FBDEA2, parent
EAD4491DC2AC2C34BC36EF5EB743E16D. Both independently captured startup bodies
are 1,886 bytes, SHA-256
0a3a275f78574b28bff63159dc3618d82101588e5dcaf119983f7931da8b8e8b.
Parent bytes are never substituted for child bytes.
Retained cancellations
| Case | Independent consumer | Network result |
|---|---|---|
| 3: single page stream, no interception/body read | Full length/hash | GET 200 then canceled ERR_ABORTED |
| 21: six page streams, production collector | All six full length/hash | One required 200 canceled after capture/continue; collector incomplete |
| 22: slow stream, explicit abort after first chunk, no interception | AbortError after 16,384 bytes | GET 200 then canceled ERR_ABORTED |
| 23: production collector, explicit abort after verification before continuation | AbortError, zero consumer bytes | Required cancellation retained; continuation rejected; collector incomplete |
Case 3 belongs to page session FADCA52B5B73A560CC669FCBA5E87813, target
1E6C604C53F27A5772B6C3012113AFA5, Network request 3048233.2.
At 15:59:55.543Z its Network session recorded canceled ERR_ABORTED. Command
logs prove no Fetch enable, getResponseBody or continuation in this case.
Its consumer returned the full verified body. No explicit abort was called.
Case 21 belongs to page session 10534E038C882616039102BE190BB867, target
3B2BDFD38BC1C940DC26ECE7C6956530. Network request 3048430.2, Fetch
interception-job-39.0, was captured at 15:59:59.687Z, policy verified,
continued at .748Z, then canceled at .750Z. The consumer returned the full
verified body. The collector sealed exactly one immutable first fault,
network-loading-failed; drain rejected and completeness remained false.
Both explicit cancellation cases also retained their failure outcomes.
The browser result is not an all-pass matrix: the corrected strict checker exits 1 for cases 3 and 21. It verifies full consumer delivery separately and finds no collector-only delivery-interference candidate. The first checker also incorrectly assumed one asset receipt globally per Worker request. Its source patch, report and failure log are retained. The corrected checker requires both distinct parent and child receipts, including exact owning startup binding; the two actual required-cancellation failures remain failures. No production policy or assertion was relaxed.
The generated control establishes that this terminal signature can occur without the collector and without missing consumer bytes. It does not identify the underlying Chromium/stream lifecycle cause, establish that the original consumed its body, or prove interception had no influence on the original. Investigation stops at this concrete unproven-cause boundary. No speculative host repair, transport switch, cancellation exception or state patch was made.
Validation and cleanup
The unchanged collector suite passed 91 cases. The unchanged published
composition suite passed all 33 synthetic CDP/real-FSHTTP cases in 131.943
seconds, including public/native no-spawn guards (zero Chrome launches).
flock /tmp/wine-build.lock bash tools/build.sh passed in 37.205 seconds.
The final input hashes, including the original immutable failure, are
unchanged. Canonical and compat module hashes match the predecessor's
10462bd9…e60031 and eb59d322…15158; no module consumption is claimed by
this generated fixture.
The first composition runner expired at 120 seconds after reaching 32 of 33 cases. This was an undersized runner deadline: the predecessor's retained unchanged composition suite took 149.7 seconds. Its partial evidence and exit are preserved; unchanged tests were rerun in a fresh owned directory with a finite 240-second limit. No test timeout or production behavior was modified.
Normal Browser.close exited PID 3048093/startticks 194160290 at
16:00:00.459Z, code 0/null; no browser kill fallback ran. Final process,
profile, port, lock and watcher cleanup is recorded in this run. Independent
cleanup found all 18 unique recorded browser/command identities absent,
HTTP 44215 and DevTools 46701 refusing connections, the own profile absent,
four locks free, no heavy runtime and over 9 GB free. No test box
was assigned: ID/state/expiry N/A, lifecycle ownership remains with the
coordinator. Held investigations and public deployment were untouched. There
was no platform cybersecurity rejection. Current gameplay remains unobserved.