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

Wait for complete Agenda discovery before starting a session #735

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

Problem

Mobile Agenda selection starts/resumes the work session while older assigned-issue pages are still loading. A saved item on a later page can be replaced by a page-one fallback, and a fresh session can begin from an incomplete deadline order.

User impact

On slow mobile connections or accounts with more than one issue page, users can open the wrong deadline, omit older deadlines, or overwrite valid resume progress.

Acceptance criteria

  • Start and Resume await complete assigned-deadline discovery.
  • Repeated launch taps share one in-flight discovery and open at most one session.
  • Failed/incomplete discovery opens no item, preserves the checkpoint, and exposes a retryable status.
  • Leaving Agenda before discovery completes cannot open a stale detail.
  • Existing Today behavior remains unchanged.
  • Focused behavioral tests and the full suite pass.

Evidence / non-duplication

frontend/dashboard.js currently calls completeAgendaIssues() asynchronously on queue selection, while openAgendaSession() immediately invokes workSession.start()/resume(). Issues #703, #731, and #733 added pagination, sequential execution, and durable resume respectively, but none makes discovery and launch atomic.

## Problem Mobile Agenda selection starts/resumes the work session while older assigned-issue pages are still loading. A saved item on a later page can be replaced by a page-one fallback, and a fresh session can begin from an incomplete deadline order. ## User impact On slow mobile connections or accounts with more than one issue page, users can open the wrong deadline, omit older deadlines, or overwrite valid resume progress. ## Acceptance criteria - Start and Resume await complete assigned-deadline discovery. - Repeated launch taps share one in-flight discovery and open at most one session. - Failed/incomplete discovery opens no item, preserves the checkpoint, and exposes a retryable status. - Leaving Agenda before discovery completes cannot open a stale detail. - Existing Today behavior remains unchanged. - Focused behavioral tests and the full suite pass. ## Evidence / non-duplication `frontend/dashboard.js` currently calls `completeAgendaIssues()` asynchronously on queue selection, while `openAgendaSession()` immediately invokes `workSession.start()`/`resume()`. Issues #703, #731, and #733 added pagination, sequential execution, and durable resume respectively, but none makes discovery and launch atomic.
timmy self-assigned this 2026-08-13 11:48:51 +00:00
timmy closed this issue 2026-08-13 11:58:31 +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#735
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?