felixxia-oai 99d66aa1c5 Preserve acceptance order in retained thread context (#42770) ...

## Why

Queued prompts and `request_user_input` answers can be persisted in a different
order from when the host accepted them. Using persistence order can therefore
reorder retained instructions during replay or apply the wrong rollback
boundary.

## What changed

- Reserve an acceptance sequence for user prompts and elicitation responses
  when retained thread context is enabled.
- Persist that sequence with user-message metadata and verified answers, and
  use it when ordering, bounding, replaying, and rolling back retained context.
- Keep events without acceptance metadata compatible with legacy recording
  order.

## Testing

- Cover delayed queued-input recording, rejected prompts, checkpoint replay,
  compaction, rollback migration, and legacy retained-context behavior.

GitOrigin-RevId: 42d24465cc2033bc51c0c2da79d3c0884a8ad98a

2026-09-04 13:50:27 +00:00

..

schema

Preserve acceptance order in retained thread context (#42770)

2026-09-04 13:50:27 +00:00

scripts

Format Python scripts across the repository (#42109)

2026-09-01 17:47:29 +00:00

src

Deprecate detached review delivery (#42602)

2026-09-03 19:36:11 +00:00

BUILD.bazel

Add a cacheable Bazel app-server schema bundle (#42174)

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

Cargo.toml

Keep credentials out of app-server logs (#39993)

2026-08-21 19:04:32 +00:00