jif-oai cccde930ce Move memory prompt injection to app-server extension (#22841) ...

## Why

Memory prompt injection should be owned by the extension path that
app-server composes at runtime, not by an inlined special case inside
`codex-core`. This keeps `codex-core` focused on session orchestration
while allowing the memories extension to own its app-server prompt
behavior.

## What Changed

- Registers `codex-memories-extension` in the app-server extension
registry.
- Moves the memory developer-instruction injection out of
`core/src/session/mod.rs` and into the memories extension prompt
contributor.
- Adds config-change handling so the extension keeps its per-thread
memory settings in sync after startup.
- Leaves memories read/retrieval tools unregistered for now so this PR
only changes prompt injection.
- Removes the stale `cargo-shear` ignore now that app-server depends on
the extension crate.

## Validation

Not run locally; validation is left to CI.

2026-05-15 16:19:34 +02:00

..

extension-api

Simplify tool executor and registry plumbing (#22636)

2026-05-15 11:47:54 +02:00

guardian

feat: move extension scope ids into ExtensionData (#22490)

2026-05-13 16:13:16 +02:00

memories

Move memory prompt injection to app-server extension (#22841)

2026-05-15 16:19:34 +02:00