Neverhood reused qualification and first authentic child capture

Evidence: scratch/runs/20261117-neverhood-reused-current-proof-installed-room/result.json.

The retained CURRENT full qualification passed hash verification, including its 360 artifacts, source inventory, native waits, media references, installed 65-record/58-file restore, registry and unchanged WININIT state. Published 9acca37be helpers and module 5a4178950559d4f677d86aa75403908abee343493805f01a0b8aae8f1df2429a were reused. The unchanged 13 modes, full authored workflow and canonical build were not repeated. No production source change or timing repair is claimed. Historical confirmation crossing remains UNKNOWN/UNREPRODUCED and was no gate.

Before the one newly authorized original, actual free space was 1,518,993,408 bytes; the necessary output estimate was 12,087,156 bytes. Existing immutable media and module bytes were reused. Ordinary child staging used a private tmpfs TMPDIR; permanent evidence and the run overlay remained in the run directory. The independent deadline/disk watchdog was armed before native execution. Its actual disk-floor guard did not fire in this run.

A new whole launcher PNG was personally reviewed in a separate tool turn before Play. Native Play was consumed and independent UP acknowledged. Ordinary CreateProcess spawned authentic NHC; the launcher guest exited with code zero, and its OS process continued as child broker. NHC published readiness 2,791 ms after Play and passed authenticated child attestation. The first whole capture request began at 2,980 ms, leaving approximately 20 ms before the unchanged aggregate 3,000 ms deadline. The HTTP capture timed out and permanently latched UNKNOWN. No subsequent HTTP or action was sent. A late whole PNG was inspected only after the failure: it is entirely gray and establishes no room or object progress. Child startup/capture cause remains unresolved; these timings do not establish a particular scheduling, filesystem, rendering or emulator defect.

Host cancellation then closed the child and launcher broker. Their OS exit statuses of zero are not native original Quit. Actual waits and both EOFs cover the native parent, child, controllers, release process, owner, outer supervisor and watchdogs. All three desktop Worker termination events were observed and known owned PIDs were absent. No box was created.

The original allowance is consumed. Room, object action and native original Quit remain unproved. The retained run registry and authentic overlay index are available. A persistence limitation is explicit in the result: the unchanged runtime merged one child file after the launcher's overlay flush, then removed its temporary export; that child delta has no separate durable copy. No gameplay save is claimed.

Further work needs a faithful workload reproducing the authentic startup/first capture deadline failure before a repair, and separate authorization before any additional original. This task leaves the failed endpoint permanently closed.