docs: clarify update/lifecycle entry points via help text (BE-3001)

[mattmillerai]

ELI-5

comfy has four commands that sound like they might all "update" things, and it's confusing which does what:

• comfy update — updates ComfyUI itself (or comfy-cli).
• comfy node update — updates custom nodes.
• comfy manager — turns ComfyUI-Manager on/off and configures it. Not an updater.
• comfy standalone — downloads a standalone Python interpreter bundle. Not an updater.

This PR is help-text only — no renames, no aliases, no behavior change. It adds cross-references so --help steers you to the right command, and relabels the two that were mislabeled as "update-ish".

What changed

Command	Before	After
comfy update	Update ComfyUI Environment [all|comfy|cli]	+ To update custom nodes, use comfy node update.
comfy node update	Update custom nodes or ComfyUI	+ To update ComfyUI itself or the CLI, use comfy update.
comfy manager	Manage ComfyUI-Manager.	Enable/disable and configure ComfyUI-Manager (lifecycle, not updates).
comfy standalone	Download a standalone Python interpreter…	+ This bundles an interpreter; it does not update ComfyUI or custom nodes.

Notes / judgment calls

• node update kept its "or ComfyUI" wording (appended, not replaced). comfy node update all dispatches the same CM-CLI update all call that comfy update all uses, so "or ComfyUI" is factually accurate — removing it would be a regression. Followed the ticket's "append" instruction rather than rewording.
• No snapshot to regenerate. The comfy discover self-describing surface builds its command tree from the live Typer app at runtime (build_help_json), and its tests validate against JSON schemas, not exact help strings — so the new text flows through automatically. Full unit suite is green (2471 passed, 13 skipped).
• No confusing docs to fix. README already documents these commands in separate sections; none group them under a single "update" heading.
• Not a capability denial. The "lifecycle, not updates" / "does not update" phrasings are clarifications, not dead-ends — both real update paths (comfy update, comfy node update) exist and are explicitly cross-referenced.

Testing

• ruff format + ruff check clean on both touched files.
• comfy update|node update|manager|standalone --help render the new strings correctly.
• pytest tests/comfy_cli → 2471 passed, 13 skipped.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 86400873-874a-4c66-808a-88d51ba2fd8a

📥 Commits

Reviewing files that changed from the base of the PR and between a732f5c and 3e7bedb.

📒 Files selected for processing (2)

• comfy_cli/cmdline.py
• comfy_cli/command/custom_nodes/command.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch matt/be-3001-clarify-update-lifecycle-help

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch matt/be-3001-clarify-update-lifecycle-help

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🔍 Cursor Review — Consolidated panel

Triggered by @mattmillerai.

✅ No high-signal findings.

Panel: 6/8 reviewers contributed findings.

Reviewers that did not contribute: kimi-k2.5:adversarial (empty), kimi-k2.5:edge-case (empty)

[mattmillerai]

The failing Windows Specific Commands / test check is a pre-existing Windows-runner infra flake, not caused by this PR. It dies in the Install Dependencies step — uv fails to remove a locked pydantic_core.cp312-win_amd64.pyd (Access is denied. (os error 5)) — before any of this PR's code runs. It reproduces identically on rerun and this PR only edits Typer help= strings (docs-only), so it can't be the cause. All other checks (including the windows-latest platform matrix, ruff, and the Cursor review panel) are green; no review threads outstanding.

[mattmillerai]

🤖 The reviews loop filed Linear follow-up ticket(s) for review thread(s) deferred as out of scope for this PR:

• https://linear.app/comfyorg/issue/BE-3280|BE-3280 — Fix repo-wide 'Windows Specific Commands' CI failure (pydantic_core import / uv pip install)