Neverhood current route qualification and installed shortcut
Evidence: scratch/runs/20261117-neverhood-current-qualified-installed-room/result.json.
Current qualification passed using the published 9acca37be helpers and retained
5a4178950559d4f677d86aa75403908abee343493805f01a0b8aae8f1df2429a
module. The complete sealed source inventory equals the retained final handoff
inventory. Unchanged native, installed provenance, startup, refusal and build
proofs are referenced rather than repeated.
The new authored route exercised native Play, ordinary CreateProcess, launcher guest ExitProcess(0), child-owned USER input, independent physical release and native child Quit. Actual new waits and both pipe EOFs cover the native launcher OS process (which remains the child broker after its guest exits), NHC-shaped fixture child, controllers, release processes, owner, outer supervisor and all watchdogs. The desktop authority/client participants are Worker threads; their termination events are observed separately, with no invented OS wait or pipe. The current qualification ended with no cleanup signals and empty owned scopes.
The historical 461/463-to-500 ms confirmation crossing remains unreplicated; its cause and the interrupted historical outer wait remain UNKNOWN. Neither is reclassified as a current defect, and no timing repair or relaxed predicate is claimed. Limits remain confirmation 500 ms, UP 1,750 ms, capture 3,000 ms, and review freshness 15/30 seconds.
One fresh authentic installed-shortcut invocation followed qualification. Its unchanged 65-record/58-file restore and WININIT state were recovered from pinned existing references into temporary sealed descriptors; no persistent media copy, reinstall or manufactured product state was used. An initial preparation attempt found the old launcher/overlay media had been deduplicated. It launched no native original and is excluded. The fresh invocation hydrated the authenticated restore, opened the shortcut target, and displayed the Neverhood launcher. The complete launcher PNG was personally reviewed before selecting its visible Play button. Play was natively consumed, independent UP acknowledged, and the actual NHC OS child was spawned.
Before child readiness, the independent watchdog sampled /home free space at
1,493,000,192 bytes, below the actual 1,500,000,000-byte floor, and sent SIGTERM.
The child exited by SIGTERM. The owner/broker exited with status zero after host
cancellation; that status is not native game Quit. The resulting endpoint remains
permanent UNKNOWN, with no subsequent HTTP or input. There is no room/object
progress or original native Quit claim. Every new owner, watchdog, outer and
native child has an actual wait and both EOFs; owned scopes are empty.
The original allowance is consumed. The immediate blocker is actual filesystem capacity, not the historical timing hypothesis. No second original, worker, box, public deployment, source archive, duplicated media or frame bundle was created. No production code change was needed or claimed.