# Issue 21772 evidence index

Base: `8d3b061121`. Head verified locally: `a64184c7d3497a17a19a77c3d46f7bac521bc1e6`.

Environment: Linux x64, machine fs-34. Lead's integrated real-app run: browser 1280×800, no emulation, isolated seeded data. Persisted provider/model: Claude Agent Opus 5.5 (`claudeAgent`, `claude-opus-5-5`, fastMode=false).

- [Before runtime transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/29c3aa3468274d4a/before-runtime.txt): final child canary did not reach parent on base.
- [After runtime transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/7cc8f2df82d926af/after-runtime.txt): 5 runs, 2 completed tasks, 21 turn items; exact correlated IDs and UTC timestamps, original and follow-up completion notifications, delivered follow-up result, parent acknowledgement. Read directly from isolated SQLite using mode=ro/query_only in a single read transaction. No auth data or unrelated threads exported; local provider output path sanitized.
- [Red regression proof](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/bd5920cd2a9ba10f/red-test.txt): existing lead-provided failure transcript; not rerun by capture agent.
- [Proof auditor requirements](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/74458559ed218f89/proof-audit-pass1.md).

Observed AFTER: child run1 requested 10:20:41.084; WAITING at 10:20:48.055; original parent completion notification 10:21:46.810; provider background wake and child run2 10:21:46.915 with non-null distinct delegatedTaskId; child CANARY 10:21:48.626; follow-up task completed 10:21:49.441; follow-up parent notification 10:21:52.571; RECEIVED acknowledgement 10:21:58.653. All 2026-10-22 UTC. Both task completionDelivery states are delivered.

Qualification: parent WAITING acknowledgement at 10:21:51.620 follows the child wake. Follow-up task is owned by parent run6, the original-result continuation, rather than delegation run5. This proves automatic final delivery in the observed sequence, but does not establish the auditor's stricter acknowledgement-before-wake/original-owning-run ordering. Do not claim that stricter S1/S3 sequence from this recording.

No task_status, manual resume, or thread-send calls in the 21 relevant turn items; one initial delegate_task plus native sleep 60. Interrupted child Repro21772 AFTER excluded. Lead reports no restart during 10:20:30–10:22:00 and tracked same server PID 1576532; read-only process inspection confirms it started 10:18:19 and remains running. Historical PID continuity is lead-supplied, not independently monitored by this capture agent. Captured runs contain no restartContinuationOfRunId.

Server-only exemption: diff changes only Orchestrator.ts and DelegatedCompletionDelivery.test.ts. Zero render paths changed. What else changed in rendering: none. Render fixture rows 0/0; unverified render rows none. No additional viewport/provider matrix required by proof auditor. No browser/server/test execution, source edits, commits, forge writes, or pushes by evidence capture. Files saved only under /tmp/issue-21772; public uploads authorized by brief.

FRICTION evidence ordering | persisted original-result acknowledgement overlaps child wake; follow-up ownership is parent run6 | retain exact timestamps/IDs and obtain auditor acceptance or a separately authorized run for stricter ordering; never relabel the sequence.

FRICTION restart provenance | SQLite cannot independently certify continuous process lifetime | preserve lead's tracked PID log and label its provenance explicitly.