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

Make Following and My PRs actionable from adaptive mobile Work #1456

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

Evidence

The mobile Queues census now truthfully includes Following and My PRs, but frontend/mobile-queue-launcher.js excludes both from its continuation order. With only watched changes or authored pull requests pending, the primary Start / Continue action and persistent Work dock action incorrectly fall through to Find Work. The existing dedicated Following flow and authored pull workspace are already wired, so users are sent to claim new work while existing work needs action.

This is not covered by #1450 (one adaptive action) or #1452 (truthful census); neither makes these queues continuable. A search of historical issue titles and recent commits found no shipped behavior that does so.

Acceptance criteria

  • Following is recommended after higher-priority active work and before Filed/Later/Drafts; activating it opens the dedicated changed-first Following flow.
  • My PRs is recommended after Following and before Filed/Later/Drafts; activating it opens the first authored pull through the existing authored workspace.
  • Find Work appears only when every actionable queue is empty.
  • The persistent Work action exposes truthful visible and accessible labels for Following and My PRs.
  • Existing Delivery, Human Gates, Attention, Today, Updates, and Agenda priority is preserved.
  • Rendered 320x568, 375x667, and 430x932 journeys keep the CTA above the fold, at least 44px high, without horizontal overflow, and prove the same destination for activation.
  • Focused and full automated suites pass.
## Evidence The mobile Queues census now truthfully includes Following and My PRs, but `frontend/mobile-queue-launcher.js` excludes both from its continuation order. With only watched changes or authored pull requests pending, the primary Start / Continue action and persistent Work dock action incorrectly fall through to Find Work. The existing dedicated Following flow and authored pull workspace are already wired, so users are sent to claim new work while existing work needs action. This is not covered by #1450 (one adaptive action) or #1452 (truthful census); neither makes these queues continuable. A search of historical issue titles and recent commits found no shipped behavior that does so. ## Acceptance criteria - Following is recommended after higher-priority active work and before Filed/Later/Drafts; activating it opens the dedicated changed-first Following flow. - My PRs is recommended after Following and before Filed/Later/Drafts; activating it opens the first authored pull through the existing authored workspace. - Find Work appears only when every actionable queue is empty. - The persistent Work action exposes truthful visible and accessible labels for Following and My PRs. - Existing Delivery, Human Gates, Attention, Today, Updates, and Agenda priority is preserved. - Rendered 320x568, 375x667, and 430x932 journeys keep the CTA above the fold, at least 44px high, without horizontal overflow, and prove the same destination for activation. - Focused and full automated suites pass.
timmy self-assigned this 2026-08-27 04:24:00 +00:00
timmy closed this issue 2026-08-27 04:46:59 +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#1456
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?