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

Queue multiple offline Week-to-Today pulls without losing intent #1249

New Issue
Closed
opened 2026-08-22 03:20:52 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-22 03:20:52 +00:00
Member
Copy Link

Product gap

Week Ahead currently persists only one pending Week-to-Today pull under stackchain.week-today-pull.v1.<account>. A second offline pull overwrites the first, so a phone operator can lose an admitted work move after reload/reconnect. The reverse Today-to-Week flow already has a bounded FIFO (#1233); #1246 only made one pull durable.

User flow

From the mobile Week Ahead overview, add two items to an active Today plan while delivery is unavailable, reload, then reconnect. Both admitted intents must reach Today exactly once in original order and disappear from Week Ahead.

Acceptance criteria

  • Persist multiple account-scoped Week-to-Today pulls as a backward-compatible bounded FIFO.
  • Admit each pull only after durable storage succeeds; optimistic Today and Week snapshots include every queued pull.
  • Replay oldest-first with at most one request in flight and rebase each remaining request on returned Today/Week revisions.
  • Preserve unresolved intents on delivery failure or conflict; migrate the legacy single-record shape losslessly.
  • Verify the controller behavior with a failing test first, focused tests, the full suite, and packaged mobile browser coverage.

Non-duplication evidence

All 627 historical issue titles and recent commits were reviewed. #1242 adds one pull, #1244 adds capacity confirmation, and #1246 persists one pull. None queues multiple Week-to-Today pulls. #1233 is the opposite Today-to-Week direction.

## Product gap Week Ahead currently persists only one pending Week-to-Today pull under `stackchain.week-today-pull.v1.<account>`. A second offline pull overwrites the first, so a phone operator can lose an admitted work move after reload/reconnect. The reverse Today-to-Week flow already has a bounded FIFO (#1233); #1246 only made one pull durable. ## User flow From the mobile Week Ahead overview, add two items to an active Today plan while delivery is unavailable, reload, then reconnect. Both admitted intents must reach Today exactly once in original order and disappear from Week Ahead. ## Acceptance criteria - Persist multiple account-scoped Week-to-Today pulls as a backward-compatible bounded FIFO. - Admit each pull only after durable storage succeeds; optimistic Today and Week snapshots include every queued pull. - Replay oldest-first with at most one request in flight and rebase each remaining request on returned Today/Week revisions. - Preserve unresolved intents on delivery failure or conflict; migrate the legacy single-record shape losslessly. - Verify the controller behavior with a failing test first, focused tests, the full suite, and packaged mobile browser coverage. ## Non-duplication evidence All 627 historical issue titles and recent commits were reviewed. #1242 adds one pull, #1244 adds capacity confirmation, and #1246 persists one pull. None queues multiple Week-to-Today pulls. #1233 is the opposite Today-to-Week direction.
timmy was assigned by rockachopa 2026-08-22 03:20:52 +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#1249
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?