cqs-planlisted

# Plan Generate an implementation plan by combining `cqs scout` output with a task-type template. ## Process 1. **Classify the task** into one of the templates below based on the description. 2. **Run scout**: `cqs scout "<task description>" --json 2>/dev/null` (no `-q` flag on subcommands) 3. **Run targeted lookups** from the template's checklist — scout alone misses structural touchpoints (clap structs, dispatch arms, skill files). 4. **Produce a plan** listing every file to change, what to change, and why. Be specific about struct fields, function signatures, and match arms. ## Arguments - `$ARGUMENTS` — task description (required) ## Templates ### Add/Replace a CLI Flag **When:** Adding a new flag, renaming a flag, changing a flag's type (bool → enum). **Checklist:** 1. `src/cli/definitions.rs` — `Commands` enum variant. Add/modify `#[arg]` field (often via a shared `*Args` struct in `src/cli/args.rs`). If enum-typed, define with `clap::ValueEnum`. 2. `src/cli/dispatch.rs` — `run_with()`/`run_with_dispatch()` match arm. Update destructuring and `cmd_<name>()` call. 3. `src/cli/commands/<group>/<name>.rs` (groups: search/, graph/, review/, index/, io/, infra/, eval/, train/) — flag flows into the `*_core` fn's typed `*Args`; update branching there, not just the CLI adapter. 4. **Daemon surface**: if the flag affects core behavior, the daemon `dispatch_*` handler in `src/cli/batch/handlers/` must forward it too — CLI and daemon are parallel surfaces, wire both in t