bodycheck

Overview ¶

Command bodycheck is the automated CI guard for the §9 anti-falsehood discipline (see CLAUDE.md §9). The drift guard in check-coverage.sh only inspects frontmatter; this tool inspects the BODY of every public docs page (website/docs/**) — the place where the three P0 falsehoods of 2026-05-24 hid (a wrong Go version, a non-existent function name, an inexistent YAML key). It complements (does not replace) the docs-content-verifier subagent.

Checks:

1. [hard] Go-version claims (`go 1.XX` / `Go 1.XX` / `1.XX+`) must match the `go` directive in go.mod.
2. [hard] Go symbols of the form `pkg.Symbol` in fenced ```go blocks that reference a Nucleus package must exist in the freeze baseline. Symbols qualified by a block-local identifier (an alias or var defined in the same example) are skipped, as are non-Nucleus packages (stdlib, etc.).
3. [advisory] YAML keys in nucleus-config blocks should exist in the config-key registry. Reported but not failing, because distinguishing a nucleus.yml block from an arbitrary YAML example is heuristic.
4. [hard] `db:"…"` struct tags in ```go blocks must parse cleanly against the REAL parser (pkg/model.ExtractMeta over a synthetic field): any directive the parser would silently ignore fails the check. This is the guard for NU5-1 — the website taught `db:"id,primary"` / `fk=…` for four audit rounds while parseDBTag never recognized any of it.

Usage: bodycheck [-root .] [-docs website/docs] [-strict]