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

Gate release candidates on a mobile offline filing journey #863

New Issue
Closed
opened 2026-08-15 01:49:52 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 01:49:52 +00:00
Owner
Copy Link

Problem

CI verifies unit tests and checksums, but never launches the built release in a browser. The highest-risk user flow—capture an issue on mobile, survive an offline reload, and deliver exactly once after reconnect—can regress across the service worker, IndexedDB, frontend bundle, API, and Gitea boundary while releases remain green.

Acceptance criteria

  • Run a real Chromium mobile viewport against the assembled release artifact.
  • Prove an issue queued offline survives reload and reaches a deterministic upstream exactly once after reconnect.
  • Assert payload and stable idempotency key; fail on browser errors or missing assets.
  • Make release-candidate publication depend on the browser gate.
  • Keep browser-only dependencies isolated from runtime dependencies.

Evidence / non-duplicate

Current .gitea/workflows/ci.yml only runs pytest before packaging. All 435 historical issue titles and recent commits were checked: #232 implements offline issue outbox behavior and #339 gates verifiable artifacts, but neither launches a release artifact in a browser; there is no Playwright/Selenium/WebDriver coverage in the repository.

## Problem CI verifies unit tests and checksums, but never launches the built release in a browser. The highest-risk user flow—capture an issue on mobile, survive an offline reload, and deliver exactly once after reconnect—can regress across the service worker, IndexedDB, frontend bundle, API, and Gitea boundary while releases remain green. ## Acceptance criteria - Run a real Chromium mobile viewport against the assembled release artifact. - Prove an issue queued offline survives reload and reaches a deterministic upstream exactly once after reconnect. - Assert payload and stable idempotency key; fail on browser errors or missing assets. - Make release-candidate publication depend on the browser gate. - Keep browser-only dependencies isolated from runtime dependencies. ## Evidence / non-duplicate Current `.gitea/workflows/ci.yml` only runs pytest before packaging. All 435 historical issue titles and recent commits were checked: #232 implements offline issue outbox behavior and #339 gates verifiable artifacts, but neither launches a release artifact in a browser; there is no Playwright/Selenium/WebDriver coverage in the repository.
timmy self-assigned this 2026-08-15 01:49:52 +00:00
timmy closed this issue 2026-08-15 02:17:34 +00:00
timmy reopened this issue 2026-08-15 02:21:02 +00:00
timmy closed this issue 2026-08-15 02:28:02 +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#863
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?