jif 2210380232 Resolve Guardian policy from the reviewed thread's catalog (#59913) ...

## Why

Async classification could use policy from the manager's startup catalog even when the reviewed thread had a different reviewer policy.

## What changed

Share reviewer resolution between synchronous review and async classification, using the thread's catalog and reviewer eligibility rules. Select reviewer metadata from the same catalog snapshot, filter out models unsupported by API authentication, and preserve captured parent metadata when no eligible default reviewer exists.

## Testing

Update the async classification regression test with distinct thread and manager catalog policies, asserting that the thread reviewer's policy appears in classifier instructions.

GitOrigin-RevId: 0b28644d30bda42d2cf1bd8a31de2e8f8d38e1a6

2026-11-06 13:44:03 +00:00

..

src

Resolve Guardian policy from the reviewed thread's catalog (#59913)

2026-11-06 13:44:03 +00:00

BUILD.bazel

Extract Guardian review policy into a dedicated crate (#44227)

2026-09-09 17:31:37 +00:00

Cargo.toml

Use prepared MCP owner permissions in Guardian reviews (#59028)

2026-11-03 01:41:16 +00:00