corpora

tooling ยท ready

corpora 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 devpackage.json@fuzdev/blake3-wasm
fuz_schema devpackage.json@fuzdev/fuz_schema
fuz_util devpackage.json@fuzdev/fuz_util
gro devpackage.json@fuzdev/gro

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:

  • npm run check  # gro check: typecheck + vitest + gen + format; never reaches collections/
    line 34

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.

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

check on ubuntu-latest

  1. uses actions/checkout, pinned to a commit
  2. Use Node.js 24.14
    uses actions/setup-node, pinned to a commit
  3. npm ci
  4. npx @fuzdev/gro check --workspace
  5. npm run materialize:check

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.

Gates

  • Types, tests, lints and format (every change): Type errors, regressions, lint errors and style drift. corpora 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. corpora is among the repos whose check script runs gro check.
  • 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. corpora is among the repos with a CI step, on a push or a pull request, that runs gro check with --workspace.
  • A snapshot that reproduces from its pins (ci): A corpus that no longer matches its pinned upstreams, byte for byte, or whose license no longer reads as declared. Where: corpora.

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.