Keep retained mobile planning available through refresh outages #290

2026-08-08T10:21:10Z

timmy commented

2026-08-08 10:21:10 +00:00

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 )

CI / build-frontend (pull_request) Successful in 5s

Details

CI / lint (pull_request) Successful in 29s

Details

8c4e729c4a

timmy merged commit b458dbaa78 into main

2026-08-08 10:22:07 +00:00

timmy referenced this issue from a commit

2026-08-08 10:22:08 +00:00

Merge pull request 'Keep retained mobile planning available through refresh outages' (#290) from timmy/289-retained-planning into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#290