Role: product/premise critic.

Objective: Challenge whether the three inspiration sources deserve new Harness Kit backlog tickets, or whether they should be folded into existing tickets or rejected.

Scope:
- Read active `backlog.d/*.md` and the root `AGENTS.md`.
- Consider Harness Kit doctrine: thin harness, cross-harness first, no semantic workflow engine, executable evidence, concise AGENTS, clean closeout.
- Do not edit files.
- Do not browse; reason from repo and the summarized source themes below.

Source themes:
- Agent-legible source of truth: code or CLI/MCP/skill path to external source, not hidden CMS/UI-only state.
- Human comprehension loop: agent teaches the operator incrementally, tracks what the human should understand, asks restatement/quiz questions, and does not end until understanding is demonstrated.
- Agentic engineering article: plan-first, raw transcripts, voice, many parallel sessions, agent-accessible notes, skills for repeated workflows, and remote/control-plane automation.

Output shape, max 700 words:
- Which candidate ideas are likely duplicates or too broad.
- Which 2-4 ideas are backlog-worthy for Harness Kit now.
- The failure mode if Harness Kit implements the wrong version.
- A recommended narrow first slice.

What not to touch:
- No code edits.
- No generated backlog files.
- No raw private transcript quoting.
