@@ -67,6 +67,42 @@ area asserts on source text, which cannot catch a rotation site that forgets a s
67672 . HTTP 429 rotation: assert ` replayOAuthCredentialSnapshot ` names the rotated account.
68683 . Cursor sidecar 429: assert ` _cursorConversationId ` does not survive the rotation.
6969
70+ ## Independent verification (2026-08-27)
71+
72+ A second read-only audit checked every claim above against ` dev ` rather than trusting
73+ the first pass. Two things changed.
74+
75+ ** Confirmed.** The stale snapshot is real: ` applyFailoverSnapshot ` never updates
76+ ` sentOAuthSnapshot ` , and ` forceRefreshOAuthAccessSnapshot ` refreshes the SNAPSHOT's
77+ account (` src/oauth/index.ts:500 ` ), which after a rotation is still A. The
78+ three-site asymmetry is real too, exactly as tabled above. Generic 429 failover never
79+ promotes the active account, so the active-credential helper still names A.
80+
81+ ** Corrected.** The 429-then-401 cross-origin send is NOT reachable on today's control
82+ flow, so the table above overstated the consequence. Copilot Responses models take an
83+ early passthrough return that has no generic 429 rotator at all, and in the HTTP
84+ recovery loop the 401 handler sits ABOVE the 429 rotator while the 429 branch does not
85+ ` continue recovery ` - so a 401 after rotation falls out of the loop and is returned as
86+ an upstream error rather than re-entering the refresh. The runTurn and sidecar paths
87+ never re-enter those 401 blocks either.
88+
89+ That reframes the phase without weakening it. What exists today is latent identity
90+ drift; the missing ` continue recovery ` is an ACCIDENTAL guard, not a designed one.
91+ Adding that continue - a plausible future improvement to 429 recovery - would activate
92+ the defect. So the fix order matters: rebind identity inside ` applyFailoverSnapshot `
93+ FIRST, and only then consider making 429 recovery continue.
94+
95+ The audit also named the specific pairing that would leak if the 401 handler did run:
96+ not the allowlist itself, but the transport fallback that drops to ` provider.baseUrl `
97+ when the refreshed account carries no allowlisted origin of its own. After a rotation
98+ that base URL is B's.
99+
100+ Test placement, from the same audit: ` tests/generic-oauth-failover.test.ts ` already
101+ source-asserts the three ` applyFailoverSnapshot ` sites, and there is no Copilot
102+ 429-then-401 coverage anywhere. The behavioral cases belong beside
103+ ` tests/adapter-event-oauth-failover.test.ts ` and
104+ ` tests/server-xai-oauth-401-replay.test.ts ` .
105+
70106## Boundary
71107
72108This is an authentication/credential surface. ` MAINTAINERS.md ` requires explicit
0 commit comments