The initial probe now calls GET /api/v1/admin/ping and only enters the shell on a 2xx; 403 -> refusal, 401 -> login, 404/500/network -> a clear error state (not the shell). Tests assert the path and each outcome.
Checks: cd admin && npm test = 14 files, 189 passed; npm run build exit 0.
Maestro task: f50338c8-8b48-4e3d-9064-e20d9b32fe34 (Feature 19 - Admin PWA). Addresses feature-review HIGH F-001.
The initial probe now calls GET /api/v1/admin/ping and only enters the shell on a 2xx; 403 -> refusal, 401 -> login, 404/500/network -> a clear error state (not the shell). Tests assert the path and each outcome.
Head: 0adaed553d8b22b80716fe733d542e00c5771223
Base: feature/24ce7ebf-... @ 487bc00
Checks: cd admin && npm test = 14 files, 189 passed; npm run build exit 0.
The initial authorization probe called the nonexistent /api/v1/children
and treated every non-403 outcome as success, so a 404 rendered the
admin shell. Probe the admin plane's GET /api/v1/admin/ping instead and
enter the shell only on a 2xx: 403 shows the refusal, 401 keeps the
login flow, and any other status or network failure shows a new
probe-error screen with Retry and Sign out.
Task: f50338c8-8b48-4e3d-9064-e20d9b32fe34
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Maestro task: f50338c8-8b48-4e3d-9064-e20d9b32fe34 (Feature 19 - Admin PWA). Addresses feature-review HIGH F-001.
The initial probe now calls GET /api/v1/admin/ping and only enters the shell on a 2xx; 403 -> refusal, 401 -> login, 404/500/network -> a clear error state (not the shell). Tests assert the path and each outcome.
Head:
0adaed553dBase: feature/24ce7ebf-... @
487bc00Checks: cd admin && npm test = 14 files, 189 passed; npm run build exit 0.
Independent Codex gpt-5.6-terra review completed for this exact commit.