retro-metalisted

# ax:retro-meta - deep retro of retros The companion to `ax:retro`. Where `ax:retro` walks the heuristic-derived proposals one by one, `retro-meta` asks: *what improvements does the existing pipeline NOT yet see?* The external agent (this one, Claude Code or Codex with high thinking) drives the reasoning. The CLI just produces structured evidence and takes user-approved plans back. ## When to fire Explicit triggers only: - "let's do a deep retro" / "retro of retros" - "investigate my ax setup" / "what should I fix in my setup" - "review proposals the heuristic missed" - `/ax:retro-meta` slash command - After `ax:retro` finishes if the user wants broader exploration Do NOT auto-trigger on generic "look at recent work". ## Prerequisites - `ax` (axctl) is on PATH. If `ax doctor` fails, stop and point the user at `docs/development.md#setup` (DuckDB dylib setup - no daemon required). - At least 3 retros in the last 30 days. Below that, evidence is too thin for a meta pass - recommend `ax:retro` first. ## Workflow ### Step 1 - Snapshot ```bash ax retro meta --json --since=30 > /tmp/ax-meta.json ``` Read `/tmp/ax-meta.json`. The keys you care about: - `experiment_status[]` - **read this FIRST** (see Step 2). Each entry: `experiment_id`, `proposal_dedupe_sig`, `proposal_title`, `proposal_form`, `artifact_path`, `days_since_accepted`, `opportunities_count`, `addressed_count`, `address_ratio`, `latest_checkpoint{kind,suggested,observed_at}`, `locked_verdict`. P