Repository navigation
Mobile outage recovery and attributed maintenance status (JVNAUTOSCI-2758) - #665
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds mobile outage recovery using the existing health decision, a public-only service-worker fallback, namespace-bound unsent draft recovery and an operator-bound maintenance ETA publisher. Previously loaded clients can reload during backend downtime and return to the authenticated app without replaying prompts.
The outage and push features now share one service-worker registration, preserving notification handlers while caching only four public fallback assets. The UI retains the PWA manifest and presents maintenance source, freshness and local return-time estimates without inventing an ETA.
Validation: 22 targeted PDM backend tests and 29 frontend outage/health/push tests pass. Authenticated Chromium acceptance verified controlled backend stop/restart, transient non-takeover, reload/reopen, device-offline wording, reauthentication and recovered drafts with zero send/generate effects. Final combined-worker browser acceptance verifies notification-disable handling plus outage recovery in three mobile viewports and public-only cache contents. Physical installed phones and public OAuth were not tested.
The independent production-status blocker is resolved: checksum-verified operator receipts establish a separate read-only public route, publisher bindings, readiness-based clearing and rollback; fresh anonymous GET returned 200 no-store JSON. Private application routes remain protected. No public outage was induced. Evidence and exact tested revisions are in docs/engineering/jvnautosci_2758_outage_candidate_2026-09-12.md and retained under .run/outage-resume/ and .run/outage-release/.
Merge decision changes — retained authenticated acceptance, final shared-worker checks and repaired production status binding support merge. No demonstrated material regression remains on the affected path. Controller deployment/read-back follows merge; this PR does not claim deployment. Cold uncached visits, cache eviction and expired Cloudflare sessions remain explicit limits.
JVNAUTOSCI-2758; native execution task #V#task_agent_2933920b7da4ff15bf3db11d3f7e9fb5. Canonical tracking updates and deployment belong to the receiving controller.