implementation-harness-capture-idealisted

# Capture an idea (zero-ceremony, rich) Append ONE JSON object, on its own line, to `.harness/tracking/IDEAS.jsonl` (a JSONL file — one idea per line) — no interview, no decomposition, no `TASKS.json` edit, no clarifying questions. This must never derail the task at hand: it's a quick side-append, no back-and-forth. But "zero-ceremony" means **no scoping/decisions**, NOT "terse" — capture the idea RICHLY (step 4): the context you have in front of you right now is cheap to record, and the later `implementation-harness-convert-ideas` sweep runs COLD and would otherwise have to re-excavate all of it (or bug the user for it). ## Schema Each line is one JSON object: ```json {"id": 3, "title": "One-line summary shown in the dashboard's collapsed row", "description": "The full rich capture — as much detail and context as you have.", "capturedAt": "2026-07-07T14:32:00Z"} ``` - `id` — integer. See step 3. - `title` — a short, one-line summary (a few words to ~10). This is what the dashboard shows collapsed, so make it identify the idea at a glance; it is NOT the full capture. - `description` — the rich body (step 4). No length limit. - `capturedAt` — ISO-8601 UTC timestamp of when you're capturing it (`date -u +%Y-%m-%dT%H:%M:%SZ`). ## Steps 1. **Require the harness.** `.harness/docs/HARNESS.md` must exist. If missing, stop and tell the user to run `implementation-harness:implementation-harness-create` first. 2. **Ensure the inbox exists.** If `.harness/tracking/IDEAS.json