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

Plan a Following change and continue review #1326

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

User problem

Following now explains each captured change, but its mobile preview still exposes the generic Search action wall. Operators cannot make one explicit workload decision and continue the bounded review pass.

Vertical slice

For an eligible open issue opened from Following, make the existing planning outcomes continuation-aware:

  • Add to Today & next
  • Later & next
  • Week Ahead & next

Advance only after the existing durable admission succeeds (including truthful sync-pending outcomes). Cancellation, validation, capacity conflict, assignment-only success, or persistence failure must retain the current captured change. Preserve watch status and the final Prepare Today handoff.

Acceptance

  • Following context uses explicit continuation labels without changing generic Search.
  • Today, Later, and Week Ahead successful admissions advance exactly once; failures/cancel do not advance.
  • Week Ahead exposes a completion callback rather than coupling to Following.
  • Controls remain touch-safe at 320px and packaged mobile tests cover the user flow.
  • Focused tests, full suite, and Gitea Actions pass.

Evidence / non-duplication

Audited origin/main at 0f36d30, all 666 historical issue titles, 8 open issues, the sole open PR, releases, and recent commits. Related #1299, #1301, #1320, and #1322 cover sequential review, Prepare Today integration, keep-and-next, and change explanation; none turns Today/Later/Week Ahead planning into an action-and-continue flow.

## User problem Following now explains each captured change, but its mobile preview still exposes the generic Search action wall. Operators cannot make one explicit workload decision and continue the bounded review pass. ## Vertical slice For an eligible open issue opened from Following, make the existing planning outcomes continuation-aware: - **Add to Today & next** - **Later & next** - **Week Ahead & next** Advance only after the existing durable admission succeeds (including truthful sync-pending outcomes). Cancellation, validation, capacity conflict, assignment-only success, or persistence failure must retain the current captured change. Preserve watch status and the final Prepare Today handoff. ## Acceptance - Following context uses explicit continuation labels without changing generic Search. - Today, Later, and Week Ahead successful admissions advance exactly once; failures/cancel do not advance. - Week Ahead exposes a completion callback rather than coupling to Following. - Controls remain touch-safe at 320px and packaged mobile tests cover the user flow. - Focused tests, full suite, and Gitea Actions pass. ## Evidence / non-duplication Audited origin/main at `0f36d30`, all 666 historical issue titles, 8 open issues, the sole open PR, releases, and recent commits. Related #1299, #1301, #1320, and #1322 cover sequential review, Prepare Today integration, keep-and-next, and change explanation; none turns Today/Later/Week Ahead planning into an action-and-continue flow.
timmy was assigned by rockachopa 2026-08-23 23:22:12 +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#1326
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?