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

Make progressive mobile capture survive reloads before workspace hydration #1409

New Issue
Closed
opened 2026-08-25 21:19:39 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-25 21:19:39 +00:00
Member
Copy Link

Problem

The progressive New → Capture work flow keeps title and note only in memory until Save to Drafts. On constrained mobile startup, a reload or process eviction before that tap loses the operator’s work, even though the hydrated composer checkpoints input.

Evidence: frontend/progressive-capture.js only persists inside saveDraft; tests/test_progressive_capture.py covers explicit save and hydration handoff but not page recreation. Historical issue #1407 delivered pre-hydration capture and in-memory hydration handoff, not process-loss recovery.

Acceptance

  • Account-bound progressive title/note input is checkpointed without creating a Draft card.
  • Recreating the progressive flow for the same confirmed login restores the latest checkpoint and announces recovery.
  • Another or missing login cannot read or clear the checkpoint.
  • Saving to Drafts creates exactly one durable unfiled draft and clears the checkpoint only after save succeeds.
  • Failed durable save leaves both rendered fields and checkpoint available for retry.
  • Hydration handoff transfers current fields and clears the checkpoint only through an explicit successful acknowledgement.
  • Existing mobile-only, filing retry, and full-suite behavior remains green.

Implementation must follow strict RED/GREEN TDD.

## Problem The progressive **New → Capture work** flow keeps title and note only in memory until **Save to Drafts**. On constrained mobile startup, a reload or process eviction before that tap loses the operator’s work, even though the hydrated composer checkpoints input. Evidence: `frontend/progressive-capture.js` only persists inside `saveDraft`; `tests/test_progressive_capture.py` covers explicit save and hydration handoff but not page recreation. Historical issue #1407 delivered pre-hydration capture and in-memory hydration handoff, not process-loss recovery. ## Acceptance - Account-bound progressive title/note input is checkpointed without creating a Draft card. - Recreating the progressive flow for the same confirmed login restores the latest checkpoint and announces recovery. - Another or missing login cannot read or clear the checkpoint. - Saving to Drafts creates exactly one durable unfiled draft and clears the checkpoint only after save succeeds. - Failed durable save leaves both rendered fields and checkpoint available for retry. - Hydration handoff transfers current fields and clears the checkpoint only through an explicit successful acknowledgement. - Existing mobile-only, filing retry, and full-suite behavior remains green. Implementation must follow strict RED/GREEN TDD.
timmy was assigned by rockachopa 2026-08-25 21:19:39 +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#1409
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?