Q2 current caller: full offline lifecycle and runtime queue

Evidence: scratch/runs/20261109-quake2-current-caller-guard-progress-1715/.

Fresh production preparation accepts all 735 providers with published caller repairs d0ecba843 / e46911276, browser module quake2-1495-published-5c8780318-writer-e5eff70be-f977ebf7c-v2-browser-1605-v1 and policy quake2-current-primary-3e491c08-v1. No provisional provider repin was used. No additional production code blocker was demonstrated.

tools/quake2-current-caller-lifecycle.test.py now exercises the owning production CLI, explicit stdin start, actual retained 1645 launch branch, content-verified startup barrier, actual current remote parent, selected preload and actual composed consumer. The fixture, passive health and wire hooks all execute their composition checks. DRIVER_PREFLIGHT stops before Chrome, Worker or guest execution. Runtime Git is forbidden by a failing executable adapter; the production manifest remains byte-identical.

Both the explicit direct-Node test seam and the actual kernel supervisor pass. The kernel run verifies complete descendant reaping, empty unresolved sets and lock release. Every outer parent separately waits and drains stdout and stderr. The caller keeps stdin open through setup, then treats preflight transport exit without a quit ACK as terminal, without publishing a command. The direct seam makes no kernel claim; neither run establishes native qualification. An initial authored test seam omitted the supervisor's BROWSER_DEADLINE setup and correctly failed. Its empty stdout and retained error are not a pass; the seam was corrected to preserve actual supervisor environment setup before the passing checks.

Existing lifetime controls pass: six EOF/start/command cases, historical failure reproduction and sticky cancellation before a late parent. The staged Git-free suite passes its missing/damaged-provider, wrong-version, wrong-authority and forged-repin refusals. The required flock /tmp/wine-build.lock bash tools/build.sh passes.

At 15:46:13 UTC, an independent exact-UUID API read confirms Redline1635 box bx_ncb2wqug, UUID 846740ce-e8a4-4e30-946a-249f07f89376, is ARCHIVED. Normal unforced stop stop_e0bd4a87ad595fc7 completed without error at 15:41:47.791Z. Its recovered physical and kernel drain receipts were independently reread by SHA, size and gzip CRC: twelve owned identities were actually reaped, with no remaining identities, FD holders or profile. No endpoint number was published, so this supplies no numbered-port connect proof. Historical separate Node-command EOF remains UNKNOWN.

At that observation, both final published queue releases were absent. Redline1635 subsequently published its final RELEASE STOP at 15:46:43 UTC on 801ed127f0ae9997912f7abce45f3b61edd92d71. Its exact archive and physical drain are independently verified above. The remaining first allocation blocker is Q3-1705's required final published release and exact-UUID archive/ drain or explicit NOT_CREATED. Q3-1705 remains ahead of this task. Thus no lease plan, final runtime pinset, allocation watchdog or box was created, and no local Chrome, native fixture or original attempt ran. Guard defeat and onward-door consequence remain UNVERIFIED. Box ID/state NOT_CREATED, UUID/expiry/ stop receipt N/A. No preexisting box was changed.

Only the new regression and this note are owned source changes. They are not included providers in the current Q2 or retained Redline runtime manifests; no foreign provider was frozen. Owning Worker, slot0, native writes, canonical EXE, primary CPU 3e491c08…, compatibility CPU ecb45716…, source lifetime and deadline behavior are unchanged. All-writers, aliases, peer/raw-host parsing and ABA remain UNKNOWN; nativeQualification=false.

Recovery records the exact Git base and small patches, with logs in this run; no source-tree, media or module archive was made. Free /home stayed above 1.5 GB during observed checks. No agents, workers or public deployment were launched.

Next runtime work requires both final published queue releases and Q3's exact-UUID archive/drain or explicit NOT_CREATED. Then prepare fresh runtime pins through the production preparer and observe an independent immutable 25-minute UUID watchdog before one allocation. Execute the one authorized fixture; original guard/door work remains conditional on every existing fixture and cancellation gate. First failure is terminal. Retrieve and hash-verify unique evidence before delegated normal shutdown.