Prepared release helper; genuine UT partial memory installation
Evidence: scratch/runs/20261118-ut-prepared-release-helper-memory-install-gameplay/.
Code ae551e2fa was published with strict pull/push after focused tests and a
locked build. The single affected original used the published CLI graph
cc007fc738c2932bd5219de16fd26cbbad51b6df and the clean module
a1b157f7d9e800ac8739ddb0a31755f2738bc080d8f31146b2a31562663a8a64.
Held worktree runtime changes were excluded.
The previous original's one-second arm included spawning Node and importing helpers. Its first-chunk JSON parsing also assumed a complete stdout line. The new independent helper has a finite standby preparation phase before fresh capture/review and action clocks. READY explicitly has no release authority. Complete newline records survive fragmented output. The separate arm still has exactly one second, checks the native PID/start token/listener, guard owner and live document lease, and refuses cancellation, replacement and late arm. Only ARMED authorizes DOWN. The original fallback, confirmation and physical-UP bounds remain unchanged. The independent release survives parent retirement after DOWN, verifies the same owner, and observes physical-UP state within the existing confirmation budget. No ACK is synthesized.
Actual helper processes passed delayed startup beyond one second, fragmented READY/ARM, owner/document/native replacement, cancellation, late arm and early parent exit controls. A repeated negative caught an IPC cancellation EPIPE race; it was repaired offline and the suite rerun before publication. An earlier repeated run's evidence-directory mistake is retained separately. One authored native PE scope, within its declared 600-second/max-three aggregate, showed ordinary Enter changing the guest window title, matching independent UP with physicalUp=true/capture=0, then ordinary Escape/key-up/timer Quit and actual native exit zero, both output EOFs and no supervisor survivors. Tool-managed outer boundaries do not expose separate pipe EOF flags. The pre-arm parent-exit control proves helper retirement by process state; its orphaned helper has no separately retained actual-parent wait receipt.
One genuine UT Setup began at 11:23:40.694 UTC on 2026-11-18, with fixed
installation 1200 / total 2400 / final reserve 300 / cleanup 30 seconds. The
unchanged unique CD1 ISO mounted on default D:, with fresh writable memory C:
and default C:\UnrealTournament; neither old partial overlay was attached.
No media bundle, VFS export, manual extraction, config/registry/guest-state edit
or callback injection was used. Five ordinary native button gestures advanced
Welcome, I Agree, default destination, default components and Install. Each has
an actual native dialog invocation receipt and matching independent physical
UP. The first original arm took about 127 ms, causally removing the old startup
failure. Some immediate post-input images precede the asynchronous page change;
only fresh personally reviewed pages authorized later gestures.
The last retained snapshot showed genuine BotPack.u expansion at file 67%,
total 14%. A subsequent read-only memory manifest records 144 actual paths,
101,507,146 bytes, with per-file sizes/hashes and one selected small generated
INI. This is a partial installation inventory, not completed-install evidence.
No original installed child PID or exit exists.
The persistent disk guard preempted the owned supervisor; it recorded SIGTERM at 11:26:54.026, and native local cancellation began at 11:26:54.049. The guard's preselected threshold was 1,540,000,000 free bytes, above the owner's 1.5 GB floor. Native, supervisor and owner each exited zero with actual waits and both output EOFs; containment reported no survivors. These are cancellation results, not ordinary Quit. A later capture's unused standby preparation saw the already-present native wait and failed before READY, endpoint request or DOWN. That helper was awaited internally, but the failed-preparation path did not retain its PID/stream wait receipt; that evidence limitation remains explicit. No runtime endpoint or replay followed the closed scope.
This run proves the prepared helper on the affected original and genuine ordinary installation progress. Setup completion, Finish/Run, installed-child gameplay and ordinary Quit remain unproved. Durable installation remains OPEN, separately. The precise stopping condition is shared disk-capacity preemption, not a demonstrated UT engine fault. The writer responsible for the contemporaneous burst was not identified by this task. The disk-cause worker's later residual measurements cannot retroactively attribute it.
Both earlier partial overlays, the ISO and foreign source hashes were unchanged at offline audit. The first preparation guard stopped at its preemption warning, leaving a preparation monitoring gap; its minimum was 1,539,919,872 bytes. A fresh persistent guard covered the original and offline drains; final sealing records its actual minimum and wait. No agent, worker, box, Python, Wine, deployment or held-title action was used. Box ID/expiry/stop receipt are null; state is NOT_CREATED. The original scope is permanently closed; no retry or extension.
Final guard retrieval records a 1,496,264,704-byte minimum, below the 1.5 GB floor despite preempting the owned scope at the higher threshold. The global floor therefore did not hold during the monitored original/drains window; the exact minimum's timing within that window is unavailable. This task did not remove foreign files or attribute the writer.
The board-watcher enclosing tool exited 143 without retaining its child wait or pipe EOF receipt; its recorded tail PID is absent. The first offline seal attempt timed out on that missing receipt and published no result. The guard had retired, so there is a short additional offline seal-monitoring gap before the final finite seal sampler. Original native/supervisor/owner and the five armed release-helper waits retain their actual EOF evidence. These limitations are recorded explicitly rather than manufacturing a board wait or reopening the original.