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

Make Human Gates first-class in mobile queues and Prepare Today #1417

New Issue
Closed
opened 2026-08-26 02:28:11 +00:00 by timmy · 0 comments
timmy commented 2026-08-26 02:28:11 +00:00
Owner
Copy Link

Evidence

The Human Gates release inbox is hidden from the normal mobile workflow: its only launcher is inside .my-work-actions, which frontend/dashboard.css hides at phone widths. The mobile queue sheet in frontend/index.html, queue badge/accessible summary in frontend/mobile-task-dock.js, and Prepare Today phase order in frontend/mobile-start-day.js all omit pending gates. Current origin/main only tests the standalone shell/deep route.

User flow

Expose pending Human Gates in the thumb-reachable Queues sheet and active-queue summary. Review them in Prepare Today after Delivery recovery and before Agenda. Opening either entry must use the existing exact-hash fixed-snapshot review. A successful final decision updates mobile counts and advances Prepare Today exactly once. A failed load without cache must remain retryable rather than claiming review is clear.

Acceptance tests

  • Human Gates row and pending count are rendered in the mobile queue sheet.
  • Dock count and accessible queue summary include Human Gates.
  • Prepare Today orders Delivery → Human Gates → Agenda and opens the existing gate review.
  • Gate load updates all mobile surfaces; final successful decision clears the phase and hands off once.
  • Failed no-cache gate load exposes unavailable/retry state and blocks a false Review clear handoff.
  • Existing fixed-snapshot, desktop, deep-link, and offline read-only behavior remains intact.

Non-duplication

Searched all 711 historical issue titles, 702 pull requests, current releases, and recent commits through e9d257e. Closed #1415/#1416 built the standalone Human Gates inbox but did not integrate it with mobile Queues or Prepare Today; no open issue or recent commit covers this behavior.

## Evidence The Human Gates release inbox is hidden from the normal mobile workflow: its only launcher is inside `.my-work-actions`, which `frontend/dashboard.css` hides at phone widths. The mobile queue sheet in `frontend/index.html`, queue badge/accessible summary in `frontend/mobile-task-dock.js`, and Prepare Today phase order in `frontend/mobile-start-day.js` all omit pending gates. Current `origin/main` only tests the standalone shell/deep route. ## User flow Expose pending Human Gates in the thumb-reachable Queues sheet and active-queue summary. Review them in Prepare Today after Delivery recovery and before Agenda. Opening either entry must use the existing exact-hash fixed-snapshot review. A successful final decision updates mobile counts and advances Prepare Today exactly once. A failed load without cache must remain retryable rather than claiming review is clear. ## Acceptance tests - Human Gates row and pending count are rendered in the mobile queue sheet. - Dock count and accessible queue summary include Human Gates. - Prepare Today orders Delivery → Human Gates → Agenda and opens the existing gate review. - Gate load updates all mobile surfaces; final successful decision clears the phase and hands off once. - Failed no-cache gate load exposes unavailable/retry state and blocks a false Review clear handoff. - Existing fixed-snapshot, desktop, deep-link, and offline read-only behavior remains intact. ## Non-duplication Searched all 711 historical issue titles, 702 pull requests, current releases, and recent commits through `e9d257e`. Closed #1415/#1416 built the standalone Human Gates inbox but did not integrate it with mobile Queues or Prepare Today; no open issue or recent commit covers this behavior.
timmy self-assigned this 2026-08-26 02:28:11 +00:00
timmy closed this issue 2026-08-26 03:42:47 +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#1417
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?