Gates

A gate is a check that gives a verdict on a change. These are the kinds the stack runs, sorted by how soon each reports, as the oracles are.

The holds whose instances this table lists: Lints for the mechanical rules (Design drifts to the model's average); Drift checks and twin suites (Two copies drift apart); Oracles, mutants and control cases (Green but wrong); Suppressions that expire (A check is silenced instead of satisfied); Suites that fail on a skip (A gate stops gating); CI reruns the gate (A slow check gets skipped); Link and drift checks (A stale statement is trusted); Committed size limits (A predicted speedup that is not one); The gate (A known mistake comes back); Checks at the edges (Private content reaches a public repo)

Where a row speaks of a class of repos, the repos under it are the class's members, computed from this site's snapshot of each repo's files. A repo that reaches the same check another way, such as through a script its check script calls, is not listed unless the row names it. Read from the repos on .

A row may carry probes: a string that a named file, check script or CI step of the repo must have, or must not have, for the row to still be true in the way a file can show. The tests of this site check the ones about a check script or a CI step against its snapshot of the repos, and the evidence task checks the ones about a file. A probe that passes says the file, script or step still has the text the row depends on. It does not say the check is sound. A probe reads only the text it names, so one that says a step is absent does not see the same thing reached through another script or switched on by an environment variable.

  • Every change In the gate a session runs before landing, and again in CI.
  • CI In CI on a push to the main branch or a pull request, and not in the local gate.
  • Release Before a release, and not on each change.
  • On demand When someone chooses to run it.
GateCatchesRunsWhereSource
Types, tests, lints and formatType errors, regressions, lint errors and style driftEvery changeThe repos whose check script runs gro's check, with lints where the repo has a lint config. pglet's check script reaches it through a script of its own, for its TypeScript check task
2 probes
  • the check script of pglet has npm run check:ts
  • pglet/package.json has "check:ts": "gro check
Drift in generated filesA generated file that no longer matches its sourceEvery changeThe repos whose check script runs gro's check, and pglet's TypeScript the same way checking generated files
2 probes
  • the check script of pglet has npm run check:ts
  • pglet/package.json has "check:ts": "gro check
Format, lints as errors, tests and doc linksLint and test failures and broken doc linksEvery changeThe Rust workspaces, less the CI gaps listed below, and less zervo, whose lints only warn and which checks no doc links Rust gate
1 probe
  • zervo/Cargo.toml has all = { level = "warn"
Release auditA forbidden crate or a test-only feature in a release build, a broken layering rule, and a copied lint table that has driftedEvery changefuz, fuz_forge and zap. pglet runs an audit of its own, for its test-only crate alone release audit
9 probes
  • the CI steps of fuz have cargo xtask check-release
  • fuz/CLAUDE.md has cargo xtask check-release
  • the CI steps of fuz_forge have cargo xtask check-release
  • fuz_forge/CLAUDE.md has cargo xtask check-release
  • the CI steps of zap have cargo xtask check-release
  • zap/CLAUDE.md has cargo xtask check-release
  • the check script of pglet has npm run check:release
  • the CI steps of pglet have npm run check
  • pglet/crates/xtask/src/release.rs has FORBIDDEN_CRATES: &[&str] = &["pglet_testing"]
Pinned pass countsConformance coverage that quietly shrinks or shiftsEvery changepglet, and tsv's fixture validation pinned counts
5 probes
  • the CI steps of pglet have cargo xtask gates --check
  • pglet/tests/gates_baseline.txt has fixtures.passed
  • the check script of tsv has npm run test &&
  • the CI steps of tsv have npm run check
  • tsv/tests/fixtures_tests.rs has FIXTURES_MIN
Required programs and suitesA suite that passes by skipping: a program a test needs is missing, or a database suite is left off the CI listEvery changezap for programs, fuz for the CI list testing rules
4 probes
  • the CI steps of zap have cargo test
  • zap/crates/zap/tests/required_programs.rs has the_programs_the_gated_tests_run_are_installed
  • the CI steps of fuz have cargo test
  • fuz/crates/xtask/tests/db_suite_lists.rs has .github/workflows/check.yml
Links and anchors in MarkdownA dead relative link or anchor in any Markdown file of the repoEvery changetsv conformance audit
2 probes
  • the check script of tsv has npm run conformance:audit
  • the CI steps of tsv have npm run check
Size limits in the gate setA WebAssembly build that has grownEvery changepglet gate runner
2 probes
  • pglet/crates/xtask/src/gates.rs has size:check
  • the CI steps of pglet have npm run size:check
A budget for the startup snapshotA startup snapshot that has grown past its committed budgetEvery changegro baseline suite
3 probes
  • the CI steps of gro have cargo xtask check-rust
  • gro/crates/xtask/src/snapshot.rs has suites/baseline/suite.json
  • gro/crates/gro_bench/suites/baseline/suite.json has "snapshot_bytes"
Drift in the package exports mapAn exports map that no longer matches the source, which the local gate rewrites instead of failing onCIThe repos with an exports map whose CI runs gro's check with its workspace flag
The repos with an exports map in package.json, and a CI step, on a push or a pull request, that runs gro check with --workspace: zzz, fuz_forge, fuz_app, fuz_css, fuz_ui, fuz_code, mdz, fuz_blog, gro, svelte-docinfo, fuz_repos, fuz_util, fuz_schema, zap
check task
BuildA broken buildCIThe repos whose CI runs gro's check with its build flag
The repos with a CI step, on a push or a pull request, that runs gro check with --build: fuz_template, zzz, fuz_forge, fuz_app, fuz_css, fuz_ui, fuz_code, mdz, fuz_blog, gro, tsv.fuz.dev, svelte-docinfo, fuz_repos, docs.fuz.dev, fuz_util, fuz_schema, zap
check task
A clean tree after the run, and no TODO docs at the rootUncommitted output and a TODO Markdown file at the repo rootCIThe repos whose CI runs gro's check with its workspace flag
The repos with a CI step, on a push or a pull request, that runs gro check with --workspace: fuz_template, zzz, fuz_forge, fuz_app, fuz_css, fuz_ui, fuz_code, mdz, fuz_blog, gro, tsv.fuz.dev, svelte-docinfo, fuz_repos, docs.fuz.dev, corpora, fuz_util, fuz_schema, zap
check task
Size limits in CIA WebAssembly build or a native addon that has grownCItsv and fuz_schema artifact validation
3 probes
  • the CI steps of tsv have npm run validate:artifacts
  • the CI steps of tsv have npm run validate:napi
  • the CI steps of fuz_schema have wasm_size_ceiling.txt
Mutation gateA test that passes whether or not the code is rightCIfuz's install script mutation gate
1 probe
  • the CI steps of fuz have scripts/install-test-mutants.sh
A snapshot that reproduces from its pinsA corpus that no longer matches its pinned upstreams, byte for byte, or whose license no longer reads as declaredCIcorpora CI workflow
1 probe
  • the CI steps of corpora have npm run materialize:check
Conformance against committed ledgersA parser or formatter difference that no ledger recordsReleasetsv audits
6 probes
  • tsv/scripts/publish.ts has ['run', 'conformance:all']
  • tsv/package.json has "conformance:all"
  • the check script of tsv lacks conformance:all
  • the CI steps of tsv lack conformance:all
  • the check script of tsv lacks corpus:compare
  • the CI steps of tsv lack corpus:compare
Mutation runA test that passes whether or not the code is rightOn demandfuz_schema mutants
3 probes
  • fuz_schema/package.json has "mutate"
  • fuz_schema/src/test/mutants.ts exists
  • the CI steps of fuz_schema lack mutate
Evidence links on this siteA link in this site's data whose file or heading is goneOn demandThis site evidence check
2 probes
  • docs.fuz.dev/src/routes/evidence_check.task.ts exists
  • the CI steps of docs.fuz.dev lack evidence_check
Wall time and instruction counts against a baseA performance regression: tsv fails a row past a committed percentage, and gro asks for a written reasonOn demandgro and tsv measure
5 probes
  • gro/crates/xtask/src/bench/base.rs has --base
  • the CI steps of gro lack xtask bench
  • tsv/package.json has "perf:ab"
  • the check script of tsv lacks perf:ab
  • the CI steps of tsv lack perf:ab

CI gaps

Where CI runs less than the local gate, or does not run:

  • The Rust gate of zzz and its cross-backend tests run only locally, and its CI is Node-only
  • zervo's CI builds and tests nothing, because its browser engine is too heavy to build on each push
  • blake3 has no CI, so its size limits and test vectors run only by hand and before a release
  • tsv-format has no CI, so its typecheck, build and tests run only locally
  • tsv's CI skips the two legs of its gate that read sibling checkouts, the wider Prettier round trip and corpus discovery
  • pglet's CI leaves out the WebAssembly and concurrency suites of its gate set
  • zap's CI has no build of gro's runtime, so the tests that evaluate config through it are skipped there, by an explicit allowance