📝 Confirm pre-push stays a local quick check

Pre-push runs npm test only. That is intended: the staged-file checks
are pre-commit's job and whole-project correctness is CI's, which
checks the pushed commits' content. Dirty working-tree files are out
of scope for a local check that CI backs up, so no dirty-tree guard is
added.

backlog.tasks

@@ -35,9 +35,9 @@ Setup:
     - `publish: needs: build`, then re-runs `npm ci` + `build` from scratch, discarding the tested output
     - tag push pays a double build and the two builds could differ
     ✔ Persist `dist/` as an artifact in `build` and consume it in `publish` @done
-☐ Confirm pre-push gate strength
-    - pre-push runs `npm test` (`check:tsc` + tests), not full `check`; oxlint/oxfmt/cspell drift on unstaged content is only caught per-staged-file at commit or whole-project in CI
-    ☐ Confirm this is intended per the feedback-tier table, or point pre-push at `verify`
+✔ Confirm pre-push gate strength @done
+    - pre-push runs `npm test` (`check:tsc` + tests), not full `check`; the staged-file oxlint/oxfmt/cspell checks live in pre-commit, whole-project correctness in CI
+    ✔ Confirmed intended: pre-push is a local quick check, not a gate — CI on Gitea is the authoritative whole-project gate and checks the pushed commits' content; dirty working-tree files are out of scope by design @done
 ✔ Clean stale `coverage/` in `npm run clean` @done
     ✔ `npm run clean` only removes `dist`; add `coverage` (both are gitignored but bloat the working tree) @done
 ✔ Drop redundant `main`/`types` top-level fields @done