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

Keep adaptive mobile Work actionable while offline #1458

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

Problem

Adaptive mobile Work prioritizes queues by count alone. When the installed dashboard is offline, the primary Start / Continue action can recommend an online-only Human Gate or delivery recovery, sending the operator into a dead end even though cached Today, Updates, Later, or Draft work remains actionable.

Vertical slice

Make the adaptive recommendation capability-aware: skip online-only Delivery and Human Gates while offline, continue into the highest-priority offline-capable queue, restore normal priority when connectivity returns, and rerender the visible recommendation on connectivity changes. Direct queue rows remain visible for truthful census/navigation.

Acceptance tests

  • Given Delivery and Human Gates plus cached Today work while offline, Start / Continue recommends and opens Today.
  • Given the same census after reconnecting, Delivery regains normal priority.
  • Online/offline events rerender the recommendation without reopening the sheet.
  • Packaged 390x844 mobile journey verifies the phone-visible action and successful offline handoff.
  • Existing focused and full test suites remain green.

Evidence / non-duplicate proof

frontend/mobile-queue-launcher.js currently selects from a fixed continuation list and has no capability input; frontend/dashboard.js wires counts only despite already tracking offline state. Historical issue-title and recent-commit review found connectivity-aware queue snapshots/outboxes but no behavior making adaptive Start / Continue skip online-only queues. Recent #1450/#1452/#1456 established the adaptive action, census, and Following/My PR actions but did not add connectivity-aware routing.

## Problem Adaptive mobile Work prioritizes queues by count alone. When the installed dashboard is offline, the primary Start / Continue action can recommend an online-only Human Gate or delivery recovery, sending the operator into a dead end even though cached Today, Updates, Later, or Draft work remains actionable. ## Vertical slice Make the adaptive recommendation capability-aware: skip online-only Delivery and Human Gates while offline, continue into the highest-priority offline-capable queue, restore normal priority when connectivity returns, and rerender the visible recommendation on connectivity changes. Direct queue rows remain visible for truthful census/navigation. ## Acceptance tests - Given Delivery and Human Gates plus cached Today work while offline, Start / Continue recommends and opens Today. - Given the same census after reconnecting, Delivery regains normal priority. - Online/offline events rerender the recommendation without reopening the sheet. - Packaged 390x844 mobile journey verifies the phone-visible action and successful offline handoff. - Existing focused and full test suites remain green. ## Evidence / non-duplicate proof `frontend/mobile-queue-launcher.js` currently selects from a fixed continuation list and has no capability input; `frontend/dashboard.js` wires counts only despite already tracking offline state. Historical issue-title and recent-commit review found connectivity-aware queue snapshots/outboxes but no behavior making adaptive Start / Continue skip online-only queues. Recent #1450/#1452/#1456 established the adaptive action, census, and Following/My PR actions but did not add connectivity-aware routing.
timmy self-assigned this 2026-08-27 05:52:24 +00:00
timmy closed this issue 2026-08-27 06:11:58 +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#1458
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?