jif-oai 436c0df658 extension: wire extension registries into sessions (#21737) ...

## Why

[#21736](https://github.com/openai/codex/pull/21736) introduces the
typed extension API, but the runtime does not yet carry a registry
through thread/session startup or give contributors host-owned stores to
read from. This PR wires that host-side path so later feature migrations
can move product-specific behavior behind typed contributions without
adding another bespoke seam directly to `codex-core`.

## What changed

- Thread `ExtensionRegistry<Config>` through `ThreadManager`,
`CodexSpawnArgs`, `Session`, and sub-agent spawn paths.
- Wire `ThreadStartContributor` and `ContextContributor`
- Expose the small supporting surface needed by non-core callers that
construct threads directly, including `empty_extension_registry()`
through `codex-core-api`.

This PR lands the host plumbing only: the app-server registry is still
empty, and concrete feature migrations are intended to follow
separately.

2026-05-11 11:38:18 +02:00

..

src

extension: wire extension registries into sessions (#21737)

2026-05-11 11:38:18 +02:00

BUILD.bazel

Add codex-core public API listing (#20243)

2026-04-29 22:58:08 +00:00

Cargo.toml

extension: wire extension registries into sessions (#21737)

2026-05-11 11:38:18 +02:00