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

Make mobile New capture available before optional workspace hydration #1407

New Issue
Closed
opened 2026-08-25 19:53:56 +00:00 by timmy · 0 comments
timmy commented 2026-08-25 19:53:56 +00:00
Owner
Copy Link

Problem

On origin/main at a23276f, progressive My Work renders after work-core, but frontend/dashboard.js waits for both today-timer and planning before wiring the mobile task dock. The 223,917-byte gzip optional path therefore keeps New inert for several seconds on constrained links and permanently inert when either optional bundle is unavailable. The existing capture sheet and durable unfiled-draft store already provide the desired capture-first flow, but they are trapped behind that gate.

No open issue is eligible for Timmy/unassigned implementation, and enumeration of all 706 historical issue titles plus recent commits found no progressive capture/hydration equivalent. Closest work #1401-#1406 only progressively hydrates My Work and transfers its queue/live state.

Vertical slice

Make mobile New → Capture work → Save to Drafts usable as soon as work-core is ready. Bind it once, preserve an open capture through full-dashboard handoff, and load the full filing workflow only when File now is requested. Keep persisted drafts account-bound and retain current hydrated behavior.

Acceptance

  • With Today and planning bundles stalled, tapping mobile New opens Capture work and focuses the title.
  • Saving a title/note writes exactly one account-bound existing unfiled-draft record and announces success without a network mutation.
  • Full hydration adopts any open title/note without closing or duplicating listeners; one save tap creates one draft.
  • File now requests full hydration while preserving fields; failure leaves the capture editable with retry status.
  • The progressive controller is packaged with work-core, and existing desktop behavior remains unchanged.
  • Focused behavioral tests prove RED/GREEN, the full suite passes, and mobile release coverage validates 320×568 and 390×844 behavior.
## Problem On `origin/main` at `a23276f`, progressive My Work renders after `work-core`, but `frontend/dashboard.js` waits for both `today-timer` and `planning` before wiring the mobile task dock. The 223,917-byte gzip optional path therefore keeps **New** inert for several seconds on constrained links and permanently inert when either optional bundle is unavailable. The existing capture sheet and durable unfiled-draft store already provide the desired capture-first flow, but they are trapped behind that gate. No open issue is eligible for Timmy/unassigned implementation, and enumeration of all 706 historical issue titles plus recent commits found no progressive capture/hydration equivalent. Closest work #1401-#1406 only progressively hydrates My Work and transfers its queue/live state. ## Vertical slice Make mobile **New → Capture work → Save to Drafts** usable as soon as `work-core` is ready. Bind it once, preserve an open capture through full-dashboard handoff, and load the full filing workflow only when **File now** is requested. Keep persisted drafts account-bound and retain current hydrated behavior. ## Acceptance - With Today and planning bundles stalled, tapping mobile **New** opens Capture work and focuses the title. - Saving a title/note writes exactly one account-bound existing unfiled-draft record and announces success without a network mutation. - Full hydration adopts any open title/note without closing or duplicating listeners; one save tap creates one draft. - **File now** requests full hydration while preserving fields; failure leaves the capture editable with retry status. - The progressive controller is packaged with `work-core`, and existing desktop behavior remains unchanged. - Focused behavioral tests prove RED/GREEN, the full suite passes, and mobile release coverage validates 320×568 and 390×844 behavior.
timmy self-assigned this 2026-08-25 19:53:56 +00:00
timmy closed this issue 2026-08-25 20:37:01 +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#1407
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?