docs(docs): gate stages (drift, advisories), native exposure note, CI target wording, check:all in WORKSPACE and TEST_STRATEGY

This commit is contained in:
bchanot committed 2026-10-13 09:46:07 +02:00
1 parent e58c7be362
commit 073b25e52b
4 files changed
+27 -10

No files matched your search

+10 -5
View File
@@ -76,12 +76,17 @@ Target after Step 1: roughly 230–250 cases, all current ones untouched.
- Golden PDFs are compared by extracted text and attachment JSON, not by
bytes (pdf-lib dates and ids vary); raster hash only on fixed-size inputs.
## 5. CI gates
## 5. Gates before a merge, and the CI target
Per PR: `pnpm typecheck`, `pnpm lint` (0 warnings), `pnpm test:run`,
`pnpm build`; when `supabase/` changes: `supabase db reset`, `supabase test
db`, types diff. Nightly: Playwright suite. Release: full RLS matrix,
backup/restore rehearsal checklist, `pnpm audit`, secret scan.
Today (2026-10-13) no CI runs on the forge; the gate is run on the
development machine: `pnpm check:all` (`docs/development/RUST.md` §4) before
every merge, plus `supabase db reset`, `supabase test db` and the types diff
when `supabase/` changes. The workflow files under `.gitea/workflows/` are
prepared for a future runner and call the same scripts.
CI target (planned): per PR the stages of `pnpm check:all`; nightly the
Playwright suite and `cargo deny check advisories`; at release the full RLS
matrix, the backup/restore rehearsal checklist, `pnpm audit`, a secret scan.
## 6. Numbers to track