browser tests run only by hand: the suites that launch Chrome / Chromium move to tests/browser/*.browser.ts (bun test, ci, ci:quick and the Forgejo workflows never pick them up; bun run test:browser runs them); the desktop boot check leaves bun run ci (it stays in desktop-release.ts mac at release time); CI=full is gone: Forgejo's ci runs the Rust steps when the push changed a Rust input (STOREBOUND_CI_BASE=HEAD~1), no Playwright install; CONTRIBUTING

.forgejo/workflows/ci.yml

@@ -1,7 +1,8 @@
 # Every push to main is a release candidate (docs/desktop-release.md, "Release candidates"). In parallel:
 #   ci          bun run ci (adapters, desktop version, tests, typecheck, desktop i18n / typecheck / build, the boot check
 #               in headless Chromium, desktop Rust tests and clippy, scrub); tools/ci.ts runs it as a task graph with
-#               parallel test shards on the one Linux runner. CI=full runs the Rust steps on every push.
+#               parallel test shards on the one Linux runner; no browser test runs here (tests/browser/, `bun run
+#               test:browser` by hand). The Rust steps run when the push changed a Rust input (STOREBOUND_CI_BASE).
 #   acceptance  the release acceptance matrix (tools/acceptance.ts): every user-facing command from the packed npm
 #               tarball with real piped stdin, Linux and Windows x Node 20 / Node 22 / Bun.
 #   linux       AppImage + deb (path-free build), self-tests, both started under Xvfb, privacy scan.
@@ -26,7 +27,6 @@ env:
   BUN_VERSION: '1.4.0'
   CARGO_TERM_COLOR: never
   CARGO_INCREMENTAL: '0'
-  CI: full
 
 jobs:
   gate:
@@ -63,6 +63,8 @@ jobs:
     timeout-minutes: 60
     steps:
       - uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
       - uses: ./.forgejo/actions/linux-setup
         with:
           cache-key: ci