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

Keep Human Gate release decisions visible and actionable on mobile #1439

New Issue
Closed
opened 2026-08-26 17:52:52 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-26 17:52:52 +00:00
Member
Copy Link

User problem

Human Gate evidence reviews are long on phones, but Hold/Release controls remain at the bottom and validation errors render in the off-screen header. Operators can lose decision context, repeat taps, or abandon a release review.

Evidence

  • frontend/human-gates.js renders decisions after the entire evidence/checklist form and already identifies exact validation failures.
  • frontend/progressive-human-gates.js and frontend/dashboard.js report those failures only in the sheet header.
  • Existing mobile E2E coverage does not assert action visibility or field-targeted validation at phone viewports.
  • Historical-title/commit review found Human Gate inbox, progressive loading, fresh authorization, refresh, draft recovery, and notifications, but no Human Gate mobile decision tray. Issue #763 covered Updates, not Human Gates.

Acceptance criteria

  • On phone viewports, Hold and Release remain thumb-reachable without obscuring the final fields.
  • Tray reports confirmation readiness and uses safe-area spacing with >=44px action targets.
  • Invalid Release/Hold sends no request, reports the error beside the actions, and focuses/scrolls the first required field.
  • A valid decision remains single-flight, disables both actions, and advances using the existing fixed snapshot.
  • Desktop, draft recovery, and inbox-zero behavior remain intact.
  • Behavioral frontend tests and rendered mobile E2E coverage pass.
## User problem Human Gate evidence reviews are long on phones, but Hold/Release controls remain at the bottom and validation errors render in the off-screen header. Operators can lose decision context, repeat taps, or abandon a release review. ## Evidence - `frontend/human-gates.js` renders decisions after the entire evidence/checklist form and already identifies exact validation failures. - `frontend/progressive-human-gates.js` and `frontend/dashboard.js` report those failures only in the sheet header. - Existing mobile E2E coverage does not assert action visibility or field-targeted validation at phone viewports. - Historical-title/commit review found Human Gate inbox, progressive loading, fresh authorization, refresh, draft recovery, and notifications, but no Human Gate mobile decision tray. Issue #763 covered Updates, not Human Gates. ## Acceptance criteria - On phone viewports, Hold and Release remain thumb-reachable without obscuring the final fields. - Tray reports confirmation readiness and uses safe-area spacing with >=44px action targets. - Invalid Release/Hold sends no request, reports the error beside the actions, and focuses/scrolls the first required field. - A valid decision remains single-flight, disables both actions, and advances using the existing fixed snapshot. - Desktop, draft recovery, and inbox-zero behavior remain intact. - Behavioral frontend tests and rendered mobile E2E coverage pass.
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#1439
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?