@ratifia/mcp 0.10.1 → 0.11.0

package/README.md

@@ -205,7 +205,7 @@ Three properties worth knowing, because they shape how you should use it:
 
 1. The agent calls `request_decision` before a consequential/irreversible step (deploy, delete, spend, send externally), an ambiguous call it shouldn't guess, or to get a human to pick/refine something.
 2. Ratifia notifies the human (even away from keyboard) per the org's routing.
-3. The agent `await_decision`s (or polls `check_decision`) — read `verdict`/`note`, plus `response_value` (select/text) or `output` (a refined draft).
+3. The agent `await_decision`s (or polls `check_decision`) — read `verdict`/`note`, plus `response_value` (select/text) or `output` (a refined draft). `policy_version` / `policy_version_id` say which version of the policy the decision ran under (null when no policy applied).
 4. The agent proceeds only on `approved`; on `rejected`/`expired` it adapts.
 
 Learn more at [ratifia.com](https://ratifia.com).

package/dist/index.js

@@ -188,6 +188,10 @@ const formatDecision = (d) => ({
     ...(d.output ? { output: d.output, refined: Boolean(d.refinedOutput) } : {}),
     decided_by: d.decidedBy,
     decided_at: d.decidedAt,
+    // FN-316: which version of the policy governed this decision, so an agent can
+    // cite it ("approved under refunds v3"). Stays put when the policy is edited.
+    policy_version: d.policyVersion ?? null,
+    policy_version_id: d.policyVersionId ?? null,
 });
 const asToolResult = (payload) => ({
     content: [{ type: 'text', text: JSON.stringify(payload, null, 2) }],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ratifia/mcp",
-  "version": "0.10.1",
+  "version": "0.11.0",
   "type": "module",
   "description": "Ratifia MCP server — let an AI agent request a human decision/approval (HITL) mid-task and resume once it's answered. The agent becomes a Ratifia 'engine'.",
   "keywords": [