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

Resume recap-to-plan feedback after interruptions #585

New Issue
Closed
opened 2026-08-11 18:49:44 +00:00 by timmy · 0 comments
timmy commented 2026-08-11 18:49:44 +00:00
Owner
Copy Link

Problem

After Save recap & adjust plan confirms the recap, the draft and timer are cleared before recommendations exist anywhere durable. Reload, mobile browser eviction, Back/Cancel, or a failed Today-plan admission loses the estimate feedback even though recap save succeeded.

Product slice

Persist a bounded, account-scoped pending recap-to-plan handoff after confirmed recap save. Restore it into Plan Today after reload, retain it across cancel/admission failure, and clear it only after the adjusted plan is durably admitted. Provide an explicit discard action.

Acceptance tests

  • confirmed save persists the original session ID and actual-minute recommendations under the current account
  • reload restores identical recommendations without reposting recap history
  • account switching cannot expose another operator's handoff
  • cancel/back and failed plan admission retain the handoff
  • successful plan admission clears it; explicit discard clears it
  • malformed/unbounded stored state is removed

No historical issue or recent commit covers the post-save/pre-plan interruption gap; #581 protects pre-save recap drafts and #583 adds only an in-memory handoff.

## Problem After **Save recap & adjust plan** confirms the recap, the draft and timer are cleared before recommendations exist anywhere durable. Reload, mobile browser eviction, Back/Cancel, or a failed Today-plan admission loses the estimate feedback even though recap save succeeded. ## Product slice Persist a bounded, account-scoped pending recap-to-plan handoff after confirmed recap save. Restore it into Plan Today after reload, retain it across cancel/admission failure, and clear it only after the adjusted plan is durably admitted. Provide an explicit discard action. ## Acceptance tests - confirmed save persists the original session ID and actual-minute recommendations under the current account - reload restores identical recommendations without reposting recap history - account switching cannot expose another operator's handoff - cancel/back and failed plan admission retain the handoff - successful plan admission clears it; explicit discard clears it - malformed/unbounded stored state is removed No historical issue or recent commit covers the post-save/pre-plan interruption gap; #581 protects pre-save recap drafts and #583 adds only an in-memory handoff.
timmy self-assigned this 2026-08-11 18:49:44 +00:00
timmy closed this issue 2026-08-11 18:59:25 +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#585
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?