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

Make mobile Agenda sessions directly launchable and resumable #733

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

Problem

The mobile Queues → Agenda entry selects the Agenda filter and clicks the first card instead of starting the ordered Agenda session. The visible Start Agenda control is hidden on mobile, and Agenda progress is intentionally non-durable, so reloads or installed-app restarts lose the current deadline.

User impact

People working from a phone cannot reliably start or resume the deadline queue that Agenda already orders for them. Interruptions make them restart from the first deadline, increasing missed work and duplicate review.

Acceptance criteria

  • Queues → Agenda starts the first rendered deadline item and reports Agenda progress.
  • Agenda uses an account-bound stackchain.agenda-session.v1 checkpoint separate from Today.
  • Reload/resume restores the saved item or the next surviving item after reconciliation.
  • Mobile copy changes to Resume Agenda while a checkpoint exists.
  • Finishing clears only Agenda state, returns to Agenda, and announces completion.
  • Today checkpoint and timer behavior remain unchanged.
  • Behavioral tests cover start, resume, account isolation, reconciliation, completion, and mobile wiring.

Non-duplication evidence

#731/#732 added an ordered, explicitly non-durable Agenda runtime. #395 added recovery for Today only. No historical issue title or recent commit adds a dedicated Agenda checkpoint or direct mobile Start/Resume Agenda entry.

## Problem The mobile Queues → Agenda entry selects the Agenda filter and clicks the first card instead of starting the ordered Agenda session. The visible Start Agenda control is hidden on mobile, and Agenda progress is intentionally non-durable, so reloads or installed-app restarts lose the current deadline. ## User impact People working from a phone cannot reliably start or resume the deadline queue that Agenda already orders for them. Interruptions make them restart from the first deadline, increasing missed work and duplicate review. ## Acceptance criteria - Queues → Agenda starts the first rendered deadline item and reports Agenda progress. - Agenda uses an account-bound `stackchain.agenda-session.v1` checkpoint separate from Today. - Reload/resume restores the saved item or the next surviving item after reconciliation. - Mobile copy changes to Resume Agenda while a checkpoint exists. - Finishing clears only Agenda state, returns to Agenda, and announces completion. - Today checkpoint and timer behavior remain unchanged. - Behavioral tests cover start, resume, account isolation, reconciliation, completion, and mobile wiring. ## Non-duplication evidence #731/#732 added an ordered, explicitly non-durable Agenda runtime. #395 added recovery for Today only. No historical issue title or recent commit adds a dedicated Agenda checkpoint or direct mobile Start/Resume Agenda entry.
timmy self-assigned this 2026-08-13 11:20:17 +00:00
timmy closed this issue 2026-08-13 11:29:16 +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#733
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?