Neverhood published listener and normal launcher Play
Evidence: scratch/runs/20261117-neverhood-published-listener-normal-play-room/.
The single authorized installed-shortcut invocation reached ordinary Play and spawned installed NHC through the launcher's own CreateProcess. The launcher then called ExitProcess(0). The controller had already sent its next snapshot to that retiring launcher endpoint; the connection reset before a child scene was observed. Permanent UNKNOWN closed the invocation after six requests, with zero later HTTP, input, rebind, replay or retry. No room, object action or native Quit is proved.
The complete 640x480 launcher PNG was personally reviewed. Play was the actual
enabled native BUTTON, HWND 0x10004, generation 4. Its finite click received
native-button-dispatch-return with matching actor, generation, owner, epoch
and nonce in 71 ms; the independently armed physical UP completed in 206 ms.
The snapshot failure occurred 509 ms after intent. The 500/1750/3000 ms limits
and 30-second menu/15-second game freshness were unchanged. No scene or
successful aggregate completion is inferred from the input ACK.
Before any controller startup, the exact published runtime command
listener RUN PORT 30 passed its passive TCP-before-FD ownership check. It
retained 87 PID-without-listener samples before finding the native-owned socket.
There was no ad hoc listener assertion or request to an old endpoint. The
published delayed-listener complete CLI proof and native lifecycle proofs were
reused through their exact hashes and actual waits, rather than rerun.
The authentic installer output was restored byte for byte: 65 overlay records, 58 files and the original registry. Pending WININIT remained unchanged. ShellLink and InstalledShortcuts resolved the original Start Menu link to installed SETUP95 with its normal working directory and empty arguments. No installer ran; no product state was synthesized and NHC was not selected directly by the worker. The launch log and real OS-child wait name the installed NHC child produced by ordinary Play.
Publication 8df40f958 fixes a preparation boundary encountered before the
original. The shared CLI scene file had advanced through another worker's
published diagnostic change. Explicit published component selection had still
required live checkout equality. Preparation and compatibility checks now read
the same explicitly pinned published bytes, so concurrent checkout edits do
not replace the sealed component. Allowed paths and published ancestry remain
mandatory. This changes source selection, not native input or capture behavior.
Focused tests verify shared-tree drift exclusion, unchanged unselected reads,
sealed inventory integrity and path/ancestry refusals. A complete authored
preparation run passes exact module, native, startup, controller and ISO child
compatibility checks and closes with actual waits and both EOFs. The canonical
locked full build passes. Its initial failure on the concurrently owned
host-import producer review is separately retained; that owner's review repair
allowed the successful build without foreign edits by this worker.
The original prepared the exact published adapter over base Git
ef51a021d0338895288888337772768878fd4fd4, scene component
63d7b0d0e8d979772a4e527a4d3561b4bdeb3692 and retained module
5a4178950559d4f677d86aa75403908abee343493805f01a0b8aae8f1df2429a.
Git plus the binary source patch and before-execution manifests recover the
executed inputs. The native graph's existing proofs match the selected
inventory; current shared native edits were excluded.
The remaining boundary is the controller's unsupported authenticated launcher-to-child observation handoff. The reset does not demonstrate a game crash or a native listener fault. No handoff repair or child readiness is claimed. Further work needs a faithful authored launcher-exits/child-survives test and a separately authorized original invocation after an authenticated handoff is implemented. The spent original remains permanently closed.
Explicit host cleanup followed UNKNOWN. Root native exit zero is accompanied by a cancellation marker; the child has an actual SIGTERM wait with both EOFs. Native, controller, adapter, outer supervisor, persistent owner and watchdog waits are retained, with no remaining owned scope. This is host cleanup, distinct from game Quit. Hash-verified duplicate restored inputs and modules were removed only after recording recovery references; unique outputs and the selected launcher PNG remain. No source archives, frame series, bundles, duplicate CD, workers, boxes or public deployment were created. Box ID and expiry are null, state NOT_CREATED, stop receipt NOT_APPLICABLE.