Return Fire current original: byte ownership passed, native progress blocked
Run: scratch/runs/20261108-return-fire-current-native-gameplay/.
Tested source: 8a6ca96982daa4b500616a6bc02c3e50c8df1bfd plus the recorded
relevant patch (empty at preparation). One original browser, no replay.
No current vehicle/action consequence is accepted. The first capture was refused by the strict collection gate before any original input. The new causal blocker is this worker's consumer-selection composition: it accidentally selected the registration JSON for binary-consumer observation. This is not an emulator fault or a recurrence of the earlier unexplained body cancellations. The original failure remains failed, and historical movement is not new proof.
Current original consumer evidence
The published attachPinned / actual-consumer observer was installed before
navigation and application fetch aliases. All 58 original files (5,304,439
bytes) match the complete registered recovery inventory; the unchanged manifest
mounts 57 supporting files. The original DEMO.EXE remains
b3407ec82d5e8d181116d2bb7a4998ff180773f3b6f91e98e7156979f3859a63.
No guest, configuration, clock, private handler or accepted palette/depth code
was changed. The route was
index.html?candidates&no-log&app=return_fire_demo, without thread/backend
overrides. The registration specifies desktopColorDepth: 8.
original-consumer-audit.json independently joins every original to its one
GET/HTTP200 Fetch response, continued captured body, pinned size/hash and actual
application completion. It checks session, target, Network/Fetch IDs, invocation
token, numeric/unique context, frame, document URL and timeOrigin. All 58 pass,
including the shipped zero-byte file with its genuine EOF and empty SHA-256;
no missing bytes are accepted. Across the selected startup invocations, 64 of
65 complete: 58 originals, five fonts and stdole2.tlb.
Five current original requests genuinely report post-continuation
canceled:true, net::ERR_ABORTED, then complete their exact application consumer:
| Network ID | Original file | Bytes |
|---|---|---|
17734.264 |
ART/ART.CAR |
1,932,903 |
17734.283 |
RFIREDAT/SOUND/DING.~AD |
10,772 |
17734.291 |
RFIREDAT/SOUND/HELI.~AD |
17,466 |
17734.306 |
RFIREDAT/SOUND/TESTDIR.TMP |
0 |
17734.314 |
WORLDS/A2.WRL |
16,464 |
The audit retains exact request ownership, hashes and continuation/failure/EOF event order for each. These new receipts demonstrate the published fix on current originals. They neither waive unrelated errors nor retroactively supply receipts to historical failures. Overall collection is still incomplete.
Exact new blocker and local correction
Invocation wineConsumer_66abb581434c9d17c511ff96_1, Network 17734.204,
Fetch interception-job-102.0, is the 7,206-byte registration manifest
.wine-assembly-browser.json, SHA-256
e13e8ed1d2386862c11e76c1979c80e275765bf124b56997ccb7508f7f952c76.
Its body passes pinned capture/continuation and Network.loadingFinished. Its
real initiator is launchAppInner in lib/browser-shell.js, which consumes
response.json(). The published observer supports original reader EOF and
arrayBuffer completion; it does not observe JSON consumption.
The run's lazy predicate selected all other test/binaries/ paths, inadvertently
including this metadata. Consequently its bound invocation has no supported
consumer completion and the sticky ten-second completion timeout is correct.
first-body-fault.json, first-browser-failure.json and
collector-final.json retain the failure; no original input was dispatched.
The preallocation generated HTTP-worker control had covered body transport but
had not exercised the registered launcher's JSON metadata boundary. Thus the
composition was not fully qualified before allocation, despite those passing
controls. That is a limitation of this attempt, not original gameplay evidence.
corrected-browser-run.cjs excludes only the exact registration-manifest
path from the lazy binary-consumer set. Every eager original remains mandatory;
all other lazy observation and strict HTTP body/status/cancellation policy
remain. The manifest still requires pinned HTTP bytes and normal Network
completion. No generic JSON shim, blanket ERR_ABORTED exemption, optional
original or replacement fetch was introduced. prepare.py carries this exact
correction for a future composition; the executed browser-run.cjs and its
original pin ledger remain unchanged.
manifest-composition-control.cjs extracts and executes the actual before/after
lazy selectors. It fetches the unchanged registration bytes through the same
response.json() API, plus a generated binary consumer. The original selector
fails with the same consumer timeout. The corrected selector passes while the
manifest retains exact pinned bytes and loadingFinished and the binary retains
its mandatory completion. manifest-composition-regression.json records both.
No original executable was launched in this control. No production code change
or additional original was made.
Native and validation limits
The actual debugger-recovered guest module is
f9650607181301b5d2a9990420f437bd9f1ca10d40ac73067339f07499d53121.
The original log records guest Worker instantiation and native ShowWindow.
Collection failed before state/screenshot capture: no native UI was personally
reviewed and no Play, bunker, deployment, terrain/fuel, weapon/ammo or second
vehicle is proved. Actual desktop depth and renderer/context remain unqualified
in this run. A selector or Canvas2D/indexed output would not establish GL
coverage. The accepted palette/depth repairs remain accepted.
Before allocation: original recovery PASS58; collector PASS129; fresh Chromium stream/arrayBuffer completion and all eleven negative controls PASS; real HTTP worker attachment proves the published paused-worker Network body fallback, not unsupported Fetch.enable. Current numbered ACK/client controls pass 0/1/2/10-second waits, rejection before publication for oversized waits and stopped input, independent UP with a slow sampler/UNKNOWN, and native trusted H/J/K/WASD/Enter/Escape/mouse edges. Every bound identity field rejects a changed token in the synthetic comparison; the original readLive guard was never reached. No original ACK or key effect is claimed. Initial generated desktop and blob-worker composition failures are retained separately and were corrected before allocation; they are not original attempts.
The shipped RFIRE.HLP was decoded read-only. It identifies H/J/K as select/map/information in the bunker, H/J/K as ground fire/air fire/switch in the field, and WASD movement. Those semantics cannot be assigned to an unseen native action. Audible output, logical FPS and full playability remain separate.
Lifecycle, recovery and next step
One UUID-idempotent box bx_drg23cfh, created 01:37:18Z. Detached independent
normal-stop/watchdog OS delegates were armed before creation; immutable
25-minute deadline 02:02:18Z. Free /home exceeded 5 GB locally and remotely;
no RAM gate. Chrome exited normally at 01:37:52Z, code0/signal null, and the
controller recorded terminal closure. The adapter was closed before browser
shutdown and the owned profile removed by the controller. A separate remote
PID/port census was not retained, so that additional cleanup proof is not claimed.
All 30 remote artifacts (7,876,792 reference bytes, 29 unique hashes) were
retrieved and independently reread for size/SHA-256 before delegated normal
stop. Stop stop_04c349fbb8d4bb49 completed 01:38:53.971Z, forced=false.
Final box state is archived, current expiry null/unknown; initial expiry was
02:12:18.330Z. Both delegates exited0, supervisor children empty. No resume,
delete, second box, source/media archive or public deployment occurred.
Recovery uses source-sha.txt, relevant-source.patch,
executed-browser-run.patch, runtime-pins.json, fixture-identity.json,
owned-helper patches and retained unique instantiated module/logs. Media is
referenced by its existing path and hash, not copied into evidence.
Next requires a separately authorized fresh original using the corrected exact selection, after qualifying that same metadata/binary composition. Then personally inspect One Player/Easy, Play and any actual warning, reach a readable bunker and test native vehicle/action consequences through strict bound input. This spent single-attempt grant permits no original replay.