@anchrd/intel-api 0.38.0 → 0.39.0

package/dist/mcp/mcp.js

@@ -218,7 +218,7 @@ export async function handleMcp(request, deps) {
         }, async (input) => text(await deps.boards.resolveAssignees(actor, input)));
         server.registerTool("board_task_create", {
             title: "Add a card to a board",
-            description: "File a new card on a board. Omit the status to put it in the first column. Name a parent task to make it a subtask — it lands on the same board, and moving an existing card under another one is `node_update` with a new parent. The card is a node like any other: its own address, its own permissions, its own history.",
+            description: "File a new card on a board. Omit the status to put it in the first column. Name a parent task to make it a subtask — it lands on the same board, and moving an existing card under another one is `node_update` with a new parent. The card is a node like any other: its own address, its own permissions, its own history — and its own body. This call answers with the BOARD rather than the new card, so to write that body, make the card with `node_create` under the board instead: it answers with the node itself, files it on the board just the same, and hands you the id `node_version_create` asks for.",
             inputSchema: BoardTaskCreateInput,
             annotations: {
                 title: "Add a card to a board",
@@ -539,7 +539,7 @@ export async function handleMcp(request, deps) {
     if (permits(deps.authorization, "nodes", "create")) {
         server.registerTool("node_create", {
             title: "Create node",
-            description: "Create a governed folder, document, attachment, or table node.",
+            description: "Create a governed node: a folder, a board, a document, a card, an attachment or a table. A card made under a board lands on that board, and the answer carries the new node's id — which is what `node_version_create` needs to give it a body.",
             inputSchema: CreateNodeInput,
             annotations: {
                 title: "Create node",
@@ -553,7 +553,7 @@ export async function handleMcp(request, deps) {
     if (permits(deps.authorization, "nodes", "write")) {
         server.registerTool("node_version_create", {
             title: "Create node version",
-            description: "Append an immutable content version using an optimistic base version.",
+            description: "Append an immutable content version using an optimistic base version. Documents and board cards both take one — writing a card here is how a ticket gets a body instead of only a title.",
             inputSchema: SaveNodeVersionInput,
             annotations: {
                 title: "Create node version",

package/dist/nodes/nodes.js

@@ -27,6 +27,22 @@ const nothingWithheld = { titles: [], hidden: 0 };
 function applicableVerbs(kind) {
     return kind === "folder" ? ["read", "write", "execute", "share"] : ["read", "write", "share"];
 }
+/**
+ * Which kinds hold an editor body — the text somebody types and `node_get` reads back.
+ *
+ * ⚠️ **A card is one of them, and that is the whole of D66 on the write side** (#785). A task is a
+ * node like every other: its text is a node version, in the same table, through the same route. The
+ * panel reaches this call through `POST /nodes/:id/versions` exactly as MCP does, so a list that
+ * omitted `task` closed BOTH surfaces at once — an agent could name a card and not describe it, and
+ * a reader typing into the card got "could not be saved" over a body the model says it should hold.
+ *
+ * ⚠️ **A set, not one more `||`.** The other four kinds each carry their content some other way —
+ * a folder and a board hold children, an attachment holds bytes, a table holds CSV segments — and
+ * naming the ones that DO take an editor version is what keeps the next kind from being waved
+ * through by a condition that only ever grew. The annotation ties it to the enum: a kind renamed in
+ * the contract stops this file from compiling instead of silently dropping out of the set.
+ */
+const EditorContentKinds = ["document", "task"];
 // ⚠️ The refusal has to be actionable without becoming a directory of the tree. Whoever holds
 // `share` on one folder must not learn the titles of flows they may not see, so the ones they may
 // see are named and the rest are only counted (ADR-0004 §3, and #17's review) — which is the whole
@@ -666,8 +682,8 @@ export function createNodes(deps) {
                 return document;
             }
             const node = await requireVisible(actor, input.nodeId);
-            if (node.kind !== "document") {
-                throw new IntelError(409, "document_content_required", "Only documents accept editor content versions");
+            if (!EditorContentKinds.includes(node.kind)) {
+                throw new IntelError(409, "document_content_required", "Only documents and cards accept editor content versions");
             }
             if (!(await deps.repository.can(actor, node.id, "write"))) {
                 throw new IntelError(403, "node_forbidden", "This node cannot be edited");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anchrd/intel-api",
-  "version": "0.38.0",
+  "version": "0.39.0",
   "type": "module",
   "license": "UNLICENSED",
   "repository": {
@@ -43,7 +43,7 @@
   },
   "dependencies": {
     "@anchrd/gate-sdk": "^0.26.0",
-    "@anchrd/intel-contract": "^0.30.0",
+    "@anchrd/intel-contract": "^0.31.0",
     "@cfworker/json-schema": "^4.1.1",
     "@modelcontextprotocol/sdk": "^1.30.0",
     "fflate": "^0.8.3",