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

Carry unfinished Today work into the Tomorrow plan #1174

New Issue
Closed
opened 2026-08-20 09:37:26 +00:00 by timmy · 0 comments
timmy commented 2026-08-20 09:37:26 +00:00
Owner
Copy Link

Problem

Today wrap-up labels unfinished work as Tomorrow 09:00 but sends it to Later, so it is absent from the first-class ordered Tomorrow plan, capacity review, reminders, and next-day promotion.

Vertical slice

During wrap-up, let the operator carry selected unfinished Today items into the existing Tomorrow plan. Preserve existing Tomorrow order and estimates, deduplicate items, enforce plan capacity, and remove carried items from Today only after the Tomorrow plan is durably accepted.

Acceptance

  • Wrap-up offers Carry to Tomorrow or Keep in Today for unfinished items.
  • Existing Tomorrow order/estimates are preserved and selected Today items are appended exactly once.
  • The five-item/capacity constraints block an invalid handoff without removing Today work.
  • A successful handoff updates the Tomorrow plan before removing carried items from Today.
  • Mobile wrap-up remains usable without horizontal overflow and with 44px actions at 390x844 and 320x568.
  • Behavioral frontend and rendered mobile tests cover failure and success; full suite passes.

Non-duplication evidence

#990 scheduled unfinished work into Later before the first-class Tomorrow plan existed. #992 reviewed commitments before rebuilding Today. #1152-#1170 built Tomorrow planning, promotion, offline conflict recovery, release gating, and reminders, but frontend/today-wrap-up.js still calls laterWork.presetUntil('tomorrow'); no historical issue connects wrap-up to the Tomorrow plan.

## Problem Today wrap-up labels unfinished work as **Tomorrow 09:00** but sends it to Later, so it is absent from the first-class ordered Tomorrow plan, capacity review, reminders, and next-day promotion. ## Vertical slice During wrap-up, let the operator carry selected unfinished Today items into the existing Tomorrow plan. Preserve existing Tomorrow order and estimates, deduplicate items, enforce plan capacity, and remove carried items from Today only after the Tomorrow plan is durably accepted. ## Acceptance - Wrap-up offers **Carry to Tomorrow** or **Keep in Today** for unfinished items. - Existing Tomorrow order/estimates are preserved and selected Today items are appended exactly once. - The five-item/capacity constraints block an invalid handoff without removing Today work. - A successful handoff updates the Tomorrow plan before removing carried items from Today. - Mobile wrap-up remains usable without horizontal overflow and with 44px actions at 390x844 and 320x568. - Behavioral frontend and rendered mobile tests cover failure and success; full suite passes. ## Non-duplication evidence #990 scheduled unfinished work into Later before the first-class Tomorrow plan existed. #992 reviewed commitments before rebuilding Today. #1152-#1170 built Tomorrow planning, promotion, offline conflict recovery, release gating, and reminders, but `frontend/today-wrap-up.js` still calls `laterWork.presetUntil('tomorrow')`; no historical issue connects wrap-up to the Tomorrow plan.
timmy self-assigned this 2026-08-20 09:37:26 +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#1174
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?