Eddie Chen cfc946f4e1 Expose and persist turn lineage across the app server (#51415) ...

## Why

Clients starting delegated work need to attribute descendant turns to the original turn and retain that attribution through completion and history reads.

## What changed

- Accept optional `parentTurnId` and `rootTurnId` in `turn/start`, and expose `rootTurnId` on returned turns and lifecycle notifications.
- Default new turns to their own root when none is supplied. Preserve the active turn's root when steering, ignoring incoming lineage fields.
- Carry root IDs through completion, interruption, recovery, and fork boundaries, and persist them for paginated history reads. Leave unknown roots null in older history.
- Update protocol schemas and generated TypeScript and Python bindings.

## Testing

Extend coverage for default and explicit roots, steering without changing lineage, interrupted and recovered turns, history reads after restart in both history modes, nested fork pagination, and compatibility with older database writers.

GitOrigin-RevId: f1a570a12bd11742929fd2e8b017e5d35aa07dcb

2026-10-06 16:56:39 +00:00

..

python

Expose and persist turn lineage across the app server (#51415)

2026-10-06 16:56:39 +00:00

python-runtime

[codex] Add independent beta release for the Python SDK (#24828)

2026-05-27 17:57:51 -07:00

typescript

Add per-turn Cyber access program selection to exec and the SDK (#49939)

2026-10-01 08:57:53 +00:00