Corrections batch for the CLI_DOCS content in lib/llm/index.js (written to ~/.claude/docs/, ~/.gemini/docs/, ~/.codex/docs/ on every setup):
- cli-m365.md (
llm/index.js:650,745): safety rules forbid the --confirm flag — cli-microsoft365 renamed it to --force in v6 (2023) and later removed it entirely. A fresh install gets v11+; the doc guards a flag that no longer exists. Reword to --force.
- cli-grafana.md (
llm/index.js:603-636): (a) states config at ~/.grafanactl/config.yaml — grafanactl actually uses the XDG config dir (~/.config/grafanactl/... on Linux, ~/Library/Application Support/... on macOS); (b) the doc is ~entirely logcli + raw HTTP traces despite grafanactl being what's installed. Rewrite alongside the gcx swap (sibling issue).
- cli-hcloud.md (
llm/index.js:1022): claims "Most delete commands need --yes to skip the prompt" — hcloud delete commands don't prompt and have no --yes flag. Verify against current hcloud and correct.
- cli-sqlcmd.md (
llm/index.js:50): example context list still includes prod-ro, which is decommissioned (prod is Azure MI via Entra, not a context).
While in there: the doc content lives as inline JS template literals — same maintainability concern as environment-setup's llm_internal.js (tracked there); consider moving to .md assets in the same refactor.
Corrections batch for the
CLI_DOCScontent inlib/llm/index.js(written to~/.claude/docs/,~/.gemini/docs/,~/.codex/docs/on every setup):llm/index.js:650,745): safety rules forbid the--confirmflag — cli-microsoft365 renamed it to--forcein v6 (2023) and later removed it entirely. A fresh install gets v11+; the doc guards a flag that no longer exists. Reword to--force.llm/index.js:603-636): (a) states config at~/.grafanactl/config.yaml— grafanactl actually uses the XDG config dir (~/.config/grafanactl/...on Linux,~/Library/Application Support/...on macOS); (b) the doc is ~entirely logcli + raw HTTP traces despite grafanactl being what's installed. Rewrite alongside the gcx swap (sibling issue).llm/index.js:1022): claims "Most delete commands need--yesto skip the prompt" — hcloud delete commands don't prompt and have no--yesflag. Verify against current hcloud and correct.llm/index.js:50): example context list still includesprod-ro, which is decommissioned (prod is Azure MI via Entra, not a context).While in there: the doc content lives as inline JS template literals — same maintainability concern as environment-setup's llm_internal.js (tracked there); consider moving to .md assets in the same refactor.