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

Gate mobile Tomorrow conflict recovery on the packaged release #1170

New Issue
Closed
opened 2026-08-20 07:21:22 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-20 07:21:22 +00:00
Member
Copy Link

Evidence

The shipped mobile Tomorrow conflict recovery journey exists in tests/e2e/test_mobile_tomorrow_conflict_release.py, but .gitea/workflows/ci.yml omits it from the packaged browser gate. The journey passes against a locally assembled release artifact, proving the flow is runnable; because CI never invokes it, release candidates can publish without exercising either conflict-resolution path. A complete all-state title scan found no duplicate issue, and recent commits implement the flow but do not gate it.

User impact

Prevent release candidates from shipping a broken 320px/390px mobile recovery flow that can discard either the phone Tomorrow plan or newer server plan after an offline conflict.

Acceptance

  • Add a failing workflow contract test first that requires the Tomorrow conflict journey in the packaged browser gate.
  • Run the packaged journey at 320×568 and 390×844; both server-plan and phone-plan resolutions pass with 44px controls and no horizontal overflow.
  • Run the complete packaged browser job including the new gate.
  • Focused tests and the complete suite pass.
  • CI browser gate is green before release publication.
## Evidence The shipped mobile Tomorrow conflict recovery journey exists in `tests/e2e/test_mobile_tomorrow_conflict_release.py`, but `.gitea/workflows/ci.yml` omits it from the packaged browser gate. The journey passes against a locally assembled release artifact, proving the flow is runnable; because CI never invokes it, release candidates can publish without exercising either conflict-resolution path. A complete all-state title scan found no duplicate issue, and recent commits implement the flow but do not gate it. ## User impact Prevent release candidates from shipping a broken 320px/390px mobile recovery flow that can discard either the phone Tomorrow plan or newer server plan after an offline conflict. ## Acceptance - Add a failing workflow contract test first that requires the Tomorrow conflict journey in the packaged browser gate. - Run the packaged journey at 320×568 and 390×844; both server-plan and phone-plan resolutions pass with 44px controls and no horizontal overflow. - Run the complete packaged browser job including the new gate. - Focused tests and the complete suite pass. - CI browser gate is green before release publication.
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#1170
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?