Idea-intake bridge schema

[JSONbored]

Problem: No defined interface exists for turning a freeform human idea into something the loop mechanics can execute against. Without this, a person still has to manually translate their own intent into a well-formed, claimable issue — the whole point of "renting a loop" is that they shouldn't have to.

Area: Product spec

Proposal: Define a schema for an "idea" submission and the rules for translating it into a structured, claimable task-graph: constituent issues, acceptance criteria per issue, and a scoring rubric the execution loop can evaluate its own output against.

Deliverables:

• A written spec: input schema, translation rules, at least two fully worked examples (one simple idea, one multi-step idea) traced end-to-end through the schema.

Acceptance criteria:

• Spec reviewed and approved before Idea-intake API/MCP tool #4798 (its implementation) begins.
• Both worked examples produce a task-graph that a human reviewer agrees is faithful to the original idea.

Resources:

• The miner package's existing discovery documentation, for the shape of a "claimable" unit of work today.

Boundaries:

• Spec only — no implementation in this issue.

---

Part of #4778.

[linear-code]

JSO-3451