GLTron owned invoker lifetime, 2026-11-20

Evidence: scratch/runs/20261120-gltron-owned-invoker-lifetime-visible-turns/.

The retained 20261120-gltron-moving-held-publication-original/start.cjs awaited normal completion but installed no cancellation handler. Its custodian also converted a signalled child's null status to success with code || 0. The earlier original lost owner PID 2070463 and its outer tool returned 143; the sender remains unknown. Nested waits and leaked:false do not establish the missing enclosing waits, nor identify that sender.

The bounded old control evaluates that retained invoker with only its runtime and watchdog command vectors replaced by real finite children. An explicit control-parent SIGTERM kills the old invoker and loses both enclosing waits. The new invoker retains direct normal, TERM, INT and deadline child waits, separate stdout/stderr EOF, stdio modes, PID start identities and owned signal calls. Cancellation closes admission before forwarding; deadlines and native supervision remain finite. Required-output and failed-status checks throw. This repairs cancellation custody, not an attribution of the historical kill. Shared native-supervise remains unchanged.

One fresh original used exact f6962ba5 runtime, a6002d5d module and all 92 unchanged media pins. The full host and fullscreen title menu were personally reviewed. At 1795148699795 admission closed on actual free disk 1492160512 bytes, before the first Enter DOWN. No successor was launched. Two later filesystem commands were refused before publication; neither issued an endpoint request. Visible turns, ordinary pause/resume, round outcome and Quit remain unproved. The writer consuming disk is unknown; no foreign process inspection or cleanup was performed.

The new original retains actual direct invoker wait 1, native supervisor wait 1, watchdog wait 0 and browser-driver wait 1, all with both EOFs. These enclosing waits are separate from the native descendant receipt. The prior 697ff892e moving whole-RGBA/operator-once, 11 focused and locked-build proofs are reused unchanged. No moving fixture campaign, module dump campaign, box or deployment was created. Final build/publication disposition is recorded in result.json; the disk floor must permit the required locked build before a code commit.