22. AI suggestion review UI

Goal

A human explicitly reviews each of a Recording's AI-extracted suggestions and decides, one at a time, whether it becomes a real Action or Decision — nothing is written to either model except through this explicit approval.

Acceptance criteria

• Any project member (#6's membership_required — not facilitator-only, matching #13/#14's own permission level for creating actions/decisions directly) can view a Recording's pending AISuggestions (#21) and see "Add"/"Ignore" per item.
• If the Recording hasn't produced suggestions yet (still transcribing/processing) or failed (Recording.error_message set), the view shows that state clearly instead of an empty, unexplained list.
• For a decision-type suggestion, "Add" creates the real Decision (#14) from the suggestion's content and marks the suggestion accepted.
• For an action-type suggestion, "Add" first shows an editable confirmation step — pre-filled with the AI's guessed owner name and due date where parseable — requiring the human to confirm or pick a real project member as owner before the Action (#13) is created, since #13 requires owner to be a validated member and the AI's guess is free text that may not match anyone. Only after that confirmation is the Action row created and the suggestion marked accepted.
• "Ignore" marks a suggestion rejected without creating anything.
• Once a suggestion is accepted or rejected, it no longer appears among the pending ones shown by this view.
• Submitting "Add" or "Ignore" against a suggestion that's already been decided (e.g. a double-click, or a stale page) is a no-op or clear error — it never creates a second Action/Decision row for the same suggestion.
• Non-members get 403/404, matching #6.

Out of scope

• Reviewing blocker/update suggestions — deferred to #27 along with #21's scope restriction to action/decision.
• Bulk accept/reject-all — not requested by the plan, which explicitly frames this as "AI proposes, humans approve" one item at a time; no follow-up filed.

Constraints

• Depends on #13, #14, and #21 already existing.
• Nothing writes to Action/Decision except through this explicit accept step, per the plan's "AI proposes, humans approve" rule.

Start by reading the existing Action (#13), Decision (#14), and AISuggestion (#21) implementations, along with the Recording state and membership permission behavior described here. Trace how pending suggestions are displayed and how each decision is persisted; done means every acceptance criterion passes, including confirmation, authorization, and duplicate-submission handling.