[thebrandonlucas]

Stack: master ← #26 ← #27 ← #28 ← #29 ← #30 ← #55 ← #60. #20, #22, #57, #24 and #19 are merged.

Page	Source	Kept true by
docs/reference/global-flags.md	Rendered from GlobalFlags	A golden test; VOLTAGE_BLESS=1 cargo test regenerates it
docs/reference/environment.md	Hand-written: every VOLTAGE_* variable, XDG_CONFIG_HOME, COLUMNS, and the flag that beats each	A test that every VOLTAGE_* literal in src/ and its subdirectories is listed
docs/reference/configuration.md	Hand-written: the configuration directory, config.toml, credential stores, the lock, the request journal	The relative-link and anchor check
docs/reference/exit-codes.md	Existing	A test that every ErrorKind code is listed; an exhaustive match makes a new kind fail to compile until it is added

The docs index links the new pages, and the development guide explains VOLTAGE_BLESS.

Not in this PR: a help-rendered command reference. Rendering --help for all 60 commands would exceed the 1,000-line limit on its own; --help now carries examples and a guide link (#27), and docs/commands.md keeps the generated route table.

Changes after review

• --config-dir documents its real default: VOLTAGE_CONFIG_DIR, else $XDG_CONFIG_HOME/voltage, else ~/.config/voltage. Before, global-flags.md said only ~/.config/voltage, which contradicted configuration.md.
• The variable scan walks src/ recursively (rust_sources), with a test that it reaches src/output/human.rs. VOLTAGE_DOCS_REF (feat(cli): show examples and a guide link in every command's help #27, a build-time value) is excluded.
• ErrorKind is imported at module scope, and the exhaustive list is an error_kinds() helper that docs: add troubleshooting, getting started, a changelog, its CI check, and a PR template #29 reuses.
• The generated header says --execute is per command, not global, and links the safety model.

Checks

On e1436ed:

• cargo fmt --check, cargo clippy --locked --all-targets -- -D warnings, cargo machete --with-metadata: pass.
• cargo test --locked: 102 unit and 86 integration tests pass. VOLTAGE_BLESS=1 cargo test --locked leaves the tree clean.
• python3 scripts/check-coverage.py: pass.
• CRAP (scripts/crap-report.sh): no function at or above 20. Highest is api::wait_for_payment at 19.24, unchanged from or lower than master (19.66).
• Skill review: voltage-pr-review and the voltage-backend-engineering Rust checklist, against the stack base. Findings are fixed in this commit.

Not run: the staging and live tutorials, which need credentials.

[tee8z]

One sentence in environment.md describes the precedence wrongly; the rest checked out against the code (config directory order and checks, files, VOLTAGE_EXECUTE values, every variable the code reads). The other two comments are optional. CRAP on 0a93ed7: no function at or above 20, highest api::wait_for_payment at 19.24; the full test suite passed in the same run.