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

Complete mobile delivery attention handoff into the actionable workspace #1018

New Issue
Closed
opened 2026-08-17 10:26:44 +00:00 by timmy · 0 comments
timmy commented 2026-08-17 10:26:44 +00:00
Owner
Copy Link

Product gap

The guided mobile Delivery flow keeps its modal open while synthetic-clicking review, checklist-conflict, issue, or quarantined-draft actions underneath it. The destination can be visually blocked and the primary action may settle before asynchronous attention work completes.

Vertical slice

Make attention-state recovery an explicit, awaited handoff: suspend the recovery modal, foreground the exact actionable destination, keep the action single-flight, and resume the same unresolved recovery item when the operator returns. Quarantined content must land on its Draft card with the discard/edit path visible.

Acceptance

  • Review/checklist/issue attention closes the recovery modal and foregrounds the exact destination.
  • Async attention remains single-flight until settlement; failure retains a retryable recovery item.
  • Returning resumes the unresolved item; resolving advances exactly once.
  • Quarantined copy foregrounds its Draft card and discard path.
  • Behavioral unit tests fail first, focused and full suites pass, and packaged mobile behavior is validated.

Non-duplication

Issues #1010, #1012, #1014, and #1016 introduced and stabilized guided recovery but do not implement modal-safe awaited attention handoff. No matching title or behavior exists in the 511-item issue history or recent commits.

## Product gap The guided mobile Delivery flow keeps its modal open while synthetic-clicking review, checklist-conflict, issue, or quarantined-draft actions underneath it. The destination can be visually blocked and the primary action may settle before asynchronous attention work completes. ## Vertical slice Make attention-state recovery an explicit, awaited handoff: suspend the recovery modal, foreground the exact actionable destination, keep the action single-flight, and resume the same unresolved recovery item when the operator returns. Quarantined content must land on its Draft card with the discard/edit path visible. ## Acceptance - Review/checklist/issue attention closes the recovery modal and foregrounds the exact destination. - Async attention remains single-flight until settlement; failure retains a retryable recovery item. - Returning resumes the unresolved item; resolving advances exactly once. - Quarantined copy foregrounds its Draft card and discard path. - Behavioral unit tests fail first, focused and full suites pass, and packaged mobile behavior is validated. ## Non-duplication Issues #1010, #1012, #1014, and #1016 introduced and stabilized guided recovery but do not implement modal-safe awaited attention handoff. No matching title or behavior exists in the 511-item issue history or recent commits.
timmy self-assigned this 2026-08-17 10:26:44 +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#1018
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?