Persist verified user answers in Guardian thread context (#42579)

## Why

Guardian authorization reviews need host-verified `request_user_input` answers to
remain aligned with thread history across compaction, resume, and rollback.

## What changed

- Record verified question-and-answer pairs in retained thread context when
  `GuardianThreadContext` is enabled, and source both local and delegated Guardian
  review evidence from that context.
- Preserve complete answer records within the evidence budget. Mark authorization
  context incomplete when records are unavailable or oversized, and defer cached
  fast approvals in that case.
- Keep the existing runtime-only answer path for threads that do not enable the
  thread-owned context.

## Testing

- Cover answer retention through compaction and resume, removal after rollback,
  source-call eviction, oversized answers, delegated review evidence, and legacy
  behavior.

GitOrigin-RevId: 01f6f4541515434a0d00fdde318ff59f2f8bd2eb
This commit is contained in:
felixxia-oai authored and copyberry committed 2026-09-03 16:41:11 +00:00
1 parent 7a7c188682
commit 1d74c3ba1e
22 files changed
+960 -397

No files matched your search

+3 -3
View File
@@ -126,9 +126,9 @@ pub(crate) async fn build_guardian_prompt_items_with_parent_turn(
let trusted_user_inputs = session
.services
.thread_extension_data
.get::<GuardianReviewEvidence>()
.map(|evidence| evidence.user_input_fragments(history.as_ref()))
.unwrap_or_default();
.get_or_init(GuardianReviewEvidence::default)
.user_input_snapshot(history.as_ref())
.fragments;
let ComposedContext {
authorization,
transcript: transcript_entries,