# X_DOC_SETUP_COMMANDS_UNSCANNED

## Means

the rule read no list, or no count, or could not read `binSetup()` at all

## Typical cause

a corpus rule that stops matching reports green forever, which is worse than the drift it was written for — one half can stop matching while the other still works, so each reports on its own

## Fix

`bun run scripts/setup-commands.ts --json`, then widen `DOC_GLOBS` in `scripts/doc-commands.ts` or `stepRows`/`countClaims` in `scripts/setup-commands.ts`

[CLI and verify](/error-codes#cli-and-verify)

---

## Means

no page enumerates `bun run setup`'s sequence, so the rule read nothing

## Typical cause

the globs match nothing, or every page that documented the script was deleted. Reported rather than skipped, for `X_DOC_GATE_STEPS_UNSCANNED`'s reason: a rule with no input is a false green

## Fix

`bun run scripts/setup-commands.ts --json` from the repo root

[CLI and verify](/error-codes#cli-and-verify)