Neverhood owned listener admission
Evidence: scratch/runs/20261117-neverhood-owned-listener-installed-room/.
The complete authored CLI startup proof used the retained module
5a4178950559d4f677d86aa75403908abee343493805f01a0b8aae8f1df2429a,
a real generated USER executable and a two-second delay of the actual
net.Server.listen call. A persistent owner and independent watchdog were
armed first. Passive local socket ownership preceded controller startup,
passive native readiness and atomic capture. No ACK or guest state was
substituted, and there was no bind or input. The initial proof passed with
208 PID-without-listener samples and a 121 ms capture.
The newly authorized original restored the authentic 65-record/58-file export and registry byte for byte, preserved pending WININIT, and resolved the normal generated shortcut through ShellLink and InstalledShortcuts.entryFor to installed SETUP95. Published shortcut and explicit-ISO ownership fixes were reused with their exact component/module proofs. No installer ran.
The local admission helper sampled process FDs before TCP state. The original failed its local ownership assertion. A listener appearing between these reads can produce exactly that refusal; the focused test reproduces this race. The failing FD snapshot was not retained, so attributing the original refusal to this race is an inference. The controller never started: zero HTTP, capture, bind or input. A later local diagnostic, taken before host cleanup, showed the listener inode in the expected native PID's FDs. This is an operator/harness sampling error, not a material native fault. The endpoint was permanently closed and no further original invocation was made.
The runtime now exposes listener RUN PORT [SECONDS] for passive admission.
It samples TCP before collecting the native process's socket FDs and checks
the process start token before and after that collection. PID presence alone
never qualifies readiness; foreign or ambiguous ownership still refuses.
It performs no network request and leaves the controller's existing identity,
freshness, actor, focus, modal, generation, nonce, 500/1750/3000 ms guards
unchanged. Future separately authorized runs must complete this step before
starting the controller.
Focused tests reproduce the old ordering with a real socket, verify the fixed ordering, exercise a real delayed listener and refuse foreign ownership, stale identity, deadline expiry and UNKNOWN without HTTP. The complete CLI startup fixture passes again through the new runtime function with a 116 ms atomic capture and actual native pipe EOF/wait. Existing lifecycle TERM/INT, persistent-owner deadline and outer supervisor checks pass. The canonical locked build result is recorded in result.json.
The original's native, adapter, outer supervisor, persistent owner and all watchdogs exited with actual waits, both EOFs and no remaining owned scope. Exit zero was host cleanup, not native Quit. Room and ordinary object action remain unproved. There is no authorization to retry this operator failure. No boxes, workers or public deployment were created; box ID and expiry are null, state NOT_CREATED, stop receipt NOT_APPLICABLE.