cooper-oai 0c58612c3c Fix authentication for git-attribution settings requests (#60035) ...

## Why

Git-attribution settings requests need to honor runtime authentication for their destination. Repeated authorization failures after a credential refresh must also let world-state contribution finish.

## What changed

- Use the thread's `ProviderAuthContext` credentials and runtime authentication when available.
- Bind the settings client's network policy to the authenticated account and select authentication through the runtime-aware backend client.
- Stop policy resolution after an unsuccessful settings lookup or timeout instead of restarting it when credentials changed during recovery.

## Testing

Add app-server coverage for `dual_header` and `assertion_only` authentication with default and custom destinations, including attribution instructions in model input. Add a regression test verifying that repeated `401` responses trigger only one credential refresh and omit attribution instructions.

GitOrigin-RevId: 4824bde7d9ec11c241f1caebc754d203dbb0480c

2026-11-07 02:09:31 +00:00

..

src

Fix authentication for git-attribution settings requests (#60035)

2026-11-07 02:09:31 +00:00

BUILD.bazel

Add the git attribution extension (#34769)

2026-07-22 15:19:15 +00:00

Cargo.toml

Fix authentication for git-attribution settings requests (#60035)

2026-11-07 02:09:31 +00:00