Q3 fresh caller and preflighted local controller, 1615
The single native fixture failed before readiness at page-session
Target.setAutoAttach; movement and firing remain unverified. The resulting
generated-caller reporting defect is repaired offline: an actual first failure
now produces a nonzero exit after cleanup and read-only joins.
Evidence: scratch/runs/20261109-q3-preflighted-controller-arena-1615/.
Recovery uses exact Git base 1f69c75b640086cd27c9e41fa05fc00981e7bb90,
owned.patch, referenced retained small inputs and their patches. Git remains
the source archive; no source tree, game media or module archive was made.
Published a482339b7 extends the production controller regression to accept an
explicit fresh generated caller. It records that caller's SHA and imports its
entire generated module and run-local dependencies with process/network effects
refused. The exact generated launch body then runs through the actual
SHA-authenticated production controller CLI with its writer held open, the real
owning Session and retained launch/command branches. An explicit offline outer
transport refuses the first command; a queued later capture never reaches its
requested-command publication. Caller, Session children, controller and test
watchdog actually wait with separate output EOF. Native readiness and remote
custody are not inferred from those offline checks.
The fresh 942-provider production preparation retains the explicit foreign,
checkpoint and native lifecycle selectors. Primary CPU SHA 3e491c08 and compat
ecb45716, physical/WebGL checks, original deadlines and sticky first failure
remain unchanged. Both versioned actual prelaunch/custody/staged consumer paths
pass with Git unavailable and DRIVER_PREFLIGHT preventing Chrome creation.
Foreign closure refusals, launch-client controls, seven command-boundary cases
and the locked build pass. The actual run-specific provision function's upload
bytes and generated prelaunch syntax also pass offline checks.
Initial test supervisor errors are retained: a prelaunch invocation omitted its required output directory, a corrected invocation omitted creating that parent, and direct child writes bypassed a Python GzipFile wrapper in five initial test output files. Those mixed raw/gzip files are explicitly invalid, preserved losslessly, and excluded from proof. Final controller and subsequent test outputs use completed gzip bytes with independent CRC checks. Four completed startup manifests were losslessly compressed only after SHA/size/CRC verification with restoration recipes retained. The offline provision probe's first run omitted its explicitly inert lifecycle input; its generated upload journal was moved out of the actual provision output before any runtime use.
Q2-1615's final published release was observed by the bounded board watcher.
Independent re-reading verified 13 unique compressed artifacts, six actual
kernel reaps, physical drain, watchdog actual JOIN0 with separate output EOF,
and exact API ARCHIVED normal unforced stop_2175d0a06f9c43a9. Its missing
generated-parent wait remains UNKNOWN; kernel reaps do not replace it.
This task prearmed and independently observed an immutable 25-minute UUID
watchdog before its sole allocation, box bx_t2ubq3yn, UUID
e6dac148-e633-495b-b3f4-2727b4c80540, initial expiry
2026-11-09T16:51:04.556Z. Both actual remote prelaunch import checks passed.
The one generated fixture then failed at the unchanged 20-second CDP limit for
page-session Target.setAutoAttach, request 6, before navigation/readiness or
the fixture's input and capture. Root auto-attach request 3 and manual page
attach request 5 had replied. The diagnostic records two sessions attached to
the same page target, but does not establish that this caused request 6's stall.
The browser stall's cause remains UNKNOWN. No original, later input/capture,
retry, timeout change or second allocation followed.
The observer cancelled at the first published browser failure. All three
distinct generated-parent, prelaunch-child and runtime-parent waits have
separate stdout/stderr EOF. Kernel custody records 132/132 actual reaps.
Independent drain confirms ports 35659/46699 closed, profile absent, no runtime
FD holders or input writer lock, and runtime lock drained. Normal browser-close
EOF remains UNKNOWN. All 41 unique retrieved artifacts were independently
SHA/size/gzip-CRC checked before delegated normal shutdown. Exact final state
is ARCHIVED, archiveAfter:null, expiry NOT_RETURNED, completed unforced
stop_eb076fca0d3c6cdf at 2026-11-09T16:28:23.692Z. The watchdog actually
joined with status 0 and separate stdout/stderr EOF; its lifecycle parent
returned 0 and released the local runtime lock.
The native fixture's local generated caller recorded its terminal exception,
completed read-only joins, then incorrectly returned 0. The production
composeCheckpointCaller generator now retains that first controller exception
and re-raises it after cleanup and read-only join. A secondary read-only join
error is separately recorded and cannot replace the first exception. Planned
cancellation remains a successful prerequisite when its checks pass. No
provider acceptance, selector, custody check, input protocol, or timeout changed.
An actual production-controller CLI counterexample first reproduced child exit 0 after command failure and successful read-only join. Fresh generated callers now produce exit 1 with the exact first exception, both with successful join and with a secondary join failure. Queued later capture remains unrequested; every child actually waits with separate EOF. The full generated-caller test also covers seven checkpoint cases, including planned cancellation returning normally and six failure cases propagating their first error. Both actual versioned prelaunch/custody/staged paths, historical controller controls, 27 foreign-closure refusals, and the final locked build pass.
Next: diagnose the page-session CDP auto-attach stall offline. Native readiness, the original arena, movement/firing consequences, historical screenshot-stall cause and the prior original child wait remain unverified/UNKNOWN. No local Chrome, agents/workers, deployment or inherited-box mutation was used.