Confirm + remediate Azure repo access gap (from #2892 standup)

## Summary

During the 2026-08-15 #2892 standup an Azure repo access gap was surfaced.
As of the 2026-08-16 pre-roll-call check there is no confirmed resolution or
named owner. This issue tracks it to verified closure.

## Scope

1. Verify current Azure repo access state — confirm who/what lost access and when
2. Restore correct access if still broken
3. Document root cause and the fix applied

**Out of scope:** the application-layer #2892 defect (handled separately via the
DevAuthBypassGuardTests fix committed to main).

## Acceptance criteria

- [ ] Access state confirmed (working or restored) with evidence
- [ ] Root cause documented as a comment on this issue
- [ ] Zero contributor/CI blockage attributable to this gap after closure
- [ ] Issue closed only after access is verified — do not assume resolved

## Owner / tracking

- **Owner:** Thor (infrastructure/access domain)
- **Tracker:** Fury — reports disposition at 14:00 UTC roll-call 2026-08-16

## Timeline

Must be confirmed or restored before end of business 2026-08-17 to avoid
Monday contributor/CI blockage.

## Evidence

- 2026-08-16 11:46 tick: `#2892 fix plan reviewed and shipped` confirms the
code fix is separate from this infrastructure/access condition
- Pepper escalation 2026-08-16: gap 'not confirmed resolved or assigned to an
owner' ahead of 14:00 UTC roll-call
- No telemetry or log confirming current Azure repo access state available as
of issue creation

Start with the Azure repo access state described in the Scope and confirm who or what lost access and when, using evidence. Then verify or restore access, document the root cause and fix in a comment, and confirm no contributor or CI blockage remains before closure.

Written by the indexing model from the issue text.