ci: e2e list reporter — per-test progress in job log

.gitea/workflows/ci.yml

@@ -187,7 +187,9 @@ jobs:
           NO_PROXY: app,localhost,127.0.0.1,.kkhost.pl
           no_proxy: app,localhost,127.0.0.1,.kkhost.pl
         # Connectivity diagnostics now run post-deploy in e2e/ci-diagnostics.ts (globalSetup).
-        run: npx playwright test
+        # --reporter=list prints each test as it completes (name + ✓/× + duration) for progress
+        # visibility in the job log; failure error context/snapshots are unchanged.
+        run: npx playwright test --reporter=list
 
       # The daemon is shared with production — never leave our stack or network behind.
       # -v drops the named DB volume so every run seeds fresh (no schema drift between PRs).

CHANGELOG.md

@@ -1,5 +1,8 @@
 # Changelog
 
+## v0.13.1 — 2026-09-19 08:09
+- CI e2e step now uses Playwright's list reporter so every test prints as it runs in the job log (progress visibility); failures still get full error context
+
 ## v0.12.3 — 2026-09-19 07:36
 - **e2e: removed the unreliable curved-route assertion from `map-interactions.spec.ts`.** The "route line has >2 coordinates in the routes source" check (added with v0.12.2) failed in CI and against the live instance even though the arc renders correctly — MapLibre's `querySourceFeatures` returns tile-simplified geometry at low zoom, so coordinate counts from it are not a reliable signal for what was pushed into the source. The curved arc remains fully covered by unit tests (`lib/mapData.test.ts`: 25 sampled coordinates, exact endpoints, curvature on long routes); the spec keeps all other steps (grounded plane draws no line, marker moves across polls, plane popup with status + route)
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "flight-ops",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "private": true,
   "scripts": {
     "dev": "next dev -p 3000",