NFS III UI-owner follow-through: scoped recovery still below floor
The distinct authorized resource phase completed, but its fresh original-game launch decision was 1,495,728,128 available bytes, below the strict 1,500,000,000-byte floor. The supervisor acquired the heavy-runtime lock, found zero actual heavy children, and verified all 448 frozen current source/module/media pins before refusing. Its actual parent wait returned 1 with both stdout and stderr EOF. No native process, watchdog, input, guarded bind, Pause/Continue or driving attempt was created. There was no retry.
Evidence: scratch/runs/20261113-nfs-ui-owner-1640/. Production remains
bcd4133909610bd75987dae16e0fd56d764f6de6; every frozen pin matches the
1550 handoff. The native chooser export remains SHA-256
e532c367bf58953a0d629ae0f3e5df93b8239daab0f713c1d8945e2dd92f087d.
The original manifest and existing local 133 media files were reused by path.
Git SHA and relevant binary diff preserve source identity without archives.
No production bug or new production change is inferred from a capacity refusal.
The already reviewed shared-WASM fixture and build were not repeated.
Only newly canonical closed Pawn1520, NFS1535, LMarbles1550, Pawn1550 and NFS1550 raw rollouts/events were claimed and encoded: ten files, 9,351,104 raw bytes, 3,112,137 encoded bytes, 6,238,208 allocated bytes reclaimed. Root ledger closure, result/final/notification/review identities, and exclusion from the current/pending registry were checked before encoding. Privileged producer cmdline and FD/maps closure checks passed before encoding and every unlink. All ten files passed complete raw and encoded SHA checks, external gzip decoding, actual RAM restores with mode and nanosecond mtime, and overwrite/symlink refusal before and after unlink. A further complete external decode and RAM restore verified all ten streams and forty closure-proof hashes. Durable indexes and RECOVERY instructions preceded unlink.
The final inode census initially flagged a reused inode. The preserved raw result and resolved census establish that FD 48 of new worker PID 1134426 references its different, linked 1650 rollout, with matching live path stat; it does not reference the removed NFS1550 stream. Final resolved FD/maps census and producer closure have no hits/errors. No active stream was changed.
Keep all original-path .gz siblings, this run's indexes and helpers,
and every earlier encoded dependency. Restore raw before history consumption
or resume:
python3 scratch/runs/20261113-nfs-ui-owner-1640/restore.py ABSOLUTE_INDEX_JSON
No existing encoded stream, DB, auth, media, source, save or ISO was cleaned. No guest/config/clock/AI writes, forced presentation, private provisioning, remote boxes or workers occurred. No existing runtime was stopped. The prepared independent deadline/disk watchdog was never started because the floor decision refused first. Box ID NONE; state NOT_CREATED; expiry null; stop receipt N/A.
Next requires sustained disk headroom from a separately authorized resource change. Then freeze current inputs, prearm the observable watchdog, inspect slot 0 and the active registered UI actor before guarded bind, and manually review each native frame. Two stable Pause/Continue frames plus worldtimer and the >=1500 ms held driving consequence remain unproved.