# X_DOC_SETUP_COMMAND_STALE

## Means

a page describes a `bun run setup` the scaffold does not write — a step list missing one of its steps, or a step count that is not the script's

## Typical cause

the six-step sequence is hand-copied into four pages and `x db seed` sat in the script with no CI path running it; `scripts/setup-commands.ts` derives the list from `binSetup()` in `packages/cli/src/templates/scaffold-bin.ts`, so a step added there makes the prose red on the same commit

## Fix

`bun run scripts/setup-commands.ts --json` prints the derived sequence; make the named line state it

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

---

## Means

a page enumerating what a scaffolded app's `bun run setup` runs describes a script `x new` does not write

## Typical cause

the six-step list is hand-copied into several pages and the script is one file — `x db seed` and `x manifest` were both added to it while the prose went on naming four steps. The list is derived from `binSetup()` in `packages/cli/src/templates/scaffold-bin.ts`, so a step added or renamed there turns the stale page red on the same commit

## Fix

`bun run scripts/setup-commands.ts --json` — each finding carries the sequence to write

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