Every retained automated test belongs to a named contract and declared execution environment. Pull-request validation always runs the complete portable suite.
Core gates
pnpm validateGitHub Actions runs this exact command. Focused checks are useful during iteration, but they do not establish pull-request readiness.
What each gate protects
| Gate | Protects |
|---|---|
pnpm validate | public boundaries, builds, workspace typechecks, hermetic tests, and portable release contracts |
validate:process | real process lifecycle, Local Core, and runner boundaries |
validate:postgres | persistence, migrations, concurrency, and replay contracts |
validate:chromium | browser-visible product journeys and contract behavior |
validate:audit | dependency, governance, and public-surface audit rules |
test-proofs:mutations | current killed mutations for high- and critical-risk contracts |
validate:release:macos | CLI and Desktop macOS package readiness during release preparation |
Process validation can be narrowed to one declared module while debugging:
pnpm validate:process:modules
pnpm validate:process -- --module unitpnpm validate:process remains the complete aggregate process gate.
Package and release proofs
Pack all nine public packages, inspect contents and exact internal pins, and install them into a clean external consumer. Release evidence also covers CLI archives/checksums, signed Desktop artifacts, deployment revision/digests, and registry metadata.
Documentation and public-boundary proofs
Validate metadata, search, navigation, source references, links, sitemap, executable examples, landing contracts, and a built exact-revision preview. Public claims must not precede the artifact or deployment gate they describe.
When a check fails
Use the failing check to narrow the investigation:
- an unintended prompt change
- runtime regression
- a broken package or architecture rule
- replay instability
Review the first failing check and its output before changing runtime behavior.