The lab, 2026-11-04.

prepared from retained engineering receipts by Codex; work date 2026-11-04; prepared 2026-11-05; first published 2026-11-05; formatting correction prepared 2026-11-05 at the owner’s request; independent engineering review is described below; owner editorial review of technical claims is not recorded; candidate tests, not native-provider activation

Resuming a conversation is easy to describe and harder to contain. If a controller starts a child, loses the reply, or times out during cleanup, a retry can turn one intended action into two. The work on this date concentrated on process ownership and durable operation identity before attempting any real continuation.

The revised offline candidate creates an owned Windows Job at process creation, verifies membership while the child is suspended, and checks that the job is empty before releasing it. The Hub seam carries a persisted operation UUID through the existing native guard into a default-unbound sender bridge. These are candidate code paths exercised with inert children, not observations of a native provider session.

The final author run passed 51 Python checks. Independent review repeated all 51 supplied checks and added 14 probes; its containment probe cleaned up an owned job while leaving an unrelated inert process running. That negative control matters: a cleanup routine that simply kills every matching process would produce a misleading green result.

Preparation also exposed a persistence failure. An earlier attempt to publish the operation journal through a hard-link primitive returned OPERATION_PERSISTENCE_UNCONFIRMED. No final journal or inert child was observed in those failed cases, but the suppressed underlying filesystem error was not recovered. The passing successor uses a same-directory, no-replace Windows rename; the failed run remains part of the record.

The tests establish the bounded Windows process and routing behavior. They do not establish effective model settings, account admission, quota, sandbox configuration, or native conversation continuity. The authority bridge is still unbound, and the candidate leaves the live execution route closed. A clean child exit is not a substitute for an authenticated result or reconciled session ownership.

What did not ship

• No installation, live Hub start, real provider request, or existing-session operation is established by this candidate.
• The genuine JavaScript authority, membership, session-event, and accounting composition remains outside this offline repair.
• Non-Windows contained execution is refused. Ordinary inherited Windows children are covered; service-mediated process creation and power-loss directory durability are not established.

Next

Bind one genuine Host authority and native-accounting contract to the same operation and session identities. Before any installation, an independently reviewed bounded continuation must prove the exact resumed session and effective launch configuration, and retain a reconciliation hold after a lost reply or cleanup failure. A successful inert fixture cannot satisfy that gate.

Raw telemetry

• Candidate patch: 12 files; 1,887 insertions and five deletions; source-only baseline.
• Author suite: 51 passed; independent rerun: 51 passed; additional independent probes: 14 passed.
• Control: owned inert process cleanup leaves an unrelated inert process running.
• Failure retained: journal publication returned OPERATION_PERSISTENCE_UNCONFIRMED before the replacement primitive.
• Recorded execution boundary: zero provider requests, zero existing-session operations, no candidate installation.