Q3 owning versioned native lifecycle, 1705

Run: scratch/runs/20261109-q3-versioned-caller-arena-progress-1705/. Git base plus small binary patches retain source recovery; no source, media or module archive is used.

The published1655 staged caller alone did not integrate the retained owning Python lifecycle. Its actual prelaunch rejected the published Redline pin, and the retained runtime still forced the historical composition and preload argv. An explicit q3-native-lifecycle-foreign-v1 preparation option now requires both the existing checkpoint selector and the published foreign selector. It authenticates the retained1585 runtimes, generates phase wrappers, routes their actual Node command through the independently authenticated staged CLI, and binds the generated checkpoint caller to the phase's actual output directory. The wrappers retain the original lock, supervisor, identity, finite browser and cleanup deadlines. Repository resolution supports nested run directories.

The foreign prelaunch branch checks four fixed published foreign hashes. Other composition providers keep their original pins. Its changed Python provider hash is accepted only by the explicit foreign selector; historical/default and legacy checkpoint routes continue to refuse current drift. The versioned runtime installs the original pointer, input diagnostic and wire hooks after binding the genuine consumer and installing the authenticated composition. There is no foreign-provider filesystem substitution in the positive path.

Validation: actual preparation CLI, both actual Python prelaunch/custody/Node consumer preflights with Git unavailable, kernel drains and separate parent EOF; generated owning-caller failure/cancellation cases; staged provider read refusals; 27 foreign closure controls; seven command-boundary cases; nine screenshot/socket cases; owning launch-client controls; and the locked build. The consumer's existing DRIVER_PREFLIGHT exit prevents Chrome creation in offline tests. These results do not establish native readiness or browser EOF. Initial harness errors and the retained depth defect are preserved as failures.

The final implementation commits are 2af24dba1 and 3ed2ce544, both published with successful strict-SSH pull/push. The second also routes the independent retained physical drain to the actual phase output; its generated-program regression checks the unchanged physical and kernel assertions. The final manifest has 942 providers and records exact Git 3ed2ce54496860a39efa1eed500d1210dbfd69e0.

Native fixture and first original-controller blocker

Before allocation, the exact Redline1635 API reported ARCHIVED with completed unforced stop_e0bd4a87ad595fc7. Its genuine final publication/release and independent SHA/size/CRC reread confirmed 12/12 reaps, physical absence, no profile, FD holders or locks, and separate parent EOF. Its unpublished ports remain explicitly without an independent numbered-port connection probe.

The new independent immutable 25-minute UUID watchdog was observable and heartbeating before allocation. The single new box was bx_tg6jmkr8, UUID 00af27f6-cc90-46c4-86e2-29793256e2dc, initial expiry 2026-11-09T16:16:16.990Z. Both actual remote Python prelaunch import gates passed before the single native generated fixture/checkpoint invocation.

The fixture passed its negative controls, actual WebGL presentation/capture, ACK0 and actual owning-renderer Enter held-high/released-zero check. Its native checkpoint published at 2026-11-09T15:52:50.486Z within the existing bounds. The planned owning cancellation passed all three distinct remote parent waits with separate stdout/stderr EOF and 170/170 actual kernel reaps. Independent physical inspection confirmed ports 44787/42553 closed, no profile, runtime FD holders or input writer lock, and the runtime lock drained. Normal browser-close EOF remains UNKNOWN; kernel reaping does not establish it.

All existing fixture/checkpoint prerequisites passed, admitting one original. The retained local interactive.py parent then failed at line 8 with PermissionError: [Errno 1] Operation not permitted while registering stdin with its epoll selector. This worker should have preflighted that execution environment before spawning its child. The parent spawned the Python caller before the exception, but recorded no actual child wait: that wait remains UNKNOWN. No local original launch claim or remote original claim, runtime identity, kernel arm, output directory or runtime process was observed. The first process census matched its own diagnostic source text; the separate exact-argv census excludes the observer and found no original runtime or FD holders. That first census is not promoted as runtime presence or absence.

The selector exception was terminal. No relaunch, later input, capture, screenshot retry or deadline extension was attempted. There is no original arena screenshot, movement/firing result, or resolution of the historical screenshot stall. The concrete next blocker is preflighting the local owning controller's stdin and ensuring its parent waits in a finally path before any separately authorized new original attempt.

All 78 unique native fixture artifacts were retrieved and independently SHA/size checked with gzip CRC before delegated normal shutdown. Empty or invalid gzip sources are preserved and excluded from proof. Final box state: ARCHIVED, archiveAfter:null, expiresAt:NOT_RETURNED. Stop receipt stop_1f93513fb84c097d completed unforced without error at 2026-11-09T15:55:15.121Z. The watchdog actually joined with status 0 and separate stdout/stderr EOF; its lifecycle parent also returned 0 and released the lock. Free /home stayed above 1.5 GB. Completed owned test duplicates were losslessly compressed with independent SHA/size/CRC verification and recovery recipes. No new agents/workers, public deployment or inherited-box mutation.