[thebrandonlucas]

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

Help	Before	After
Examples	payments send, payments receive, wallets create	Every command that changes something and every alias, plus login, auth import-key, profiles create, context, convert, payments get --wait, checkout events watch; each under a # comment
-h	Usage, options, and all notes	Usage and options only
--help	Same as -h	Adds notes, examples, and Learn more:
Guide link	None	Learn more: https://github.com/voltagecloud/voltage-cli/blob/<ref>/docs/<guide>
Root help	Commands and options	Adds common commands, the --execute rule, and a docs link

Docs ref: build.rs makes one decision for --version and the links. A clean build of a release tag links v<version>; any other build, including one without a git checkout, links master. The root docs link and every Learn more link use the same ref.

Examples live in one table keyed by OperationId (endpoint_examples) plus local_examples for the CLI's own commands, so the parse test and help share one source. -h no longer shows the friendly-flag requirements; they appear under --help.

Tests:

• Every non-GET operation and payment alias has at least one commented example in --help.
• Every command's Learn more link names a page that exists under docs/, and the ref is master or v<version>, the same for the root link.
• -h shows no notes.
• The existing parse test reads commented, multi-line examples and drops redirections, so every help example still parses and every change passes --execute or --dry-run. feat(cli)!: remove --dry-run, and describe every help example offline #30 also runs every help example offline.

Changes after review

• checkout sessions create: the example read @session.json and wrote --output-file session.json, so it always failed with "File exists". It now reads @session-request.json.
• wallets policies: the round trip sent the CLI's output envelope back as the policy body. It now saves only the policies: voltage wallets policies get WALLET_ID --profile prod --json | jq .data > policies.json. The wallets guide says the same.
• Links: before, every build linked blob/v0.1.0, a tag that has no guides, so every link failed. See "Docs ref" above.
• The arms use OperationId:: paths instead of a function-scope glob import.
• Wording: "without creating a payment", and CREDIT_LINE_ID as in the other examples.

Checks

On 37b663d:

• cargo fmt --check, cargo clippy --locked --all-targets -- -D warnings, cargo machete --with-metadata: pass.
• cargo test --locked: 99 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]

Looks good. Two suggestions below, neither blocking. CRAP on 2d41d78: no function at or above 20, highest api::wait_for_payment at 19.24; the full test suite passed in the same run.

The merge-base changed after approval.

The merge-base changed after approval.