Keep retained mobile planning available through refresh outages #290

Merged
timmy merged 1 commits from timmy/289-retained-planning into main 2026-08-08 10:22:07 +00:00
Owner

Summary

  • separate retained local-planning identity from freshness-gated delivery identity
  • keep Today/Later account-scoped during stale/revalidating snapshots
  • report duplicate, invalid, missing-identity, and device-storage outcomes truthfully
  • keep detail-sheet planning disabled until identity is known

Verification

  • pytest -q — 511 passed
  • rendered Chromium checks at 320x568 and 390x844 — Today persisted/reloaded and launched its session; Later persisted; 44px controls; zero horizontal overflow

Closes #289

## Summary - separate retained local-planning identity from freshness-gated delivery identity - keep Today/Later account-scoped during stale/revalidating snapshots - report duplicate, invalid, missing-identity, and device-storage outcomes truthfully - keep detail-sheet planning disabled until identity is known ## Verification - `pytest -q` — 511 passed - rendered Chromium checks at 320x568 and 390x844 — Today persisted/reloaded and launched its session; Later persisted; 44px controls; zero horizontal overflow Closes #289
timmy added 1 commit 2026-08-08 10:21:11 +00:00
fix: keep retained mobile planning available (#289)
All checks were successful
CI / lint (pull_request) Successful in 29s
CI / build-frontend (pull_request) Successful in 5s
8c4e729c4a
timmy merged commit b458dbaa78 into main 2026-08-08 10:22:07 +00:00
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#290
No description provided.