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

Add mobile Today progress updates without advancing work #1052

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

Evidence

The active mobile Today HUD currently offers open, complete, pause, break, and adjust-plan actions, but no way to capture or publish a progress update while keeping the exact item active. Posting today requires opening the full detail sheet; the existing Comment & next flow advances the session. Historical issue/PR titles and recent commits contain no equivalent in-session update flow.

User outcome

From the active Today HUD, an operator can save an account-scoped progress draft or post/queue it to the exact current issue or pull request without pausing the timer, completing the item, or advancing Today.

Acceptance tests

  • Update is available only for an active, checkpointed Today issue/pull and is thumb reachable at mobile widths.
  • The sheet names the exact target and restores its bounded account-and-item-scoped draft after close/reload.
  • Save draft performs no network mutation and does not change timer/session position.
  • Post now admits the update to the existing idempotent authored outbox, supports offline durable admission, and clears the draft only after admission.
  • Switching Today items cannot display or post another item’s draft.
  • Sign-out/private-data clearing includes progress drafts.
  • Focus, escape/cancel, safe-area, 320px layout, focused tests, full suite, and release E2E contracts remain green.
## Evidence The active mobile Today HUD currently offers open, complete, pause, break, and adjust-plan actions, but no way to capture or publish a progress update while keeping the exact item active. Posting today requires opening the full detail sheet; the existing Comment & next flow advances the session. Historical issue/PR titles and recent commits contain no equivalent in-session update flow. ## User outcome From the active Today HUD, an operator can save an account-scoped progress draft or post/queue it to the exact current issue or pull request without pausing the timer, completing the item, or advancing Today. ## Acceptance tests - Update is available only for an active, checkpointed Today issue/pull and is thumb reachable at mobile widths. - The sheet names the exact target and restores its bounded account-and-item-scoped draft after close/reload. - Save draft performs no network mutation and does not change timer/session position. - Post now admits the update to the existing idempotent authored outbox, supports offline durable admission, and clears the draft only after admission. - Switching Today items cannot display or post another item’s draft. - Sign-out/private-data clearing includes progress drafts. - Focus, escape/cancel, safe-area, 320px layout, focused tests, full suite, and release E2E contracts remain green.
timmy self-assigned this 2026-08-18 00:24:13 +00:00
timmy closed this issue 2026-08-18 00:52:45 +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#1052
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?