zap
native and data · early · TypeScript, Rust · zap.fuz.dev
zap as this site sees it: what its repo's own files declare, and every record on the coherence and values pages that names it or links it. This page is computed and adds nothing of its own. For what the project is, see the Fuz stack page.
What uses it
The stack repos that declare a dependency on it. A breaking change has to be carried through each of them, and through any consumer that no manifest declares. Only the stack's own projects are listed, so a consumer outside the stack is not here.
| Used by | Kind | Declared in | Through |
|---|---|---|---|
| fuz_forge | dev | package.json | @fuzdev/zap |
What it uses
| Uses | Kind | Declared in | Through |
|---|---|---|---|
| fuz | runtime | Cargo.toml(path) | fuz_eval |
| blake3 | dev | package.json | @fuzdev/blake3-wasm |
| fuz_code | dev | package.json | @fuzdev/fuz_code |
| fuz_css | dev | package.json | @fuzdev/fuz_css |
| fuz_schema | dev | package.json | @fuzdev/fuz_schema |
| fuz_ui | dev | package.json | @fuzdev/fuz_ui |
| fuz_util | dev | package.json | @fuzdev/fuz_util |
| gro | dev | package.json | @fuzdev/gro |
| mdz | dev | package.json | @fuzdev/mdz |
| svelte-docinfo | dev | package.json | svelte-docinfo |
Read from the repos' manifests on . Only each repo's root manifests are read. A manifest shows what a repo declares, which is not always what its code imports, and a dependency that no manifest states, such as a sibling checkout a test reads, is not here. The kind is the manifest table a dependency is declared in, not how much it matters: an app that bundles what it builds declares everything as dev. See every dependency in the stack.
What it declares from outside the stack
- runtime
- Cargo.toml: argh, blake3, nix, reqwest, ring, rustix, rustls, serde, serde_json, tempfile, thiserror, time, tokio
Read from the repo on . What a repo's manifests declare from outside the stack, by name and without versions. The dev tables are left out, so what an app bundles from its dev table is not here. For a Cargo workspace the list is every crate's together, and it is what is declared, not what a release build links. A crate is left out as tooling only when it is named xtask or testing_*, or the release audit marks it dev-only, so what a bench, debug or test-support crate under another name uses is listed with the rest. See everything the stack declares.
Its check script and CI
The check script of its package.json:
gro check
How its CLAUDE.md comments its check command:
gro check # typecheck, test, gen --check, lint, format check (run before committing)
line 102, marked as the command to run before committing
It is among the repos whose check script runs gro check; with a CI step, on a push or a pull request, that runs gro check with --workspace; with an exports map in package.json, and a CI step, on a push or a pull request, that runs gro check with --workspace; with a CI step, on a push or a pull request, that runs gro check with --build; with a Cargo workspace at the root.
.github/workflows/check.yml runs on push (branches main), pull_request (branches **), workflow_dispatch
check on ubuntu-latest
- uses
actions/checkout, pinned to a commit - uses
actions/checkout, pinned to a commit - Install Rust
rustup toolchain install --no-self-update rustup show active-toolchain cargo --version
- uses
Swatinem/rust-cache, pinned to a commit - Use Node.js 24.14 uses
actions/setup-node, pinned to a commit -
npm ci
- Install BusyBox and acl
if ! command -v busybox >/dev/null || ! command -v setfacl >/dev/null; then sudo apt-get update sudo apt-get install -y busybox acl fi busybox true getfacl --version
- Format
cargo fmt -p zap -p zap_core -p zap_types -p xtask --check
- Clippy
cargo clippy --locked --workspace --all-targets -- -D warnings
- Test
cargo test --locked --workspace
- Test (umask 000)
umask 000 cargo test --locked --workspace
- Note the e2e's skip and verify its zap binary
echo "::warning::zap config validate e2e skipped: no fgro build in CI (ZAP_FGRO unset)" target/debug/zap version
- gro check
npx @fuzdev/gro check --workspace --build
- Release dep-graph audit
cargo xtask check-release
- Rustdoc
cargo doc --locked --workspace --no-deps --all-features --document-private-items
Read from the repo on . A workflow's jobs and steps are as the file writes them: a step's command, or the action it uses without its version. An action's inputs, a matrix's values, permissions, environment and working directories are left out, and nothing here says which command is the gate. A line is quoted when it sits in a code block of the repo's CLAUDE.md, has a # comment after the command, and either is the command gro check or npm run check, or has a comment that says to run it before committing. A repo that describes its check command in a sentence or a list, or in another file, has no line here. Every file is read at the repo's main branch as the checkout last fetched it, so nothing uncommitted or unpushed is here. See every repo's checks.
Holds that name it
- In places: Tool: Suites that fail on a skip — A gate stops gating
- In places: Tool: Deny rules and dry runs — An unattended session does something irreversible
Comparisons that name it
| Compared | Against | Kind | Runs | Source |
|---|---|---|---|---|
| zap, working tree | zap, previous main build | Previous | On demand | differential harness |
From Oracles in use.
Gates
- Types, tests, lints and format (every change): Type errors, regressions, lint errors and style drift. zap is among the repos whose check script runs gro check.
- Drift in generated files (every change): A generated file that no longer matches its source. zap is among the repos whose check script runs gro check.
- Drift in the package exports map (ci): An exports map that no longer matches the source, which the local gate rewrites instead of failing on. zap is among 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.
- Build (ci): A broken build. zap is among the repos with a CI step, on a push or a pull request, that runs gro check with --build.
- A clean tree after the run, and no TODO docs at the root (ci): Uncommitted output and a TODO Markdown file at the repo root. zap is among the repos with a CI step, on a push or a pull request, that runs gro check with --workspace.
- Release audit (every change): A forbidden crate or a test-only feature in a release build, a broken layering rule, and a copied lint table that has drifted. Where: fuz, fuz_forge and zap. pglet runs an audit of its own, for its test-only crate alone.
- Required programs and suites (every change): A suite that passes by skipping: a program a test needs is missing, or a database suite is left off the CI list. Where: zap for programs, fuz for the CI list.
- 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
From Gates. A gate is listed here when its row names the project or links its repo, or speaks of a class of repos that the snapshot puts this one in.
Actions kept with a person
- Deploy a site or a server (permission rule, dry run by default, written rule): The harness denies the site deploy command, in settings that are not public, and the deploy task of gro has no dry default. A server deploy through zap changes nothing without an explicit flag and runs only a plan it has already previewed, which a session can do itself, so there the written rule is what holds.
Values
- A decision: security over speed. Security controls are read from the live machine on every run, with no cache. Cost: Every plan reads them again instead of trusting a stored verdict. security
- Passes the question of controllability: At run time: zap's rule that a real run executes only a plan it has already previewed
- What a reader can verify, content addressing: zap pins each fetched file, build source and apt key by the BLAKE3 of the fetched bytes
- A limit of what a reader can verify, reproducible builds: zap's lock says a build of
fgrois not reproducible across machines, so its pin names one build
From the values page.