Neverhood desktop participant observation and ordinary install progress
Evidence: scratch/runs/20261117-neverhood-desktop-participant-cause-install-progress/result.json.
The previous ordinary installation reached its genuine default directory dialog,
then failed in ProcessDesktop.poll with ETIMEDOUT before directory input. That
endpoint remains permanently closed; its unobserved underlying phase is UNKNOWN.
The Neverhood runtime now arms the existing bounded worker-local desktop observations before native spawn and passes the directory through inherited OS process environments. The desktop transport and its fixed 3000 ms timeout are unchanged. A new focused probe exercises actual main/client/authority workers and an inherited OS child, verifies all nine correlated poll phases and the same sealed manifest, and checks their process/thread/preload identities. The existing real dead bridge and lost reply fixtures distinguish absence of authority receipt from authority consumption followed by a discarded reply; neither acknowledges caller success after a timeout.
Preparation uses published ef51a021 plus explicit owned helper patches, preserves the sealed Python source/hash reads and real registry repair, and reuses the prior native protocol proof only after exact equality of all 3,138 material pins and the retained tested module. All 257 CD members are hashed before the original clock.
The canonical locked build, focused unit checks, real transport diagnostic
fixtures, sealed inherited participant probe, and all twelve authored native
controller modes passed. The actual outer supervisor and both independent
watchdogs exited zero with both pipe EOFs and no remaining owned process scope.
The tested module is 5a4178950559d4f677d86aa75403908abee343493805f01a0b8aae8f1df2429a.
The single newly authorized original used the published helper composition. Personally reviewed ordinary Install and default-directory OK both completed: native receipt latencies were 48.615 and 42.512 ms, independent physical UP 161.570 and 194.742 ms, and completion records 522.330 and 241.120 ms. The complete next image showed the genuine Create Directory confirmation. No input was sent to that confirmation.
The independent native watchdog then terminated the native process. Its retained
deadline-or-disk receipt preceded its 920-second deadline by about 849 seconds.
The exact executed published watchdog has only one other trigger: a sampled
/home free-space value below 1,500,000,000 bytes. This proves the disk-floor
branch by control flow; the original exact free-space sample was not retained.
The current free-space value is not substituted for that missing sample. The
native process handled SIGTERM and exited zero, with a cancellation receipt;
this is host cleanup, not normal installer completion or native Quit. Actual
native, outer, owner and all watchdog waits and both EOFs are retained. The next
capture failed local PID identity before HTTP, permanently closed UNKNOWN, and
sent no later requests. Both inputs had already received independent physical UP.
The armed participant records contain no timeout/error for this run. Worker exit markers follow host cancellation. They do not establish the previous run's unobserved poll-timeout cause, which remains UNKNOWN. No speculative WAT fix was made, installation did not complete, and there was no installed game launch, room or object action.
The Neverhood-owned watchdog now records the exact trigger, free bytes, floor, deadline state and actual signal syscall disposition before/after cleanup, preserving the fixed deadline, disk floor and TERM/three-second/KILL policy. Authored disk-floor and deadline tests use real process groups, actual waits and both EOFs under an independently armed timeout parent. They also verify that an already completed wait sends no signal. Generic helpers remain read-only.
Another ordinary run requires separate authorization and sufficient shared disk headroom. No original was retried or rebound. No boxes or workers were created; box ID/expiry are null, state NOT_CREATED, stop receipt NOT_APPLICABLE.