Changelog

API sessions run the full board engine

• Sessions started over the REST API and MCP now run the same engine as the web app: an express intake turns your question into a decision brief, the brief staffs the board, the board researches and debates, and the run terminates in a decision memo (verdict, confidence, conditions, dissent) or a shaped artifact. New response fields on session reads: session_type, v4_phase, decision_brief, memo, board_artifact.
• The Consult over the API. Create a 1-on-1 session with a named expert via session_type: "consult" + synth_id; drive turns with the MCP tool synthboard.consult.message — each turn returns the expert's reply and any composed document, billed per turn.
• Reconvene. New MCP tool synthboard.session.reconvene — reconvene a completed board as Round N+1 when something changed. Opens from the delivered verdict plus whats_changed, re-briefs, and runs. session.continue on a current board returns invalid_session_state pointing here.
• 13 new REST endpoints: session archive, fork, metadata PATCH, mid-session update, live-summary, cross-round, assistant, bookmarks, decisions, action execute + undo, share revoke, and share password verification — plus webhook subscription CRUD and delivery logs. Spec bumped to 2.0.0 at /api/v1/openapi.json.
• Webhook events now cover the full lifecycle: session.complete, session.failed, session.cancelled, session.continued, outcomes.ready — fired natively by the engine for API-started sessions.
• Resilience. Model calls now run on provider fallback chains with circuit breakers — a session completes even when an upstream model provider degrades mid-run. Failed runs auto-refund undelivered work.
• MCP surface: new resource synthboard://session/{id}/memo (the terminal deliverable alone), a /synthboard-consult prompt, and account/recent resources now report the engine and available session types.