statuslisted

Report the validation pipeline status. Never rely on a session-start summary — read the files now. ## Steps 1. Find ideas: `ideas/*/state.json` in the current workspace. If `$ARGUMENTS` names a slug, report only that idea; otherwise report all (and if none exist, say so and point to `new-idea`). For each idea, also read the `cycles` index and every fragment `cycles/<id>/state.json` — report per cycle (a locked C1 plus an active C2 are two lines, not one). 2. **Pre-LOCK reconcile (v1.13.0, first mechanical step, before reading anything for the report below)**: for each cycle that has **not** reached LOCK (the mirror-image scope of the `reconcile` skill, which is post-LOCK only), run `node "${CLAUDE_SKILL_DIR}/../../scripts/reconcile-pre-lock.js" <idea-or-cycle-dir> --json`. Surface any deterministic divergences (each with a proposed patch) and non-deterministic open questions; apply a proposed patch only on the user's explicit confirmation, via `state-write.js` — never automatically. A cycle already past LOCK is skipped here (that is `reconcile`'s scope). 3. For each idea, read `state.json` and report, in the user's language: - **Post-launch validation** (`post_launch_validation`, only when the key is present — absent means V1 has never been deferred): report `status`, `reopen_on`, and (once set) `mvp_release_declared_at`. **When `status: "reactivated"`, flag it first and loudly** — before Position and everything else — real V1 evidence collection is now due (a controlled