jif-oai 01a8bf0ae3 Add memory tool call metrics to memories extension (#24583) ...

## Why

The memories extension now receives a metrics exporter, but the useful
extension-owned signal is the memory tool call itself: which operation
ran, which memory area it touched, whether the backend call succeeded,
and whether the result was truncated.

## What changed

- Added the `codex.memories.tool.call` counter in
`ext/memories/src/metrics.rs`.
- Emit that counter from `memories/add_ad_hoc_note`, `memories/list`,
`memories/read`, and `memories/search` after backend execution.
- Tag each call with `tool`, `operation`, `scope`, `status`, and
`truncated`.
- Pass the existing `MetricsClient` through the memories extension into
the tool executors; tests use `None`.

## Verification

- `just test -p codex-memories-extension`

2026-05-26 15:27:51 +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

Add memory tool call metrics to memories extension (#24583)

2026-05-26 15:27:51 +02:00