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

Gate releases on the packaged mobile Find Work journey #981

New Issue
Closed
opened 2026-08-16 18:50:59 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-16 18:50:59 +00:00
Member
Copy Link

Problem

The mobile Find Work workflow now spans discovery, review, capacity fitting, assignment, and Today queueing, but release CI does not exercise that integrated journey. Existing tests use Node doubles/source assertions, while the browser gate covers only offline filing and Search Preview. A packaged asset or API integration regression can therefore ship while preventing phone users from starting work.

Vertical slice

Add a deterministic Playwright journey against the assembled release archive that signs in at phone width, discovers available work, selects and reviews it, fits estimates to Today capacity, assigns exactly once, and verifies the completed Today handoff. Extend the fake Gitea fixture only for the APIs this user journey needs and make release promotion depend on the journey.

Acceptance criteria

  • The test serves the unpacked release archive, never checkout frontend files.
  • At 390x844, Discover → Review → Fit & assign works without horizontal overflow; workflow controls meet 44px touch targets.
  • Removing a selected issue updates the review and final assignment payload.
  • Successful confirmation performs exactly one upstream assignment and creates one Today item.
  • Browser/page errors and failed asset requests fail the journey.
  • Gitea Actions runs the journey before release-candidate publication.
  • Unit and full test suites pass.

Non-duplication evidence

All 493 historical issue titles, eight open issues, open PRs, and recent origin/main commits were checked. #979 implemented guided Find Work navigation; #863 added an offline-filing artifact gate. Neither tests this packaged Find Work journey, and no open or closed title describes it.

## Problem The mobile Find Work workflow now spans discovery, review, capacity fitting, assignment, and Today queueing, but release CI does not exercise that integrated journey. Existing tests use Node doubles/source assertions, while the browser gate covers only offline filing and Search Preview. A packaged asset or API integration regression can therefore ship while preventing phone users from starting work. ## Vertical slice Add a deterministic Playwright journey against the assembled release archive that signs in at phone width, discovers available work, selects and reviews it, fits estimates to Today capacity, assigns exactly once, and verifies the completed Today handoff. Extend the fake Gitea fixture only for the APIs this user journey needs and make release promotion depend on the journey. ## Acceptance criteria - The test serves the unpacked release archive, never checkout frontend files. - At 390x844, Discover → Review → Fit & assign works without horizontal overflow; workflow controls meet 44px touch targets. - Removing a selected issue updates the review and final assignment payload. - Successful confirmation performs exactly one upstream assignment and creates one Today item. - Browser/page errors and failed asset requests fail the journey. - Gitea Actions runs the journey before release-candidate publication. - Unit and full test suites pass. ## Non-duplication evidence All 493 historical issue titles, eight open issues, open PRs, and recent origin/main commits were checked. #979 implemented guided Find Work navigation; #863 added an offline-filing artifact gate. Neither tests this packaged Find Work journey, and no open or closed title describes it.
timmy was assigned by rockachopa 2026-08-16 18:50:59 +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#981
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?