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

Review wrap-up commitments before rebuilding Today #992

New Issue
Closed
opened 2026-08-16 22:55:05 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-16 22:55:05 +00:00
Member
Copy Link

User problem

Work selected during Today wrap-up returns to ordinary My Work at its wake time. The next session cannot distinguish yesterday's commitment from generic deferred work.

Evidence

  • frontend/today-wrap-up.js labels selected work as tomorrow work but uses generic laterWork.defer.
  • frontend/later-work.js stores only a timestamp and discards it on expiry.
  • frontend/dashboard.js only announces that deferred work is ready.
  • Historical titles and recent main history contain no preserved wrap-up-to-Today handoff.

Acceptance criteria

  • Wrap-up selections carry a next-day Today intent while ordinary deferrals remain unchanged.
  • Intent syncs through the Later API with backward compatibility for timestamp records.
  • Due commitments get a mobile-safe review in original order and selected work enters Today through durable sync, respecting capacity and retaining unaccepted work.
  • Behavioral tests cover persistence, wake handoff, idempotency, and capacity failure.
  • Accessible controls and offline bundle coverage ship with passing focused/full suites.
## User problem Work selected during Today wrap-up returns to ordinary My Work at its wake time. The next session cannot distinguish yesterday's commitment from generic deferred work. ## Evidence - `frontend/today-wrap-up.js` labels selected work as tomorrow work but uses generic `laterWork.defer`. - `frontend/later-work.js` stores only a timestamp and discards it on expiry. - `frontend/dashboard.js` only announces that deferred work is ready. - Historical titles and recent main history contain no preserved wrap-up-to-Today handoff. ## Acceptance criteria - Wrap-up selections carry a next-day Today intent while ordinary deferrals remain unchanged. - Intent syncs through the Later API with backward compatibility for timestamp records. - Due commitments get a mobile-safe review in original order and selected work enters Today through durable sync, respecting capacity and retaining unaccepted work. - Behavioral tests cover persistence, wake handoff, idempotency, and capacity failure. - Accessible controls and offline bundle coverage ship with passing focused/full suites.
timmy was assigned by rockachopa 2026-08-16 22:55:05 +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#992
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?