Route approvals through the extension decision API (#43432)

## What changed

- Let approval extensions choose between cached approval, synchronous review, and a user prompt for tool and permission requests, while core enforces mandatory Guardian and fresh-review requirements.
- Carry an optional `review_reason` on Guardian assessment events and use it to trigger strict-review notifications, retaining the fallback for older events.
- Require synchronous review when cached evidence has an unusable encrypted parent compaction.

## Testing

Add regression coverage for manual prompts and cached approvals with non-UTF-8 working directories. Update approval contributors in existing tests to use the decision API.

GitOrigin-RevId: a4e66416070bdaa881daa41429c49021629f44c1
This commit is contained in:
jif
2026-09-07 11:07:28 +00:00
committed by copyberry
parent 0df39752cb
commit e1eb98461c
24 changed files with 605 additions and 250 deletions
+4
View File
@@ -204,6 +204,10 @@ pub enum GuardianReviewReason {
#[derive(Debug, Clone, Deserialize, Serialize, PartialEq, JsonSchema, TS)]
pub struct GuardianAssessmentEvent {
/// Request-scoped trigger; absent in events recorded by older clients.
#[serde(default, skip_serializing_if = "Option::is_none")]
#[ts(optional)]
pub review_reason: Option<GuardianReviewReason>,
/// Stable identifier for this guardian review lifecycle.
pub id: String,
/// Thread item being reviewed, when the review maps to a concrete item.