fuz-stack

tooling · ready · docs.fuz.dev

fuz-stack 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 it uses

UsesKindDeclared inThrough
blake3 (declared by docs.fuz.dev)devpackage.json@fuzdev/blake3-wasm
fuz_code (declared by docs.fuz.dev)devpackage.json@fuzdev/fuz_code
fuz_css (declared by docs.fuz.dev)devpackage.json@fuzdev/fuz_css
fuz_schema (declared by docs.fuz.dev)devpackage.json@fuzdev/fuz_schema
fuz_ui (declared by docs.fuz.dev)devpackage.json@fuzdev/fuz_ui
fuz_util (declared by docs.fuz.dev)devpackage.json@fuzdev/fuz_util
gro (declared by docs.fuz.dev)devpackage.json@fuzdev/gro
mdz (declared by docs.fuz.dev)devpackage.json@fuzdev/mdz
svelte-docinfo (declared by docs.fuz.dev)devpackage.jsonsvelte-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.

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, format --check, lint (run before committing)
    line 70, 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 a CI step, on a push or a pull request, that runs gro check with --build.

.github/workflows/check.yml runs on push (branches main), pull_request (branches **), workflow_dispatch

build on ubuntu-latest

  1. uses actions/checkout, pinned to a commit
  2. Use Node.js ${{ matrix.node-version }}
    uses actions/setup-node, pinned to a commit
  3. npm ci
  4. npx @fuzdev/gro check --workspace --build

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.

In the opening of the coherence section

So part of the review happens after the fact. Work is reviewed before it is committed, and commits that have landed are reviewed too, by agents when asked and by the maintainer, for whom it is sometimes the first reading. The release is the checkpoint for that review: versions and publishing are the maintainer's, and a common pattern is to review all the work since the last release before making the next one.

From the coherence section's index.

Holds that name it

Gates

  • Types, tests, lints and format (every change): Type errors, regressions, lint errors and style drift. docs.fuz.dev 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. docs.fuz.dev is among the repos whose check script runs gro check.
  • Build (ci): A broken build. docs.fuz.dev 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. docs.fuz.dev is among the repos with a CI step, on a push or a pull request, that runs gro check with --workspace.
  • Format, lints as errors, tests and doc links (every change): Lint and test failures and broken doc links. Where: The Rust workspaces, less the CI gaps listed below, and less zervo, whose lints only warn and which checks no doc links.
  • 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.
  • Evidence links on this site (on demand): A link in this site's data whose file or heading is gone. Where: This site.
  • Wall time and instruction counts against a base (on demand): A performance regression: tsv fails a row past a committed percentage, and gro asks for a written reason. Where: gro and tsv.

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

  • Delete files or data (dry run by default): No public rule keeps deletion with the maintainer. In the stack's own Rust tools a new command that is hard to undo is a dry run until it is given an explicit flag.
  • Change a version or a changelog (written rule): Only a written rule: no gate detects the change.
  • Add or upgrade a dependency (written rule): Only a written rule, with an allowlist to choose from. fuz_schema alone has a test that fails on a runtime dependency.
  • Create a package or a crate (written rule): Only a written rule: the release audit checks the crate graph, not new members, and tsv asks only that a new crate declare whether it publishes.

From Actions kept with a person.

Rules that moved down

  • Add a crate to the CI list by hand when it gains a database suite became: A test that holds the CI lists to the tree, since a missing entry left the job green.
  • Copy the workspace's whole lint table into a crate that must differ on one lint became: The release audit fails a copied table that has dropped a lint or changed a level.
  • Look up the home directory one way became: One hardened function, and in fuz and fuz_forge a lint that refuses the standard one. A direct read of the variable is still only a rule.
  • Keep each table's column list in step with its schema became: A test that holds each list to the live schema, in both directions.
  • Keep test-only code out of a release build became: The test-only code is a crate of its own, and the release audit refuses it in a shipped binary.

From Rules that moved down.

Values

  • Passes the question of performance: The fuz-stack performance reference, where a claim comes from a harness and states its noise floor
  • Passes the question of controllability: In the source: the fuz-stack dependency injection convention, where a side effect is a parameter and a root decides what is passed
  • A context: WASM loaded by a page. The build is chosen by measurement per runtime, and where bundle size matters the small one is right. The WASM reference
  • A context: WASM run by a host. A host can spend bytes for speed where a browser bundle cannot. The WASM reference

From the values page.