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

Run the mobile Agenda as a sequential work session #731

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

Product gap

The mobile Agenda renders assigned deadlines in a useful overdue-to-next-seven-days order, but Start work passes the unknown agenda filter into the generic queue filter. That produces an empty session, so operators cannot execute the deadline queue they can see.

Acceptance criteria

  • On #/my-work/agenda, the launcher reads Start Agenda and starts the first visible deadline in Agenda order.
  • Previous/Next and close-and-next continue through that ordered Agenda snapshot.
  • Agenda completion returns to Agenda with an explicit completion status rather than Today recap.
  • Empty Agenda cannot start a false session.
  • Agenda sessions do not read or overwrite the durable Today checkpoint.
  • Existing Today and generic filtered sessions retain their behavior.
  • Behavioral tests cover queue resolution, launcher semantics, completion, and checkpoint isolation.

Evidence / non-duplication

Current origin/main (af27bb0) wires getItems to activeMyWork and getFilter to agenda; filterMyWork treats unknown filters as item kinds, so no Agenda items survive. All 368 historical issue titles and recent commits were scanned. Existing Agenda issues cover discovery, routing, planning, replan, and reminders—not sequential Agenda execution. There are no open eligible issues or PRs for this behavior.

## Product gap The mobile Agenda renders assigned deadlines in a useful overdue-to-next-seven-days order, but **Start work** passes the unknown `agenda` filter into the generic queue filter. That produces an empty session, so operators cannot execute the deadline queue they can see. ## Acceptance criteria - On `#/my-work/agenda`, the launcher reads **Start Agenda** and starts the first visible deadline in Agenda order. - Previous/Next and close-and-next continue through that ordered Agenda snapshot. - Agenda completion returns to Agenda with an explicit completion status rather than Today recap. - Empty Agenda cannot start a false session. - Agenda sessions do not read or overwrite the durable Today checkpoint. - Existing Today and generic filtered sessions retain their behavior. - Behavioral tests cover queue resolution, launcher semantics, completion, and checkpoint isolation. ## Evidence / non-duplication Current `origin/main` (`af27bb0`) wires `getItems` to `activeMyWork` and `getFilter` to `agenda`; `filterMyWork` treats unknown filters as item kinds, so no Agenda items survive. All 368 historical issue titles and recent commits were scanned. Existing Agenda issues cover discovery, routing, planning, replan, and reminders—not sequential Agenda execution. There are no open eligible issues or PRs for this behavior.
timmy self-assigned this 2026-08-13 10:54:58 +00:00
timmy closed this issue 2026-08-13 10:57:29 +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#731
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?