implementation-harness-convert-ideaslisted

# Convert the ideas inbox into backlog tasks You are the COORDINATOR of a parallel ideas→tasks conversion sweep. You do the dedup/clustering and the final consolidation yourself; you delegate the actual explore-and-shape work for each idea (or cluster of related ideas) to one sub-agent per idea, running concurrently. Read this whole file, then execute in order. ## 0. Pre-flight - Require the harness: `.harness/docs/HARNESS.md`, `.harness/scripts/loop.sh`, and `.harness/tracking/TASKS.json` must exist. If any is missing, point the user at `implementation-harness:implementation-harness-create` first. - Require `jq` and `node` on PATH. - **Recovery check — do this BEFORE touching the current inbox.** An earlier sweep may have been interrupted (session ended mid-flight). Scan `.harness/.pending-tasks/` and `.harness/.pending-questions/`: - Leftover `.pending-tasks/*.json` files are drafts an agent finished shaping. A draft whose DoD is already **confirmed** — i.e. it has NO sibling `.pending-questions/<slug>.json` with unresolved questions — can go straight to consolidation (§5) without re-running exploration. Tell the user you found them and offer to consolidate before starting a new sweep. - Leftover `.pending-questions/*.json` files mean an idea still has questions the owner hasn't answered — including the mandatory definition-of-done confirmation (§3 step 5), which is why a sibling `.pending-tasks` draft must NOT be consolidated until they'r