Closes #1411
## User flow
- retry a failed progressive live snapshot without reload
- refresh lightweight My Work at server freshness deadlines with revision tokens
- coalesce timer, online, and foreground recovery into one active request
- transfer the latest snapshot and selected queue once, then clean up timers/listeners
## Verification
- RED: retry test failed because no retry timer was scheduled
- RED: lifecycle test failed because online/visibility recovery was absent
- focused: 134 passed
- full suite: 2678 passed, 24 skipped
- packaged mobile release journey: 7 passed at 320×568 and 390×844
- runtime + work-core: 43,357 bytes gzip (150 KiB budget)
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 #1411
User flow
Verification