stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Keep the confirmed Week Ahead overview available offline #1218

New Issue
Closed
opened 2026-08-21 10:22:27 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-21 10:22:27 +00:00
Member
Copy Link

Problem

The mobile shell is offline-capable, but a successfully synced Week Ahead becomes unreadable as soon as GET api/v1/week fails. frontend/week-plan.js retains only pending writes and removes them after sync, so the new read-first seven-day overview has no confirmed fallback.

User impact

Operators should be able to inspect what is next, titles, daily load, and overload state while commuting or during a forge outage without risking edits against an unchecked revision.

Acceptance

  • Cache the last confirmed account-scoped Week Ahead and minimal display metadata after a successful read/save.
  • Network-first load falls back to that snapshot with a visible refresh time and touch-safe Retry.
  • Snapshot mode is explicitly read-only: no edit, capacity-import, confirm, or write controls.
  • Pending offline edits keep precedence and existing sync behavior.
  • Retry restores live data and editing after reconnect.
  • Another account cannot read the snapshot; normal private-device purge removes it.
  • Behavioral controller/workflow tests and rendered mobile release tests cover 320x568 and 390x844 without overflow.

Historical issue/PR title review found no confirmed-read cache. #1180 covered pending offline writes; #1216 added the online read-first overview.

## Problem The mobile shell is offline-capable, but a successfully synced Week Ahead becomes unreadable as soon as `GET api/v1/week` fails. `frontend/week-plan.js` retains only pending writes and removes them after sync, so the new read-first seven-day overview has no confirmed fallback. ## User impact Operators should be able to inspect what is next, titles, daily load, and overload state while commuting or during a forge outage without risking edits against an unchecked revision. ## Acceptance - Cache the last confirmed account-scoped Week Ahead and minimal display metadata after a successful read/save. - Network-first load falls back to that snapshot with a visible refresh time and touch-safe Retry. - Snapshot mode is explicitly read-only: no edit, capacity-import, confirm, or write controls. - Pending offline edits keep precedence and existing sync behavior. - Retry restores live data and editing after reconnect. - Another account cannot read the snapshot; normal private-device purge removes it. - Behavioral controller/workflow tests and rendered mobile release tests cover 320x568 and 390x844 without overflow. Historical issue/PR title review found no confirmed-read cache. #1180 covered pending offline writes; #1216 added the online read-first overview.
timmy was assigned by rockachopa 2026-08-21 10:22:27 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
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#1218
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?