refactor: sweep dead-code cluster — unused Graph query API, vestigial installers, orphaned helpers (BE-4354)

[mattmillerai]

ELI-5

Some code in comfy-cli was written but never actually used anywhere — a handful of
query helpers on the CQL Graph, two installer methods, a couple of module-level
helper functions, and a commented-out TODO block. Nothing calls them. This PR
deletes that dead code (~100 lines removed) so the codebase carries less unused
surface. Git history keeps it if it's ever wanted again.

What & why

Dead-code cluster sweep (BE-4354). Every deleted symbol was re-verified as
zero-reference by a word-boundary grep across the whole repo (*.py, *.toml,
*.md) immediately before deletion, and cql/engine.py was confirmed to contain no
getattr/__getattr__ dynamic dispatch that could reach the Graph methods.

Deleted:

• cql/engine.py Graph: pack_nodes, label_nodes, cloud_disabled_nodes,
  api_nodes, output_nodes, known_labels. The live siblings
  (cloud_enabled_nodes, packs, downstream, find_paths) are untouched.
• standalone.py: install_comfy_cli, install_comfy (both orphaned; the
  StandalonePython class stays live via other paths).
• cmdline.py: validate_comfyui (plain function, no decorator, no callers) and
  the commented-out scan_dir # TODO: Move this to proper place block.
• update.py: get_version_from_pyproject.
• ui.py: prompt_autocomplete.
• utils.py: install_conda_package.
• env_checker.py: EnvChecker.is_isolated_env (get_isolated_env stays).
• cql/errors.py: CQLRuntimeError.as_details.

Judgment calls (consequential cleanups beyond the ticket's literal list)

To keep the tree lint-clean and free of code my own deletions orphaned:

• standalone.py run_comfy_cli — its only caller was the deleted install_comfy,
  so it became zero-reference; removed it too.
• Now-unused imports removed: update.py from importlib.metadata import metadata;
  utils.py subprocess, typer, and the rprint as print shim — each was used
  only by a function deleted here. ruff check on the changed files passes with these
  removed.

Testing

• ruff check + ruff format --check on all changed files: clean. (The 16
  pre-existing UP038 errors in the untouched workflow_to_api.py are unrelated to
  this PR.)
• Full suite: uv run --extra dev pytest -q → 2769 passed, 37 skipped (exit 0).

Note on the negative-claim/falsification check: this is a pure deletion of unused
code. No user-reachable capability is denied — the removed symbols had zero call sites,
so no product path invoked them.

[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: 2 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: 88076a91-179f-406b-9752-790182368ccf

📥 Commits

Reviewing files that changed from the base of the PR and between 98325c9 and 3327c5d.

📒 Files selected for processing (8)

• comfy_cli/cmdline.py
• comfy_cli/cql/engine.py
• comfy_cli/cql/errors.py
• comfy_cli/env_checker.py
• comfy_cli/standalone.py
• comfy_cli/ui.py
• comfy_cli/update.py
• comfy_cli/utils.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch matt/be-4354-dead-code-sweep

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch matt/be-4354-dead-code-sweep

---

_{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)

[bigcat88]

This PR currently conflicts with main — GitHub reports mergeable: CONFLICTING, so it needs a rebase before I can review it and I'm skipping it in the current review sweep.

Please rebase (or merge main in) and I'll pick it up on the next pass. main moved a fair bit in the last day, including #614 (ANSI sanitisation across the pretty-print call sites) and #628 (the duplicate server_died error-code fix that had main red), so a refresh may also clear unrelated CI noise on this branch.

[bigcat88]

Approving. A 15-symbol deletion across 8 modules is exactly where a missed reference hides — #598 is currently blocked for precisely that (it removed _LOADER_OPENER while a test file added later still named it), so I checked this one four independent ways rather than trusting a grep.

Nothing dangles

An AST sweep of every .py in the repo on this branch merged with current main, collecting definitions, Name/Attribute references, imports, and string constants matching each deleted name:

symbol                      defs-remaining   references-remaining
api_nodes                          0                0
as_details                         0                0
cloud_disabled_nodes               0                0
get_version_from_pyproject         0                0
install_comfy                      0                0
install_comfy_cli                  0                0
install_conda_package              0                0
is_isolated_env                    0                0
known_labels                       0                0
label_nodes                        0                0
output_nodes                       0                0
pack_nodes                         0                0
prompt_autocomplete                0                0
run_comfy_cli                      0                0
validate_comfyui                   0                0

Zero references and zero definitions for all fifteen — the string-constant column is what would have caught dynamic dispatch, and it's empty. There's also no getattr( anywhere in the eight touched modules, so nothing can reach them by name at runtime.

Non-Python files are clean too — no hits in *.md, *.toml, *.yml, *.json, *.cfg, *.txt.

Runtime smoke test

Every command whose module was touched still works, and all eight modules import:

comfy --help / env / standalone --help / update --help / validate --help / node --help / which
  -> all exit 0, zero tracebacks

comfy_cli.{cmdline, cql.engine, cql.errors, env_checker, standalone, ui, update, utils}
  -> all import OK

comfy standalone mattered most here, since install_comfy, install_comfy_cli, run_comfy_cli, install_conda_package and validate_comfyui all read like live installer helpers. They aren't.

The one deletion I wanted to check by hand

prompt_autocomplete is the only removal that lives on a path --help can't reach. It turns out to be a questionary single-select prompt helper, not shell-completion machinery — and real Typer completion still resolves fine on this branch:

_COMFY_COMPLETE=complete_fish ...  ->  rc=0, 41 completion entries

Public surface unchanged

cql/__init__.py's __all__ is ["CQLRuntimeError", "load_graph"] on both main and this branch, and none of the deleted Graph query methods (api_nodes, output_nodes, pack_nodes, label_nodes, known_labels, cloud_disabled_nodes) or as_details ever appeared there. So this is genuinely internal dead weight, not an API removal.

Full suite green on this branch merged with current main; ruff check + ruff format --diff clean under the CI-pinned 0.15.15.

Git history keeps all of it if the CQL query API is ever wanted back — that's the right trade for ~100 lines nothing calls.