jif-oai c5bd131567 feat: add turn_id and truncation_policy to extension tool calls (#23666) ...

## Why

Extension-owned tools currently receive a stripped `ToolCall` with only
`call_id`, `tool_name`, and `payload`.
That makes extension work that needs turn-local execution context
awkward, especially web-search extension work that needs the active
`truncation_policy` at tool invocation time.

Reconstructing that value from config or `ExtensionData` would be
indirect and could drift from the actual turn context, so the cleaner
fix is to pass the needed turn metadata directly on the extension-facing
invocation type.

## What changed

- added `turn_id` and `truncation_policy` to `codex_tools::ToolCall`
- populated those fields when core adapts `ToolInvocation` into an
extension tool call
- added a focused adapter test that verifies extension executors receive
the forwarded turn metadata
- updated the memories extension tests to construct the richer
`ToolCall`
- added the `codex-utils-output-truncation` dependency to `codex-tools`
and refreshed lockfiles

## Testing

- `cargo test -p codex-tools`
- `cargo test -p codex-memories-extension`
- `cargo test -p codex-core passes_turn_fields_to_extension_call`
- `just bazel-lock-update`
- `just bazel-lock-check`

2026-05-20 20:14:41 +02:00

..

extension-api

feat: expose turn-start metadata to extensions (#23688)

2026-05-20 15:54:29 +02:00

goal

feat: account active goal progress in the goal extension (#23696)

2026-05-20 18:36:37 +02:00

guardian

Make extension lifecycle hooks async (#23291)

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

memories

feat: add turn_id and truncation_policy to extension tool calls (#23666)

2026-05-20 20:14:41 +02:00