Return Fire current original: native vehicle movement and terrain action reviewed
Run: scratch/runs/20261108-return-fire-corrected-selection-gameplay/.
Tested source: 37ce9588e2bbe518e4bac8fa231cf893f7ebef56; preparation-time
relevant-source.patch is empty. Runtime pins identify the exact 700-file
closure. No emulator change was needed. This is one fresh original execution;
the earlier failed attempts, including 60b87651e, remain failed.
Current native vehicle/action progress is accepted. I personally reviewed the One Player/Easy launch dialog, readable bunker, vehicle deployment, forward and reverse terrain movement, steering, and a field-fire terrain consequence. This does not establish audio, logical FPS, GL coverage or full playability.
Exact selection and byte ownership
Before allocation, manifest-composition-control.cjs extracted and executed the
old selector and the actual new browser-run.cjs selector. The former reproduced
the registration JSON consumer timeout; the latter passed with the same native
response.json() API, pinned metadata bytes, normal loadingFinished, and a
mandatory generated binary consumer. No original was launched by this control.
composition-qualification.json also proves the executed selector equals the
prior corrected-browser-run.cjs selector and hashes the actual driver as
2a1caec192b09b1861a009767ee012d4c81dd9ff870753dd6bc40a65c4eb1852.
Only the exact .wine-assembly-browser.json registration path is excluded from
lazy binary observation. All 58 originals remain mandatory. The existing
qualified consumer, ACK, key/release and deadline controls were reused with
hashed references; generated cancellation research was not repeated.
The remote launcher rechecked all runtime pins before starting the browser.
original-consumer-audit.json independently joins all 58 originals (5,304,439
bytes) to GET/HTTP200, continued pinned bodies and actual application-consumer
EOF/hash completion. Session, target, Network/Fetch IDs, invocation token,
context/unique context, frame, document and timeOrigin agree. The zero-byte
TESTDIR.TMP has its actual EOF and empty SHA-256. All 64 selected consumers
complete: 58 originals, five fonts and stdole2.tlb. The final strict collector
is complete with no missing body or first fault.
The manifest is Network 6381.204, 7,206 bytes, SHA-256
e13e8ed1d2386862c11e76c1979c80e275765bf124b56997ccb7508f7f952c76:
pinned HTTP200 and loadingFinished, with no binary-consumer invocation. Eight
current original consumers genuinely report post-continuation ERR_ABORTED and
then pass their exact EOF/hash receipts: TRANS.TBL, RFIRE.HLP, BEACON.~AD,
CANNON.~AD, MISSILE_.~AD, TESTDIR.TMP, B1.WRL and B2.WRL. Their ownership and
event order are retained individually; no cancellation exemption was added.
The existing exact absent build-info.js HTTP404 policy also remains explicit.
Personally reviewed current native sequence
The unchanged registered route is
index.html?candidates&no-log&app=return_fire_demo, without thread/backend
overrides. Registration remains desktopColorDepth: 8, 57 supporting mounts,
and original DEMO.EXE SHA-256
b3407ec82d5e8d181116d2bb7a4998ff180773f3b6f91e98e7156979f3859a63.
No guest state, configuration or clock was edited; no private handler was called.
startup.png: native Return Fire Demo dialog, 1 Player and Easy selected. I read its actual warning about carpal tunnel, thumb arthritis and other humorous symptoms. A native mouse click on visible Play reachedplay-warning.png: the readable bunker with four bays, central ramp and radar/control strip. That filename was anticipatory: no separate post-Play warning appeared, and no unseen warning was dismissed.- K opened the vehicle information panel (
bunker-info.png), showing tank orientation and ammunition/vehicle indicators; another K restored the bunker. J opened the map inset (bunker-map.png); another J restored it. These match the read-only shipped RFIRE.HLP controls. - H selected/deployed the armored vehicle.
deployed.pngshows it crossing onto the central ramp. After one bounded passive wait,field-start.pngshows the tank at the yellow bunker entrance, with road, coast, radar and status bars. Deployment animation was allowed to finish normally. - W held for 2,000 ms and released:
field-forward.pngshows substantial terrain translation to palms/coast with the road receding at the top. D500 and A500 produced opposing orientation changes. S1,500 reversed the tank away from the palms;field-reverse.pngshows it clearly separated from vegetation, with the bunker entrance and road higher in view. - H750 in the field: the palm near the lower edge directly below the tank,
intact in settled
field-reverse.png, is replaced by fallen debris in settledfield-fired.png. This is a current visible weapon/terrain consequence. The viewer intermittently displayedfield-fired-held.pngand a repeat view offield-reverse.pngas blank teal. Exact retained PNG bytes prove these two files are identical (SHA-256b9e8e77748cd2fbca2c0e7e0f84f13f961c5ef8557c7e28ae39154f79de56ded), with 110 decoded colors and non-teal tank/HUD pixels. The reverse frame was personally reviewed with the scene visible. This viewer discrepancy is retained inheld-image-byte-check.json; the held frame supplies no continuous muzzle/projectile capture. No numeric ammo or fuel decrement is claimed.
All 13 numbered requests, including capture and ordinary completion, have exact successful ACKs; no UNKNOWN or stale refusal occurred. Each input used the immediately reviewed screenshot and matching live document/process/worker/module/ canvas identity. Each key hold retains passive samples and independent UP at the requested deadline. The passive physical-state reader covers arrow keys; it is not represented as WASD guest polling proof. The native key preflight, trusted dispatch, bound receipts and reviewed game consequences support these WASD/H/J/K results.
The debugger-recovered actual guest module is
f9650607181301b5d2a9990420f437bd9f1ca10d40ac73067339f07499d53121.
Chrome is 151.0.7922.108 / V8 15.1.206.16. Actual presentation ownership is
Win98Renderer with CanvasRenderingContext2D; no render endpoint or owning
D3D/GL worker exists in these captures. The unchanged registered indexed
desktop path is Canvas2D evidence, not GL coverage. Independent numeric surface
depth telemetry was not collected.
Validation, recovery and cleanup
Fresh original-recovery PASS58 and exact before-fail/after-pass manifest composition control preceded allocation. The in-browser native keyboard, typing and combo preflights passed. The final audit passed all 58 original receipts, metadata completion, 13 ACKs, capture/module hashes, hold release timing, 34 retained PNG CRC/IDAT checks, retrieval hashes and cleanup assertions. Owned JavaScript/Python syntax, note whitespace and dashboard evidence containment/schema checks passed; the global evidence checker still reports seven unrelated historical containment errors, with none in this run. No emulator source was changed, so no emulator regression/build claim is made. A local create-helper check initially ran before its detached delegate had written its armed record; it failed before any allocation API call. Allocation proceeded only once both armed PIDs existed. This was not an original replay.
One UUID-idempotent box bx_tutqr9c6, created 01:55:36Z, with detached independent
normal-stop and watchdog delegates prearmed before allocation. The fixed
25-minute watchdog deadline was 02:20:36Z, with durable heartbeats. Local and
remote /home free disk stayed above 5 GB; no RAM gate was used.
Chrome exited normally at 01:59:24.851Z, code0/signal null. A separate remote
census confirmed controller/Chrome PIDs gone, HTTP/debug ports closed, profile
removed and writer lock absent. All 196 remote artifact references (166 unique
hashes, 11,467,992 reference bytes) were retrieved and independently reread for
size/SHA-256 before requesting normal stop. Stop stop_d426b7930c00ab45
completed 02:00:08.794Z, forced=false. Final state is archived, expiry null;
initial expiry was 02:30:36.497Z. Both delegates exited0; supervisor children
are empty. The local messageboard watcher was stopped.
Recovery uses the exact source SHA, relevant patch, owned helper patches,
runtime pins, existing media path/hash references and unique recovered module,
captures and logs. No source/media archive, resume/delete, second box or public
deployment occurred. RECOVERY.txt names the checks and retained inputs.
Next: separately scoped longer combat/vehicle coverage, audio, logical FPS or full playability. This bounded task is finished; its box is stopped.