NFS III: remaining event recovery completed, native admission refused
Run scratch/runs/20261113-nfs3-native-race-1000/ waited interruptibly for
the live remaining-closed-events-pawn-witness-0940 resource phase. Its
02:12:47Z completion notice preceded this run's admission decision; the whole
Pawn task was not required or awaited. Four remaining eligible canonical
processed event streams were recovered: 1,785,809 logical bytes, with
1,794,048 allocated bytes reduced to 450,560 bytes of gzip and indexes.
The resource worker reports 1,257,472 allocated bytes saved, including
its then-current evidence. This is a distinct new recovery outcome.
The worker's inventory classified the other raw streams as current/pending,
without unambiguous canonical completion, or unsuccessful; already encoded
streams were excluded. Its completion notice, inventory, exact eligible list,
recovery result, recipe and four post-unlink restoration results/indexes are
referenced by existing path and SHA-256 in dependency-observation.json.
All four post-unlink results report full restoration, metadata preservation,
overwrite refusal and symlink refusal. No recovery files were changed here.
While this note was being published, coordinator reviews made two further
streams eligible (NFS0845 and stdout0900). The resource worker recovered
those too and announced phase2 completion at 02:14:08Z: another 548,864
allocated bytes saved, for 1,806,336 bytes across six streams. The final
inventory reports zero eligible raw streams: 20 remaining raw streams are
11 without unambiguous processed completion, eight current/pending, and one
unsuccessful worker. Both phase2 results and the final inventory are pinned
in dependency-observation.json. This scoped eligible pool is exhausted;
it did not restore the floor.
At 2026-11-13T02:13:18.126535Z, fresh actual /home available space was
1,487,409,152 bytes, 12,590,849 bytes short of the requirement to be
strictly above 1,500,000,000. After phase2 and the zero-eligible final inventory,
the fresh 02:14:45.696515Z sample was 1,486,520,320 bytes, a shortfall
of 13,479,681 bytes. Admission was refused before any runtime or
input. There was no RAM gate, foreign cleanup, private provisioning or disk
polling loop. No independent runtime watchdog was started because no runtime
was admitted; observable prearming remains required before any future launch.
The parent0930 task/note and published guard418099fe9 were read, followed by
inspection of the actual current lib/cli-guarded-input.js,
lib/control-server.js, handler dispatch and takeInput sweep in test/run.js.
The inspected source checks actual owner references and immutable wall and
monotonic expiry at consumption, refuses reused nonces, retains sticky
UNKNOWN/noReplay, and releases through the originally bound renderer.
These are source observations, not new native actor/consumer qualification.
All 147 source/media pins, 133 media files, nine prepared route
proofs, and 13 parent sealed files matched. The registered local
catalogue/setup/chosen-renderer route and unchanged native registry export
remain available in place. No media was copied or registry edited.
Renderer selection/OK, unchanged export into nfs3_chosen_renderer, race
entry, two settled native Pause/Continue frames with stable world timer,
and one manually reviewed >=1500ms driving interval with a held frame before
independent UP/Escape remain UNPROVED. No old capture or fixture was
promoted to native success. No automatic route, blind input chain, state,
clock/config edit, forced Present or uncertain replay occurred.
Git SHA and relevant binary diff are retained, with owned helper/note patches and media path hashes. No source/media archive was made. Only this note changes tracked content; no production code changed, so no build or native runtime test is claimed. Evidence checks verified the pins, parent seals, resource phase ordering and this run's dashboard references.
No owned runtime, input, watchdog or watcher remains. The short board watcher has an actual timeout124 parent result; it produced no runtime or input. Native parent waits/both EOF are N/A because no native child was created. Box ID NONE, state NOT_CREATED, expiry null, stop receipt N/A.
Next requires a distinct authorized source of sustainable headroom, then native selection/OK and the requested reviewed race, Pause and driving steps.