jif-oai 27e67a8c2a feat: add turn lifecycle contributors (#22480) ...

## Why

Extensions can already contribute prompt, tool, turn-item, and
thread-lifecycle behavior, but there was no explicit host-owned hook for
per-turn setup and cleanup. That makes extension-private turn state
awkward: an extension either has to stash it outside the turn lifecycle
or depend on core runtime objects.

This adds a small turn lifecycle boundary. Extensions receive stable
identifiers plus the existing session, thread, and turn `ExtensionData`
stores, while core keeps owning task scheduling, cancellation, and turn
teardown.

## What Changed

- Added `TurnLifecycleContributor` with `on_turn_start`, `on_turn_stop`,
and `on_turn_abort` callbacks in `codex-rs/ext/extension-api`.
- Added typed `TurnStartInput`, `TurnStopInput`, and `TurnAbortInput`
payloads that expose `thread_id`, `turn_id`, `session_store`,
`thread_store`, and `turn_store`.
- Registered and re-exported turn lifecycle contributors through
`ExtensionRegistry` and `ExtensionRegistryBuilder`.
- Wired `Session` to emit turn start, stop, and abort callbacks from the
existing turn/task lifecycle paths.
- Carried the turn-scoped `ExtensionData` through `RunningTask` and
`RemovedTask` so stop/abort callbacks receive the same turn store
created at turn start.

## Verification

- Not run locally.

2026-05-13 13:47:27 +02:00

..

compact.rs

feat: add remote compaction v2 Responses client path (#20773)

2026-05-04 14:15:01 +02:00

lifecycle.rs

feat: add turn lifecycle contributors (#22480)

2026-05-13 13:47:27 +02:00

mod_tests.rs

Update models.json (#18586)

2026-04-20 10:27:01 -07:00

mod.rs

feat: add turn lifecycle contributors (#22480)

2026-05-13 13:47:27 +02:00

regular.rs

[codex] Add token usage to turn tracing spans (#19432)

2026-04-28 11:41:32 -07:00

review.rs

[codex] Remove unused event messages (#20511)

2026-04-30 20:03:26 -07:00

user_shell.rs

[codex-analytics] add item lifecycle timing (#20514)

2026-05-04 22:33:20 +00:00