Neverhood persistent owner and ordinary installation

Evidence: scratch/runs/20261117-neverhood-normal-create-directory-install-room/result.json.

Published b8dbbc7fb adds an actual persistent waiting launch owner pinned to the task worker, with an independently prearmed owner watchdog. It retires the transient launcher thread's inherited parent-death signal only after pinning the actual ancestor. The ordinary outer supervisor remains unchanged. Native TERM/INT cleanup now waits in finally, joins the pipe readers and independent native watchdog, and records both EOFs. Host cancellation is distinguished from native Quit and ordinary installation completion.

The same change permits retaining a tested module after exact compilation-input and module hash comparisons, and reusing completed native/controller proofs after component identity checks. dd9823805 records the byte-identical controller/native-test suffix separately from the prepended watchdog diagnostic. The first preparation correctly refused that whole-test-file difference before any original launch. Its actual outer/owner/watchdog waits remain in preparation-refusal/. No original allowance was consumed by that preparation.

The locked canonical build, unit checks, actual native TERM/INT cleanup, actual transient-launcher survival, independent owner deadline cancellation, actual outer/two-watchdog lifecycle, and exact disk-floor/deadline observation tests passed. The ordinary run used published ef51a021 plus the explicit published dd9823805 owned helpers. Material native proof pins matched; the unchanged controller/actor/focus/modal/fifteen-second/lifecycle proofs were reused rather than rerunning unchanged suites. Retained module SHA-256: 5a4178950559d4f677d86aa75403908abee343493805f01a0b8aae8f1df2429a.

One genuine SETUP95 invocation ran with all 257 CD members unchanged before its fixed 900/920-second clocks, the tested module retained before execution, and participant and exact-trigger watchdog observations prearmed. Personally reviewed Install and untouched default-directory OK completed under the 500/1750/3000 ms input limits. The genuine Create Directory confirmation was reached. No confirmation input was sent.

The agent then made a review error: it interpreted repeated image previews as blank desktop captures, permanently closed UNKNOWN, and requested host cleanup. Subsequent local SHA-256 comparison, PNG decoding and reopening prove that directory-ok-after.png, create-directory.png and confirmation-visible.png are byte-identical complete Create Directory images, with 259 RGBA colors. There is no established native rendering or capture defect. The earlier blank image statements are retracted. No speculative runtime repair is justified.

Native, outer, persistent owner and every watchdog have actual waits and both pipe EOFs; the outer scope is empty. The native status zero has a SIGTERM cancellation receipt and is not successful normal installation or native Quit. No watchdog fired. Neither the old exact disk sample nor the previous underlying ProcessDesktop timeout cause was established by this run.

Installation, authentic installed launch, room and object action remain unachieved. This original is permanently closed and its allowance is consumed; the agent did not retry, replay or rebind it. A further ordinary invocation requires separate owner authorization. No boxes, workers or public deployment were created. Box ID/expiry are null; state NOT_CREATED; stop NOT_APPLICABLE.