Published Neverhood handoff and release attempt

Evidence: scratch/runs/20261117-neverhood-published-handoff-release-room/.

The single installed-shortcut attempt used both published repairs: 95990aee32d4cd9f833857afba136d1d17681a5e for authenticated ordinary child observation and da5d6a6ee29ed1f76385f97268f02e8bfa350459 for the independent UP request's original absolute deadline. No production code changed in this run.

Before the original, a fresh published-source rehearsal proved ordinary native Play/CreateProcess, launcher ExitProcess(0), the child's own USER scene, child input, independent UP and normal child Quit. Parent failure, child cancellation, identity/source refusals, inherited ISO, real delayed TCP release failures, desktop participants, provenance and all twelve controller cases passed. The retained module SHA-256 is 5a4178950559d4f677d86aa75403908abee343493805f01a0b8aae8f1df2429a; 3,139 material source paths matched the retained native proof. The canonical locked build, lifecycle and shortcut tests passed. This does not claim a fresh run of every historical native regression.

The original restored the authentic 65 records/58 files and preserved pending WININIT. Its normal generated ShellLink selected SETUP95. Personally reviewed Play was consumed in 97.24 ms, independently released with ACK, and spawned the expected installed NHC. Launcher guest exit was zero. Authenticated child scene capture completed in 2,387.85 ms, within the unchanged 3,000 ms deadline. Subsequent complete captures showed black startup and then the illustrated Neverhood opening credits. The repaired handoff and release worked on the real installed product.

The operator allowed the credits capture to age 15.3705 seconds before trying to bind for ordinary Escape. The unchanged 15-second freshness check refused before child binding or input transport, then permanently latched UNKNOWN. There were twelve HTTP requests total and zero after UNKNOWN. No child DOWN, room, object action or normal game Quit was earned. This was an operator timing failure, with no demonstrated subsequent runtime defect to repair. No retry, rebinding, later query, direct NHC launch or bypass occurred.

Host cancellation then collected actual parent, child, controller, owner, watchdog and outer waits with both EOFs and empty owned scopes. Native exit zero during that cancellation is cleanup, not normal Quit; the child's failure record explicitly says host cancellation SIGTERM. All selected images, exact Git and binary patches, module-before-execution inventory and media hashes are retained. Closed duplicate installation inputs are recoverable from the authenticated existing ISO and prior installer state, with hash-verified recovery references. No boxes, workers, deployment, source archive or media bundle was created.

Room and ordinary object action remain open. Another original requires a new authorization; this attempt's UNKNOWN endpoint must never be reused.