fix(wavemachine): call installed binaries by PATH-resolvable names

[bakeb7j0]

Summary

/wavemachine and /nextwave SKILL.md bodies were calling supporting tooling via paths that only resolve inside claudecode-workflow's source tree (python3 -m wave_status, ./scripts/generate-status-panel, scripts/mcp-log). On any other project the calls failed, breaking the statusline indicator, status panel, and observability log — or in the better case, halting an agent that correctly diagnosed the missing tooling. This PR rewrites the call sites to use the PATH-resolvable installed-binary names (wave-status, generate-status-panel, mcp-log), adds a pre-flight existence check that refuses early with a named-CLI error, and locks the invariant in with two regression tests.

Regression-introducing commit: f9d3a12 (PR #383, 2026-04-20). The intent ("route state writes through wave-status CLI") was right; the executed change shipped the wrong invocation form.

Changes

• skills/wavemachine/SKILL.md:
  • All python3 -m wave_status <subcmd> → wave-status <subcmd> (4 sites)
  • All ./scripts/generate-status-panel and scripts/generate-status-panel → generate-status-panel (~9 sites)
  • All scripts/mcp-log → mcp-log (5 sites)
  • Orphan wave_status wavemachine-stop (no python3 -m) → wave-status wavemachine-stop (3 sites — half-finished edit from fix(wavemachine): route state writes through wave-status CLI #383)
  • NEW pre-flight check (item feat: complete repo scaffolding — CI, settings, MCP, sync, dogfooding, releases, uninstall #1, runs before any MCP calls): command -v wave-status generate-status-panel mcp-log; refuses with a message that names every missing CLI individually and points the operator at ./install for remediation
• skills/nextwave/SKILL.md:
  • All scripts/mcp-log → mcp-log (4 sites)
• tests/regression/test_skill_uses_installed_binaries.sh (new): greps both skill bodies for forbidden patterns (backtick-inline AND fenced-block forms), fails if any present
• tests/regression/test_wavemachine_preflight_tools_check.sh (new): verifies pre-flight check exists, names all three CLIs, points at the installer, doesn't suggest PYTHONPATH/pip-install workarounds

Out of scope (called out in test header): scripts/wavebus/{wave-init,flight-finalize,wave-cleanup} references in nextwave have the same shape of bug but a different install layout (subdirectory not on PATH). Separate issue to follow.

Linked Issues

Closes #569

Test Plan

• ./scripts/ci/validate.sh — 124/124 pass (including 2 new regression tests auto-picked up by the suite glob)
• trivy fs --scanners vuln --severity HIGH,CRITICAL — 0 findings
• Code review by feature-dev:code-reviewer — 3 important findings, all fixed in-place: (1) test pattern extended to catch fenced-block form; (2) pre-flight ordering note added; (3) explicit out-of-scope wavebus comment in test header
• Manually confirmed ~/.local/bin/{wave-status,generate-status-panel,mcp-log} are all on PATH and that wave-status --help lists every subcommand the skill calls
• Post-merge smoke: invoke /wavemachine from a non-cc-workflow project (e.g. mcp-server-discord checkout) with a wave plan, confirm pre-flight passes and the loop runs cleanly. Will do this once fix(wavemachine): skill body calls non-portable paths instead of installed binaries #569 is on main.

🤖 Generated with Claude Code