Neverhood visible modal and normal installation
Evidence: scratch/runs/20261117-neverhood-visible-modal-normal-install-room/.
The predecessor's installer endpoint remains permanently closed. Its host cleanup was not successful installation or native Quit. This task has one fresh ordinary CD SETUP95 installer authorization, with fixed 900/920 second native/watchdog deadlines and all 257 CD members checked before native start.
The controller now uses the owner's fifteen second game image policy at review, intent deadline and native consumption validation. Menu age remains thirty seconds; native ACK, independent physical UP and complete observation remain 500/1750/3000 ms. A new modal must be live, visible, top level and belong to the reviewed actor's process/thread before requesting immutable capture. Native capture still validates the complete owner/focus/window/control context.
Authored preparation exposed another sealed-source read: Python checked a CJS helper's hash against the live checkout, which had advanced beyond the selected published execution graph. The frozen Python reader now returns inventoried bytes for every inventoried file. Unknown Python execution remains refused. Regressions cover absent JS/JSON sources and an existing CJS path whose sealed bytes deliberately differ from disk, including inherited Python execution.
Preparation can explicitly compose a published base revision with the five owned helpers from a separately named published commit. Both must be main ancestors, helper bytes must equal their published Git blobs, and the actual complete graph, binary patch and module hashes are retained. This does not claim equality with either entire commit or adopt unrelated working changes.
Final execution, test results and publication hashes are recorded in result.json.
Published repair: 23e7cc6e1766c677748cfb2511d3efc9bd44a747. Locked canonical
build passed. Selected runtime module was separately compiled before execution:
5a4178950559d4f677d86aa75403908abee343493805f01a0b8aae8f1df2429a.
Native main/CPUWorker/OSchild, modal ownership/refusal/focus/nesting and lifecycle
checks passed; unchanged completed tests were reused only after material pin
comparisons. Fresh Neverhood tests passed delayed visibility (1034.6 ms),
permanently hidden timeout, game DOWN at honest image age 10.248 seconds,
older-than-fifteen-second refusal, and terminal UNKNOWN with zero later HTTP.
The single authorized original used the published ef51 base plus the published 23e7 owned helpers. Genuine Install BUTTON consumption took 76.515 ms; independent physical UP completed at 201.752 ms and aggregate observation at 528.264 ms. DirectX installation proceeded through genuine DLLs. A subsequent complete native capture showed the visible default-directory dialog, HWND 0x1000d, owner 0x10001, generation 13, process 1000/thread 1. Its native dialog callback, return site and focused OK child matched the public USER snapshot. No directory input was sent, no visibility waiver or manual ShowWindow was used.
The original then exited with status 1 after 96.661 seconds. Its public crash
log identifies ProcessDesktop.poll -> receive: ETIMEDOUT, the unchanged
3000 ms IPC deadline. The exception crossed the WASM host import; this is not
evidence of an unimplemented guest API or a WAT unreachable trap. Participant
observations were not enabled in that invocation, so the underlying lost IPC
phase is unknown. No source change is claimed to repair that timeout.
A later capture attempt failed the local PID identity check before HTTP and latched permanent UNKNOWN. The original remains closed, with seven total HTTP requests, one consumed input and one independently acknowledged release. Actual native wait is 1 with both pipes at EOF; native and outer watchdogs joined, outer scope is empty. Outer status 0 records supervisor completion, not installer success. No guest exit receipt, successful normal install, game invocation, room, object action or native Quit was obtained; crash-time overlay/registry exports were not produced and were not reconstructed.
The unchanged desktop diagnostic test passed real worker/socket delivery, dead-bridge and consumed-poll/lost-reply distinctions, fixed timeout and terminal closed behavior. It does not identify the original timeout's cause. Next work requires participant observations prearmed for a separately authorized ordinary installer invocation; the spent original cannot be resumed or retried.