jif-oai de513a83f3 chore: move memory prompt builder into extension (#24558) ...

## Why

The memories extension now owns the read-path developer instructions it
injects at thread start. Keeping that prompt builder and template in
`codex-memories-read` left the extension depending on a helper crate for
extension-specific prompt assembly, and kept async template/truncation
dependencies in the read crate after the remaining read surface no
longer needed them.

## What changed

- Moved `prompts.rs`, its tests, and `templates/memories/read_path.md`
from `memories/read` into `ext/memories`.
- Wired `MemoryExtension` to call the local prompt builder and added the
moved templates to `ext/memories/BUILD.bazel` compile data.
- Removed the now-unused prompt export and prompt-related dependencies
from `codex-memories-read`.

## Testing

- Not run locally.

2026-05-26 11:53:47 +02:00

..

extension-api

Expose conversation history to extension tools (#23963)

2026-05-22 01:11:47 +00:00

goal

[wip] goal shift (#23858)

2026-05-26 11:22:18 +02:00

guardian

Make extension lifecycle hooks async (#23291)

2026-05-18 13:53:58 +02:00

memories

chore: move memory prompt builder into extension (#24558)

2026-05-26 11:53:47 +02:00