Audit all CLI commands and flag which ones lack TUI or Web coverage.
Produce a coverage matrix of every CLI subcommand vs. TUI and Web UI.
Read conductor-cli/src/main.rs and enumerate every subcommand (top-level and nested). Group them by command group (repo, worktree, tickets, agent, workflow, merge-queue, etc.).
Search conductor-tui/src/ for references to each command's underlying functionality:
Push, CreatePr, LaunchAgent)Mark ✅ if the TUI exposes the functionality, ❌ if not.
Search conductor-web/src/ for HTTP route handlers corresponding to each command:
conductor-web/src/routes/ for relevant route filesMark ✅ if a web endpoint exists, ❌ if not.
Print a table grouped by command group:
## <Group Name>
| Command | TUI | Web |
|---|---|---|
| `group sub` | ✅/❌ | ✅/❌ |
After all groups, print a summary section:
## CLI-Only Commands (neither TUI nor Web)
- `command sub` — one-line description of what it does
And a quick stats line:
X / Y commands covered by both TUI and Web.
For any CLI-only commands, note whether they appear to be:
Suggest which CLI-only commands are candidates for removal vs. intentional design.