NFS III after exact23 snapshot reclaim, 2026-11-13
The fresh run reached the original native 3D Device Setup renderer list,
showing Software Renderer and Direct3D Device 1. The next selection
click was refused locally before remote submission because actual /home
capacity fell below the strict floor. The immediate recorded sample was
1,499,369,472 bytes. No original race started; native SingleRacePaused,
Continue, finite driving, bends and lap remain UNPROVED. This is a
post-reclaim, post-provision, native-setup capacity blocker, not a new game
failure or an unchanged floor-only run.
Evidence: scratch/runs/20261113-nfs3-snapshot-headroom-native-driving-0700/.
The full renderer-options.png was personally reviewed before the refused
click. Original catalogue and first setup registration both exited code0.
An ordinary page reload and second native setup launch opened the chooser;
an ordinary mouse click expanded its renderer list. No renderer selection was
forced through registry, guest memory, clock, configuration or AI writes.
Preparation preceded the resource outcome. The fresh namespace reused only
the final corrected parent helpers, preserving the first missing-stage
known-unsent terminal result and both archived parent boxes. The actual
/dev/shm/nfs3-0700-ranges directory existed before freeze/create. The manager
now rechecks strict directory resolution, all descriptor hashes and the actual
browser caller's import/data branch before allocation. The caller preflight
also checks every safe local helper export it consumes and syntax-checks the
separate release/deadline/observer programs. Those are preparation changes;
the actual native-input, independent UP, full22, finite controller, initial
Pause single-use, freshness, consumed-review and UNKNOWN terminal/no-replay
behavior is unchanged. Telemetry was unchanged; no records were dropped by
a new consumer and no old matrix or 200ms UNKNOWN control was rerun.
The corrected observer adapter's original SHA remains
c34a7f9932c045f1042be06fb403ec7dc91ecdda369f563e511f980f86516c7e;
the emitted copy changes only the already-established helper-directory
reference. Nine runtime guard/observer helpers match the final dense0340
fresh namespace byte-for-byte. Eighteen retained parent proof files were
reread against their recorded SHA. Provider/custody matches published
5c2c410a5 exactly.
The coordinator's acknowledgment of dense0340's 01:02:20 explicit release
was read before monitoring backup0650's actual process, PID929948. Bounded
interruptible waits observed that specific process and its board/outcome,
without capacity polling or resource-file edits. Backup0650 completed its
stopped-snapshot transfer, restore/refusal checks and legacy-command proofs,
then reclaimed 69,382,144 allocated bytes. Its complete.json and causal
proof paths/hashes are recorded in this run. The fresh allocation sample was
1,529,524,224 bytes, above1,500,000,000. Shared capacity changes are not
attributed to a particular worker.
Before create, the final607-file descriptor was frozen and the independent
immutable deadline watchdog was observed armed. Actual readiness was idle.
Original EXE SHA is
0defab3eeb22ee4b6e0007a4d5b26a99d868008ba77e2b9bd3ef770e924548ad.
All133 original media references, current04 module, explicit RAM provisioning,
all609 remote whole-file checks and the actual provision parent code0/both
EOFs passed. The recovered actual Worker module has SHA
04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17.
Media is referenced by existing path/SHA, never copied into an evidence archive.
The local selection refusal created no provider command attempt and was not
replayed. Chrome and its owner then quit normally with actual code0 waits and
both EOFs. All64 unique output files were downloaded twice independently and
locally hash-reread before requesting the delegated normal box stop. Final
box bx_6xtq2g4h is archived, expiry null. Normal stop receipt
stop_fb1f3a8bdfcc3067 completed with forced:false and error:null at
01:14:54Z. Actual manager/watchdog joins are code0/both EOFs; see
stop-confirmed.json, manager-parent-wait.json and
watchdog-actual-wait.json.
Git SHA, relevant binary diff, owned helper addition patch and patch roundtrip preserve source identity. Only this scoped note is committed; no production code changed, so no locked build is required. Pawn0640/0730, LMarbles0650 and all resource/recovery files were untouched. No children, public deployment, source/media archive, inherited-box mutation or input replay occurred.
Next requires sustainable capacity through actual native setup and race, then a fresh watched box and complete provision join. Establish native Escape to SingleRacePaused/Continue and two settled full frames with reviewed stable world/timer before authorizing one1500ms-or-longer Continue/drive interval. Require its actual held frame before independent UP/Escape and freshly review the consequence before any further bend/lap claim.