@anchrd/intel-api 0.14.0 → 0.16.0

package/dist/mcp/mcp.types.d.ts

@@ -1,6 +1,4 @@
 import type { Authorized } from "@anchrd/gate-sdk";
-import type { AgentCostsService } from "../agent-costs/agent-costs.types.js";
-import type { AgentRuntimeService } from "../agent-runtime/agent-runtime.types.js";
 import type { BundleService } from "../bundle/bundle.types.js";
 import type { FlowService } from "../flows/flows.types.js";
 import type { NodeService } from "../nodes/nodes.types.js";
@@ -8,15 +6,12 @@ import type { ToolService } from "../tools/tools.types.js";
 export interface McpDeps {
     authorization: Authorized;
     /**
-     * The bearer this call was authorized with, forwarded to the agent runtime so a run is driven by
-     * the caller and not by Intel. Nothing else reads it, and nothing writes it anywhere.
+     * The bearer this call was authorized with, passed on where Intel has to speak to Gate as the
+     * person asking rather than as itself. Nothing else reads it, and nothing writes it anywhere.
      */
     bearer: string;
     nodes: NodeService;
     flows: FlowService;
     tools: ToolService;
     bundle: BundleService;
-    agents: AgentRuntimeService;
-    /** What an agent has cost, out of the AI Gateway log — the MCP half of the profile's figures (#251). */
-    agentCosts: AgentCostsService;
 }

package/dist/nodes/document-links/document-links.d.ts

@@ -9,14 +9,12 @@
  * newer editor wrote; a strict parse would turn "I do not recognise this block" into "this document
  * cannot be saved". What it does not recognise contributes no link, which is the safe half.
  *
- * ⚠️ A board reaches the same link graph, through the same `text` origin (#285). Its links are not
- * inline elements but the `references` of its tasks, which is a difference in where they are
- * written and not in what they are: somebody put a node id into a body, and the graph has to see it
- * from the other side. Reading it here rather than in the board service is what keeps ONE answer to
- * "what does this body point at" — the writer (`reconcileTextLinks`) asks this function and does
- * not care which kind it is holding.
+ * ⚠️ ONE answer to "what does this body point at", whatever kind holds the body: the writer
+ * (`reconcileTextLinks`) asks this function and does not care. Until #390 a board answered here
+ * too, through the `references` of its tasks — a difference in where the ids were written and not
+ * in what they were.
  *
- * Content that is neither has no links at all: an attachment, a CSV table or plain markdown carries
- * nothing to read.
+ * Content that is not a BlockNote document has no links at all: an attachment, a CSV table or plain
+ * markdown carries nothing to read.
  */
 export declare function documentLinkTargets(mediaType: string, content: string): string[];

package/dist/nodes/document-links/document-links.js

@@ -1,5 +1,4 @@
-import { BlockNoteDocument, BlockNoteMediaType, BoardDocument, BoardMediaType, DocumentLinkInlineType, } from "@anchrd/intel-contract";
-import { upgradeStoredBoard } from "../board/board.js";
+import { BlockNoteDocument, BlockNoteMediaType, DocumentLinkInlineType, } from "@anchrd/intel-contract/node";
 function isRecord(value) {
     return typeof value === "object" && value !== null;
 }
@@ -31,18 +30,16 @@ function collect(value, found) {
  * newer editor wrote; a strict parse would turn "I do not recognise this block" into "this document
  * cannot be saved". What it does not recognise contributes no link, which is the safe half.
  *
- * ⚠️ A board reaches the same link graph, through the same `text` origin (#285). Its links are not
- * inline elements but the `references` of its tasks, which is a difference in where they are
- * written and not in what they are: somebody put a node id into a body, and the graph has to see it
- * from the other side. Reading it here rather than in the board service is what keeps ONE answer to
- * "what does this body point at" — the writer (`reconcileTextLinks`) asks this function and does
- * not care which kind it is holding.
+ * ⚠️ ONE answer to "what does this body point at", whatever kind holds the body: the writer
+ * (`reconcileTextLinks`) asks this function and does not care. Until #390 a board answered here
+ * too, through the `references` of its tasks — a difference in where the ids were written and not
+ * in what they were.
  *
- * Content that is neither has no links at all: an attachment, a CSV table or plain markdown carries
- * nothing to read.
+ * Content that is not a BlockNote document has no links at all: an attachment, a CSV table or plain
+ * markdown carries nothing to read.
  */
 export function documentLinkTargets(mediaType, content) {
-    if (mediaType !== BlockNoteMediaType && mediaType !== BoardMediaType)
+    if (mediaType !== BlockNoteMediaType)
         return [];
     let parsed;
     try {
@@ -52,26 +49,6 @@ export function documentLinkTargets(mediaType, content) {
         return [];
     }
     const found = new Set();
-    if (mediaType === BoardMediaType) {
-        /**
-         * ⚠️ Upgraded first, like `parseStoredBoard` and `indexing.ts` — this is the FOURTH place a
-         * board body is parsed, and the only one that cannot complain (anchrd/intel#321).
-         *
-         * A board it fails to parse simply has no links, which reads exactly like a board that points
-         * at nothing — and the reconciliation this feeds removes the links a body no longer names, so
-         * an unparsed old board would quietly leave the link graph. Every caller hands it a body written
-         * moments earlier today, so it has never met one; the upgrade is what keeps that from being the
-         * only reason.
-         */
-        const board = BoardDocument.safeParse(upgradeStoredBoard(parsed));
-        if (!board.success)
-            return [];
-        for (const task of board.data.tasks) {
-            for (const reference of task.references)
-                found.add(reference);
-        }
-        return [...found];
-    }
     const document = BlockNoteDocument.safeParse(parsed);
     if (!document.success)
         return [];