C3 · Idea capture (text-first) → spec draft

[atomikpanda]

Problem. Capture intent away from the desk — this is where mobile is most natural. Text first; voice later (D1).

Direction.

• Capture screen: free text → POST to mship spec draft --from-text (A2); show the resulting draft.
• Entry points: brainstorm feature / refine existing spec / create directive.

Acceptance.

• Typing an idea creates a Spec draft via the API and lands it in the inbox as needs_review.

[atomikpanda]

Partial progress, not yet closeable. Ground-control PR #5 (atomikpanda/ground-control#5) shipped a minimal Capture tab: title + affected-repos form → POST /specs → lands in the Drafting group.

The acceptance criterion here is different: free-text idea → mship spec draft --from-text (A2) → lands in the inbox as needs_review, with the three entry points (brainstorm feature / refine existing spec / create directive). That --from-text draft flow and the needs_review landing state are still unbuilt. (The capture-as-conversation thread→spec flow in PR #10 is a related but distinct path.)

Remaining: wire the Capture free-text field to the draft API and surface the resulting draft as needs_review.