jif 828d7476a0 linearize history output normalization (#28309) ...

## Why

When we prepare the conversation history, every tool call needs a
matching output.

Before this change, we scanned the full history again for every call. In
a tool-heavy conversation, that makes the work `O(items x calls)`, or
`O(n^2)` in the worst case.

## What

Scan the history once and collect the IDs of existing outputs. Then each
call can check its ID with an expected `O(1)` lookup.

The full normalization step is now expected `O(n)`. The output order and
missing-output behavior stay the same.

## Performance

Based on local rollout traces, one tool-heavy session reached roughly
17,050 transcript items with about 4,292 tool-call items. On a history
of that shape, the old `calls x items` scan does about 73.2 million
membership checks, while the new pass does about 21.3 thousand set
inserts/lookups. That is roughly 3.4k times less membership work in this
normalization step.

## Validation

- `just test -p codex-core normalize_` (19 passed)

828d7476a0 · 2026-06-15 18:26:34 +02:00

History

..

history_tests.rs

[codex] Compact when comp_hash changes (#27520)

2026-06-11 04:11:26 +00:00

history.rs

[codex] Remove remote compaction failure log (#27106)

2026-06-08 19:23:35 -07:00

mod.rs

[codex] Remove remote compaction failure log (#27106)

2026-06-08 19:23:35 -07:00

normalize.rs

linearize history output normalization (#28309)

2026-06-15 18:26:34 +02:00

updates.rs

Deprecate TurnContext cwd and resolve_path (#22519)

2026-05-13 11:15:25 -07:00