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

Open ready-to-file mobile Drafts directly in final review #861

New Issue
Closed
opened 2026-08-15 00:50:16 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 00:50:16 +00:00
Owner
Copy Link

Problem

A synchronized Draft with a complete filing plan is classified as “Ready to file” internally, but its mobile card still says “Needs filing” and “Choose repository.” Opening it forces the user back through the full composer and loses the preserved create-vs-start intent instead of presenting the existing final payload review.

User flow

  • Planned Draft cards show repository, intent, estimate, evidence count, and a truthful Ready to file state.
  • Their primary action is Review & file or Review & start.
  • One tap restores the exact synchronized plan/evidence and opens final review directly.
  • Repository-less Drafts retain Choose repository.
  • Back to edit preserves all restored data; confirmation retains existing duplicate, capacity, durable admission, and sequential-file safeguards.

Acceptance

  • Behavioral tests cover planned vs minimal card presentation and intent restoration.
  • Planned Draft activation opens final review with the exact restored payload.
  • Create & start revalidates estimate and current Today capacity before review/admission.
  • Existing duplicate acknowledgement and durable outbox safeguards remain enforced.
  • Mobile actions remain at least 44px and do not overflow at 320px.
## Problem A synchronized Draft with a complete filing plan is classified as “Ready to file” internally, but its mobile card still says “Needs filing” and “Choose repository.” Opening it forces the user back through the full composer and loses the preserved create-vs-start intent instead of presenting the existing final payload review. ## User flow - Planned Draft cards show repository, intent, estimate, evidence count, and a truthful Ready to file state. - Their primary action is Review & file or Review & start. - One tap restores the exact synchronized plan/evidence and opens final review directly. - Repository-less Drafts retain Choose repository. - Back to edit preserves all restored data; confirmation retains existing duplicate, capacity, durable admission, and sequential-file safeguards. ## Acceptance - Behavioral tests cover planned vs minimal card presentation and intent restoration. - Planned Draft activation opens final review with the exact restored payload. - Create & start revalidates estimate and current Today capacity before review/admission. - Existing duplicate acknowledgement and durable outbox safeguards remain enforced. - Mobile actions remain at least 44px and do not overflow at 320px.
timmy self-assigned this 2026-08-15 00:50:16 +00:00
timmy closed this issue 2026-08-15 01:15: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#861
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?