ningyi-oai 1715e55076 Bind direct tool-call metadata to invocation outputs (#45185) ...

## Why

Direct tool-call records need to stay associated with the invocation that produced each output, including when call IDs are reused. Completeness must describe the recorded call inventory, independently of tool success.

## What changed

- Attach direct-call records to outputs before they enter history, and set `tool_calls_complete` when the invocation's arguments are fully recorded.
- Bound pending recordings and retained metadata, release reservations on completion or cancellation, and invalidate pending records when capture is disabled.
- Apply request budgets to direct metadata and strip it from inference and compaction inputs when capture is disabled.
- Remove executed-call metadata from app-server raw response notifications and exclude its size from Guardian history retention budgets.
- Track call IDs that bypass dispatch so their reuse cannot incorrectly establish Code Mode completeness.

## Testing

Add regression coverage for direct-call attribution, malformed calls, metadata budgets, cancellation, configuration changes, compaction, notification filtering, and Guardian context isolation.

GitOrigin-RevId: 2ebd39c7f141d04788736491495109841656b4c0

2026-09-13 06:53:20 +00:00

..

configuration_update_tests.rs

Support durable reasoning configuration updates (#42328)

2026-09-02 18:52:44 +00:00

configuration_update.rs

Support durable reasoning configuration updates (#42328)

2026-09-02 18:52:44 +00:00

executed_tool_calls_tests.rs

Harden Code Mode tool-call completeness tracking (#44472)

2026-09-10 08:57:35 +00:00

executed_tool_calls.rs

Bind direct tool-call metadata to invocation outputs (#45185)

2026-09-13 06:53:20 +00:00

item_metadata_tests.rs

Preserve content item kinds in message metadata (#40174)

2026-08-23 02:50:45 +00:00

item_metadata.rs

Preserve content item kinds in message metadata (#40174)

2026-08-23 02:50:45 +00:00