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

Plan tomorrow without disrupting active Today work #1152

New Issue
Closed
opened 2026-08-19 22:22:16 +00:00 by timmy · 0 comments
timmy commented 2026-08-19 22:22:16 +00:00
Owner
Copy Link

User problem

Operators can only build the current Today plan. End-of-day deferral sends work to Later at 09:00, losing ordered intent, estimates, and capacity. Planning tomorrow currently risks replacing the active Today plan.

Vertical slice

Add an advance Tomorrow plan that is stored independently from Today, is editable on mobile with order/estimates/capacity, syncs across devices, and promotes exactly once at the next local-day rollover without disturbing the active Today session.

Acceptance tests

  • Saving Tomorrow leaves Today IDs, order, capacity, timer, and active item unchanged.
  • Tomorrow persists ordered IDs, estimates, capacity, target local date, timezone, and revision across restart/account boundaries.
  • A rollover promotes the matching Tomorrow plan exactly once; retries cannot duplicate or partially replace work.
  • A stale promotion cannot overwrite a newer Today revision and returns an explicit conflict for review.
  • At mobile width the Tomorrow entry and save actions remain touch-safe and accessible.
  • Existing Today behavior is unchanged when no Tomorrow plan exists.

Evidence / non-duplication

Current today_plans is keyed only by login (src/today_store.py), while frontend/today-wrap-up.js defers unfinished work to Later rather than retaining a future ordered plan. Historical issue-title and recent-commit searches found Today ordering/sync and Later deferral, but no independent Tomorrow plan or atomic next-day promotion.

## User problem Operators can only build the current Today plan. End-of-day deferral sends work to Later at 09:00, losing ordered intent, estimates, and capacity. Planning tomorrow currently risks replacing the active Today plan. ## Vertical slice Add an advance Tomorrow plan that is stored independently from Today, is editable on mobile with order/estimates/capacity, syncs across devices, and promotes exactly once at the next local-day rollover without disturbing the active Today session. ## Acceptance tests - Saving Tomorrow leaves Today IDs, order, capacity, timer, and active item unchanged. - Tomorrow persists ordered IDs, estimates, capacity, target local date, timezone, and revision across restart/account boundaries. - A rollover promotes the matching Tomorrow plan exactly once; retries cannot duplicate or partially replace work. - A stale promotion cannot overwrite a newer Today revision and returns an explicit conflict for review. - At mobile width the Tomorrow entry and save actions remain touch-safe and accessible. - Existing Today behavior is unchanged when no Tomorrow plan exists. ## Evidence / non-duplication Current `today_plans` is keyed only by login (`src/today_store.py`), while `frontend/today-wrap-up.js` defers unfinished work to Later rather than retaining a future ordered plan. Historical issue-title and recent-commit searches found Today ordering/sync and Later deferral, but no independent Tomorrow plan or atomic next-day promotion.
timmy self-assigned this 2026-08-19 22:22:16 +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#1152
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?