chore(cli-registry): clean up dead code and stale claims left after #380

[opticon454]

What this does

Follow-up to #380. When merging it you flagged several items as "left as they are" / "worth knowing rather than fixing" — none correctness-blocking, but all real. This cleans each one up:

1. Dead code removed from install.sh: _cli_index/check_cli/get_cli_path were the generic lookup helpers behind the per-CLI check_<cli>/get_<cli>_path pairs feat(cli-registry): drive install.sh and the Docker agent image from the CLI catalogue #380 removed; once the catalogue-driven menu and hints stopped calling them, nothing did.
2. CLI_KIND/CLI_NPM dropped from the generated bash block. Nothing in install.sh read either array — the .mjs/docker-hosts.ts producers already read the JSON catalogue's kind/npmPackage fields directly, so only the bash copies were dead weight.
3. detect_all_clis now skips a disabled entry's probe entirely instead of running it and filtering the result downstream afterward. No stock entry ships disabled today, so this closes a latent inefficiency before it is a latent bug rather than reacting to an observed one.
4. The DeepSeek/launcher-only install hint now explains itself. Its docs page documents npm install -g @deepseek-ai/dsh, which installs the launcher only and can't drive a pane on its own — the exact trap the menu already avoids by withholding the command. The hint now adds one line saying so, driven by a new generated CLI_LAUNCHER_ONLY array (from discovery.launcherProfile), not an id check — any future launcher-only entry gets the same caveat for free.
5. Corrected the non-interactive-default comment. It claimed the default is "always Claude Code (order 0)"; on a wget-only host Claude's curl one-liner is filtered out of the offered list first, so the default becomes whichever npm-based entry sorts earliest instead (Codex today). Behaviour is unchanged — it was already printed, never silent — only the comment overclaimed.

Tests

test/install-sh-invariants.test.ts gained:

• a positive guard for the trimmed array list (now includes CLI_LAUNCHER_ONLY)
• a negative guard that CLI_KIND/CLI_NPM cannot come back
• a negative guard that the three dead helpers cannot come back
• two real-bash tests (driven the same way the existing skip-menu tests are) proving a disabled entry is genuinely never probed rather than merely filtered after the fact

Verification: tsc --noEmit clean, generate-cli-catalog --check clean (JSON output byte-identical — kind/npmPackage still flow through the JSON side, only the redundant bash arrays are gone), and the full CLI-catalogue test set (install-sh-invariants, install-sh-detection-parity, cli-catalog-sync, docker-agent-image-coverage, agent-image-build-args-parity, cli-registry-no-id-branching) passes clean on a Linux-shaped checkout. Three pre-existing install.sh menu tests fail locally on this Windows dev box (bash/MSYS trips the script's own "Windows is not supported directly" guard before the sourcing guard is reached) — reproduced identically against master before this change, so it's an existing Windows-only test-environment gap, not a regression.

🤖 Generated with Claude Code

https://claude.ai/code/session_011WzDjJnbK7zug8iQWnCc9z