docs: regenerate forge-cli.md for pr status's positional

`docs/tools/forge-cli.md` is generated from the clap tree, so changing an
argument or its doc comment changes that file too. The freshness check in
`checks.hive-forge-docs` is what says so, and it is what failed here —
after 8m44s, on a PR that was already approved.

Regenerated, no hand edits. Two hunks, both the `pr status` section, and
`nix fmt` leaves the result byte-identical so the formatter and the
generator are not fighting over it.

Part of #4182.
This commit is contained in:
atlas 2026-09-11 03:35:18 +02:00 committed by mara
commit 23850e633b

View file

@ -548,12 +548,16 @@ Create a pull request
PR health view: mergeable / CI / reviews
**Usage:** `hive-forge pr status [OPTIONS]`
**Usage:** `hive-forge pr status [OPTIONS] [NUMBER]`
###### **Arguments:**
* `<NUMBER>` — PR number — full health view (mergeable, CI, reviews, last comment). Mutually exclusive with `--sha`
###### **Options:**
* `--pr <PR>` — PR number — full health view (mergeable, CI, reviews, last comment). Mutually exclusive with `--sha`
* `--sha <SHA>` — Explicit commit sha (or ref) — CI-only fast path. Mutually exclusive with `--pr`
* `--pr <PR>`Same as passing the number positionally. Kept because this verb accepted only this spelling before the positional existed
* `--sha <SHA>` — Explicit commit sha (or ref) — CI-only fast path. Mutually exclusive with a PR number