pakrym-oai f476338f93 Move apply-patch file changes into turn items (#20540) ...

## Why

Apply-patch file changes are now part of the core turn item stream, so
v2 clients can consume the same first-class item lifecycle path used by
other turn items instead of relying on app-server-specific remapping
from legacy patch events.

## What changed

- Added a core `TurnItem::FileChange` carrying apply-patch changes and
completion metadata.
- Updated the apply-patch tool emitter to send `ItemStarted` /
`ItemCompleted` with the new `FileChange` item while preserving legacy
`PatchApplyBegin` / `PatchApplyEnd` fan-out.
- Updated app-server v2 conversion to render the new core item directly
and stopped `event_mapping` from remapping old patch begin/end events
into item notifications.
- Kept thread history reconstruction based on the existing old
apply-patch events for rollout compatibility.

## Verification

- `cargo test -p codex-protocol -p codex-app-server-protocol`
- `cargo test -p codex-core --test all
apply_patch_tool_executes_and_emits_patch_events`
- `cargo test -p codex-app-server bespoke_event_handling`

2026-05-01 08:47:18 -07:00

..

schema

feat: Track local paths for shared plugins (#20560)

2026-05-01 00:50:12 -07:00

src

Move apply-patch file changes into turn items (#20540)

2026-05-01 08:47:18 -07:00

tests

chore: clean up argument-comment lint and roll out all-target CI on macOS (#16054)

2026-03-27 19:00:44 -07:00

BUILD.bazel

feat: vendor app-server protocol schema fixtures (#10371)

2026-02-01 23:38:43 -08:00

Cargo.toml

Refactor config loading to use filesystem abstraction (#18209)

2026-04-17 00:51:21 +00:00