docs(vault): Document Sign-Off, the MCP server and the release gap are delivered

vault/features/Document Sign-Off MVP.md

@@ -1,21 +1,24 @@
 ---
 type: feature
 area: Document Sign-Off
-state: planned
+state: delivered
 owner: Quirin & Andre
 milestone: 2026-08
-updated: 2026-07-27
+prs: [356, 373, 375, 377, 378, 380, 381, 382, 384, 386, 387, 388, 397, 398]
+updated: 2026-10-10
 ---
 
 # Document Sign-Off MVP
 
-The four primitives: document creation, hash-bound versioning, signer review against
-the wallet's inherited threshold, and an exportable audit proof as JSON and PDF.
+The four primitives, shipped: document creation, hash-bound versioning, signer
+review against the wallet's inherited threshold, and an exportable audit proof as
+JSON and PDF, checkable by anyone at the public `/verify` route without an account.
 Approval belongs to a version, never a mutable container — a new version starts a
-fresh round at zero approvals. Specified as PRD-001, which is still in Draft, so
-finalizing it is the first sub-task.
+fresh round at zero approvals. All six PRD-001 user stories run end to end, and the
+whole chain is covered against a real database with real CIP-8 keys.
 
-Ready means a pilot team runs all six user stories end to end without developer help.
+Two things remain before PRD-001's own bar is met: Playwright browser specs for the
+sign-off flows, and a pilot team running the six stories without developer help.
 
 ## Related
 

vault/features/Multisig MCP Server.md

@@ -1,17 +1,21 @@
 ---
 type: feature
 area: Bot & Agent Platform
-state: planned
-owner: Andre
-milestone: 2026-11
-updated: 2026-07-27
+state: delivered
+owner: Quirin
+milestone: 2026-08
+prs: [357, 358, 360, 361, 365, 367, 370, 376]
+updated: 2026-10-10
 ---
 
 # Multisig MCP Server
 
-Expose the existing bot API as an MCP server, so an AI agent can act as a wallet
-observer or ballot drafter directly. A short step from the delivered agent surface,
-and a genuine differentiator.
+A stateless MCP endpoint behind an OAuth 2.1 authorization server, so any AI agent
+can act as a wallet observer or ballot drafter directly. Clients register
+dynamically and authorize with PKCE; the user grants scopes one by one, sees and
+revokes connections, and reviews per-wallet activity. Fifteen published tools cover
+wallets, governance, ballots and documents. Read-only by design: nothing signs or
+broadcasts. Pulled forward from November to August.
 
 ## Related
 

vault/features/Production Release Gap.md

@@ -1,23 +1,22 @@
 ---
 type: feature
 area: Release & Production Health
-state: blocked
+state: delivered
 owner: Quirin
 milestone: 2026-08
-prs: [319, 321]
-updated: 2026-07-27
+prs: [319, 321, 369, 393]
+updated: 2026-10-10
 ---
 
 # Production Release Gap
 
-Production has applied no migration since 2026-05-10, and `preprod` sits 75 commits
-ahead of `main` — so June and July are built but unreleased. The migration workflow
-only fires on pushes to `main` touching `prisma/migrations/**`, so fixing it never
-re-triggered the run that failed on 17 June. Governance tallies error, the
-notification center has no tables, and address-less bot registration cannot work.
+Closed. The June and July backlog reached production with the 14 August release
+(#369), and everything through mid-September with the 5 October release (#393); the
+migration workflow reported success on both.
 
-Unblocking is one release plus one manual workflow dispatch, and it is the first
-task of August.
+The underlying hazard has not gone away: the migration workflow only fires on pushes
+to `main` touching `prisma/migrations/**` and never retries itself, so a failed run
+still has to be noticed and dispatched by hand. Check its result on every release.
 
 ## Related