PR #20037 takeover evidence
Takeover and fresh live-verification head: a9abaa42fd0ccb4344bd2e5aa8afe31aab4e28c3
Actual merged main base: b2fa5d3e5ccb4a296fb51e569a5eb3023288e932
Normal merge preserves incoming task-status compaction and our approval guidance.
Contributor head retained: 1f7aa2b2f02ced24290cf1b677ad21b70d58df19
Clean committed source at live verification start: yes

Before: temporarily restoring both original wait predicates caused the integration
regression to return waitTimedOut=true rather than release a pending approval;
restoring exact production bytes made the same regression pass.

After main integration: 42/42 focused tests passed fresh (service33, toolkit
integration3, contracts6). Original48 in3existingfiles became41 after test
consolidation, then incoming main added one replay/compaction case:42 now.
414nettestlines removed by takeover; no new integration cases in the main merge.
Earlier R1 strengthened the existing foreign-run fixture to be truly untagged;
mutating original-run ownership failed the existing assertion and exact restoration
passed. Fixed selector/wait/delegate sections unchanged in the main merge.
Fresh merged-head scoped lint, format, contracts and server typechecks pass.
Initial server validation lacked new main math dependencies; frozen-lockfile
installation restored them (20 cached packages, no tracked dependency changes),
then all42tests and server types passed. No source workaround.
Whole change against actual main:6files,+441/-10.

REAL CODEX ACCEPTANCE, 2026-10-20T00:07:30.782Z:
- Current source server; disposable temporary data directory and Git project.
- Real installed Codex CLI0.163.0 parent and child, model gpt-6.1-sol, high reasoning.
- Parent full-access; child explicitly approval-required.
- Parent called delegate_task(mode=wait, timeoutMs=120000).
- Actual tool interval: 2026-10-20T00:07:53.951Z to 2026-10-20T00:07:59.389Z (5.438seconds).
- Parent observed approval and ended initial turn within 17611ms of launch.
- Actual result: status=running, hasPendingQuestion=false, waitTimedOut=false.
- pendingApproval contained exactly requestId, kind=command, runId.
- Test client inspected fresh live child request and the exact harmless command:
  node -e "require('node:fs').writeFileSync('approval-proof.txt','APPROVAL_FIXTURE_OK')"
- Fixture file was absent before approval; parent asked once and did not decide it.
- External client accepted through public orchestration.dispatchCommand RPC.
- Child created the expected fixture, completed APPROVAL_FIXTURE_OK.
- One normal typed completion notification, task_status read by parent,
  completionDelivery=acknowledged; parent replied COMPLETE:APPROVAL_FIXTURE_OK.
- Own server and children stopped via captured process handle after verification.

Scope limits: one-host Linux Node24 provider/API acceptance. No async approval
notice behavior, real-provider cancellation/reconnect/restart scenario, remote
relay/tunnel, web UI, Electron, Windows, macOS, iOS or Android acceptance claimed.
Deterministic integration separately covers ownership, stale request filtering,
initial retry, legacy original-run fallback, oldest approval, resolution, terminal
cleanup, cancellation and completion acknowledgement/deduplication.

Historical pre-merge harness setup notes: first bootstrap-only start inherited ambient T3 home and
ownership lock rejected it before database open (server.ts acquires ownership
first). Harness corrected to explicit CLI --base-dir and T3CODE_HOME. Second
launch exposed a verifier RPC encoding error, corrected to canonical options
array. Third launch above passed; no application-source changes for either.
Local raw evidence retained privately; this summary excludes auth/session tokens.

Fresh main-integrated run used the corrected harness and passed on its first attempt.
Prior real-provider evidence remains historical; current claims above are fresh.