fall back to the versioned cached shell for dashboard navigation responses 500/502/503/504 without hiding auth/client errors
hydrate opted-in private My Work on an initial live API outage even while the browser remains online
keep degraded actions read-only and automatically restore live mode on a healthy poll
document the outage behavior and cache upgrade
Verification
RED: the new cached-503 behavioral test failed with assert 503 == 200 before implementation
focused: 15 passed
full suite: 375 passed in 10.77s
rendered mobile (Playwright, 390x844): online=true, service worker controlled, outage snapshot visible/read-only, action disabled, no horizontal overflow
Closes #230
## What changed
- fall back to the versioned cached shell for dashboard navigation responses 500/502/503/504 without hiding auth/client errors
- hydrate opted-in private My Work on an initial live API outage even while the browser remains online
- keep degraded actions read-only and automatically restore live mode on a healthy poll
- document the outage behavior and cache upgrade
## Verification
- RED: the new cached-503 behavioral test failed with `assert 503 == 200` before implementation
- focused: `15 passed`
- full suite: `375 passed in 10.77s`
- rendered mobile (Playwright, 390x844): online=true, service worker controlled, outage snapshot visible/read-only, action disabled, no horizontal overflow
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.
Closes #230
What changed
Verification
assert 503 == 200before implementation15 passed375 passed in 10.77s