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

Personalize routine priority in adaptive mobile Queues #1460

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

Problem

Adaptive mobile Work uses one fixed routine order, so a permanently non-empty earlier queue can starve Following, My PRs, Later, or Drafts from the one-tap Start / Continue action. Recent work made those queues actionable, but operators still cannot align routine priority to their role.

Slice

Add an account-scoped, device-local routine ordering flow inside mobile Queues. Delivery and Human Gates remain immutable safety priorities, and Prepare Today remains the top checkpoint. Operators can move routine queues earlier/later and reset defaults; the primary action and Active now order refresh immediately.

Acceptance

  • Valid saved routine order changes recommendation and active row order.
  • Delivery and Human Gates stay ahead of all routine preferences when online; unavailable critical queues do not block offline work.
  • Prepare Today still overrides preferences.
  • Invalid, duplicate, incomplete, or unknown persisted data falls back to defaults.
  • Preferences are scoped to the confirmed login and do not leak across accounts.
  • Touch/keyboard reorder controls are at least 44px, screen-reader labelled, and do not overflow at 320px.
  • Focused behavioral tests, rendered phone journey, and full suite pass.

Evidence / non-duplication

mobile-queue-launcher.js currently hard-codes the continuation order. Historical issue/title and recent commit inspection found work for adaptive queue census and actionable Following/My PRs (#1450–#1459), but no operator-defined priority or account-scoped ordering. Open issues are assigned to other agents/humans and do not cover this flow.

## Problem Adaptive mobile Work uses one fixed routine order, so a permanently non-empty earlier queue can starve Following, My PRs, Later, or Drafts from the one-tap Start / Continue action. Recent work made those queues actionable, but operators still cannot align routine priority to their role. ## Slice Add an account-scoped, device-local routine ordering flow inside mobile Queues. Delivery and Human Gates remain immutable safety priorities, and Prepare Today remains the top checkpoint. Operators can move routine queues earlier/later and reset defaults; the primary action and Active now order refresh immediately. ## Acceptance - Valid saved routine order changes recommendation and active row order. - Delivery and Human Gates stay ahead of all routine preferences when online; unavailable critical queues do not block offline work. - Prepare Today still overrides preferences. - Invalid, duplicate, incomplete, or unknown persisted data falls back to defaults. - Preferences are scoped to the confirmed login and do not leak across accounts. - Touch/keyboard reorder controls are at least 44px, screen-reader labelled, and do not overflow at 320px. - Focused behavioral tests, rendered phone journey, and full suite pass. ## Evidence / non-duplication `mobile-queue-launcher.js` currently hard-codes the continuation order. Historical issue/title and recent commit inspection found work for adaptive queue census and actionable Following/My PRs (#1450–#1459), but no operator-defined priority or account-scoped ordering. Open issues are assigned to other agents/humans and do not cover this flow.
timmy closed this issue 2026-08-27 07:21:39 +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
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#1460
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?