Add written answers to decision cards

[MaggieAppleton]

People can now create a question from Decisions → New decision, then write an answer and press the existing Save button. This supports decisions whose answer is prose rather than a choice from predefined options.

The card contains the question, optional context, and one shared answer field. Saving records the answer and who saved it; Reopen and Discard preserve history. Existing choice cards keep their behavior.

Written answers use the existing shared drafts and authoritative decision records. Creation is durable and idempotent, and saving retains the existing revision claim and persistence-before-publication ordering. The Planner can create these cards with open_decision or ask; it cannot save an answer for someone. Written decisions reject options throughout the document and record boundaries.

In the app

Start in the Decisions panel, create a question, then write and save its answer. These are screenshots of the running application using sample content.

Validation

• 410 focused unit, domain, and render tests; workspace type checks, CI/design checks, and production build.
• 13 browser scenarios pass without retries: shared editing, reload, saving, reopening, discarding, read-only access, and phone controls, plus the existing choice-card phone flows.
• PostgreSQL checks reconstruct the draft, saved answer, attribution, and reopened history across five fresh processes.
• Independent review found no actionable issues. Planner tool contracts were tested; live-model behavior was not evaluated.

All 24 GitHub CI jobs pass at d8a5e4aaccd0a9df50f5e5611a920f43371f7ff8 (run). Decision-card cases pass on the first attempt. Two other browser cases require retries: investigation evidence after disconnect and Back navigation during research-child opening.