[Yash-Singh1]

What Changed

Delegated task status now returns to running when its child starts follow-up work. When that run finishes, T3 updates the task with the latest result and delivers it to the parent. A follow-up cancelled before it starts leaves the previous result intact.

Why

A delegated task stayed completed after its child began working on new input. This change keeps the parent task status in sync with the child and allows each finished follow-up result to reach the parent once.

Checklist

• This PR is small and focused
• I explained what changed and why

Closes #13490

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ No successful main baseline artifact is available yet. This run establishes the initial measurement.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	—	4.9 KiB	—	6.8 KiB	✅
Codex	Thread snapshot wire	—	3.7 KiB	—	4.9 KiB	✅
Codex	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Codex	Live turn WebSocket decoded	—	20.4 KiB	—	29.3 KiB	✅
Codex	Live turn messages	—	2	—	8	✅
Claude	Total thread wire	—	4.9 KiB	—	6.8 KiB	✅
Claude	Thread snapshot wire	—	3.7 KiB	—	4.9 KiB	✅
Claude	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Claude	Live turn WebSocket decoded	—	20.8 KiB	—	29.3 KiB	✅
Claude	Live turn messages	—	2	—	8	✅

Baseline: unavailable · PR result: 8ecdf69 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 106.1 KiB
• Claude decoded thread snapshot: 106.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This server-side change updates delegated-task state transitions, result delivery, event ordering, and startup recovery across several production orchestration paths. Although the intent is focused and the behavior is extensively tested, the state-machine and delivery changes have enough runtime blast radius to warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[juliusmarminge]

Note

This comment is posted by Julius' dot

Closing under prior approval. The maintainer ruling on #13490 identifies follow-up wakes as a change to the published-result contract. This PR enables those wakes and replaces the published task summary, but no direction-and-scope approval is linked.

Please agree on whether follow-ups should wake the parent and whether the original summary should stay stable, then link that approval for reconsideration.