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

Continue mobile Work into Filed follow-up #1008

New Issue
Closed
opened 2026-08-17 07:23:16 +00:00 by timmy · 0 comments
timmy commented 2026-08-17 07:23:16 +00:00
Owner
Copy Link

Evidence

On origin/main at 021af60, the mobile Queues dock counts Filed as actionable and Prepare Today includes Filed, but mobile-queue-launcher.js omits Filed from the primary Work continuation order. With only Filed items remaining, Work incorrectly falls through to Find Work even though openFiledFollowUp() already provides the correct delegated-outcome flow. Historical issue #755 predates Filed; #870–#925 built Filed review but none connected it to Work.

User impact

Mobile operators can use the primary thumb-reachable Work action to review delegated outcomes before seeking new work. The action remains deterministic: active Today, Attention, Today, Updates, Agenda, Filed, Later, Drafts, then Find Work. Reviewed-only Filed history must not be actionable.

Acceptance tests

  • With only actionable Filed work, Work recommends Filed and opens the existing Filed follow-up flow.
  • Filed follows Agenda and precedes Later and Drafts.
  • The dock renders Filed with accessible name Open Filed.
  • Reviewed-only Filed history does not contribute to the actionable count and Work falls back normally.
  • Focused and full test suites pass; packaged browser bundle remains valid.
## Evidence On `origin/main` at `021af60`, the mobile Queues dock counts Filed as actionable and Prepare Today includes Filed, but `mobile-queue-launcher.js` omits Filed from the primary Work continuation order. With only Filed items remaining, Work incorrectly falls through to Find Work even though `openFiledFollowUp()` already provides the correct delegated-outcome flow. Historical issue #755 predates Filed; #870–#925 built Filed review but none connected it to Work. ## User impact Mobile operators can use the primary thumb-reachable Work action to review delegated outcomes before seeking new work. The action remains deterministic: active Today, Attention, Today, Updates, Agenda, Filed, Later, Drafts, then Find Work. Reviewed-only Filed history must not be actionable. ## Acceptance tests - With only actionable Filed work, Work recommends Filed and opens the existing Filed follow-up flow. - Filed follows Agenda and precedes Later and Drafts. - The dock renders `Filed` with accessible name `Open Filed`. - Reviewed-only Filed history does not contribute to the actionable count and Work falls back normally. - Focused and full test suites pass; packaged browser bundle remains valid.
timmy self-assigned this 2026-08-17 07:23:16 +00:00
timmy closed this issue 2026-08-17 07:39:04 +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#1008
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?