@anchrd/intel-api 0.14.0 → 0.15.0

package/dist/mcp/mcp.js

@@ -1,5 +1,5 @@
-import { AddBoardTaskInput, AppendTableRowsInput, ArchiveFlowInput, ArchiveNodeInput, CancelFlowRunInput, CompleteFlowRunStepInput, ConfigureBoardInput, CreateAgentInput, CreateFlowInput, CreateNodeInput, DefineTableInput, DeleteBoardTaskInput, DeleteTableRowsInput, ExecuteToolInput, GetAgentInput, GetBoardInput, GetFlowInput, GetFlowRunInput, GetFlowVersionInput, GetNodeInput, GetNodeVersionInput, GetTableInput, IntelId, ListAgentsInput, ListFlowRunsInput, ListFlowsInput, ListGrantsInput, ListNodesInput, MoveBoardTaskInput, NodeGraphInput, PauseAgentInput, PreviewFlowPublishInput, PublishFlowInput, RedefineTableInput, RelationGraphInput, RepairBoardTaskIdsInput, ResolveNodeLinksInput, RevokeGrantInput, RotateAgentKeyInput, RunAgentNowInput, SaveAgentDefinitionInput, SaveAttachmentInput, SaveFlowVersionInput, SaveNodeVersionInput, SearchInput, ShareInput, StartFlowRunInput, TestToolInput, UnpublishFlowInput, UpdateBoardTaskInput, UpdateFlowInput, UpdateNodeInput, UpdateTableRowsInput, } from "@anchrd/intel-contract";
-import { McpServer, ResourceTemplate, } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { AppendTableRowsInput, ArchiveFlowInput, ArchiveNodeInput, CancelFlowRunInput, CompleteFlowRunStepInput, CreateFlowInput, CreateNodeInput, DefineTableInput, DeleteTableRowsInput, ExecuteToolInput, GetFlowInput, GetFlowRunInput, GetFlowVersionInput, GetNodeInput, GetNodeVersionInput, GetTableInput, IntelId, ListFlowRunsInput, ListFlowsInput, ListGrantsInput, ListNodesInput, NodeGraphInput, PreviewFlowPublishInput, PublishFlowInput, RedefineTableInput, RelationGraphInput, ResolveNodeLinksInput, RevokeGrantInput, SaveAttachmentInput, SaveFlowVersionInput, SaveNodeVersionInput, SearchInput, ShareInput, StartFlowRunInput, TestToolInput, UnpublishFlowInput, UpdateFlowInput, UpdateNodeInput, UpdateTableRowsInput, } from "@anchrd/intel-contract";
+import { McpServer, ResourceTemplate } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { WebStandardStreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/webStandardStreamableHttp.js";
 import { z } from "zod";
 import { permits } from "../shared/gate-authorization/gate-authorization.js";
@@ -61,12 +61,6 @@ export async function handleMcp(request, deps) {
         canReadFlows: permits(deps.authorization, "flows", "read"),
         canCreateFlows: permits(deps.authorization, "flows", "create"),
     };
-    const agentActor = {
-        id: deps.authorization.identity.id,
-        email: deps.authorization.identity.email,
-        isAdmin: deps.authorization.can("intel", "admin"),
-        canRun: permits(deps.authorization, "agents", "run"),
-    };
     const server = new McpServer({ name: "intel", version: "0.1.0" });
     const EmptyInput = z.strictObject({});
     // `null` is the root: the whole tree as this caller may read it. The field is required rather
@@ -213,33 +207,6 @@ export async function handleMcp(request, deps) {
                 openWorldHint: false,
             },
         }, async (input) => text(await deps.nodes.search(actor, input)));
-        // ⚠️ Plain `registerTool` and no alias: these tools are new with #139 and never had a
-        // `knowledge_` name, so inventing one would create a deprecated name that was never used —
-        // and #149, which removes the aliases, would then have one more thing to remove.
-        server.registerTool("agent_list", {
-            title: "List agents",
-            description: "List the authorized agents, over the whole tree or under one folder. Omit parentId for every agent, pass null for the root level.",
-            inputSchema: ListAgentsInput,
-            annotations: {
-                title: "List agents",
-                readOnlyHint: true,
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.listAgents(actor, input)));
-        server.registerTool("agent_get", {
-            title: "Get agent",
-            description: "Read one authorized agent with its current definition: the nodes it references and their role, its schedules, and its model.",
-            inputSchema: GetAgentInput,
-            annotations: {
-                title: "Get agent",
-                readOnlyHint: true,
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.getAgent(actor, input)));
         server.registerTool("node_table_get", {
             title: "Get node table",
             description: "Read one authorized table as column names and rows.",
@@ -252,21 +219,6 @@ export async function handleMcp(request, deps) {
                 openWorldHint: false,
             },
         }, async (input) => text(await deps.nodes.getTable(actor, input.nodeId)));
-        // A board answers whole: the statuses and every task, in one read. There is no per-task read
-        // beside it, because a card is small and the interesting question is almost always about
-        // several of them at once — what is in review, what waits for what (#285).
-        server.registerTool("board_get", {
-            title: "Get board",
-            description: "Read one authorized board: its status list and every task with its full field set. A board that has never been written answers with the default statuses and no tasks.",
-            inputSchema: GetBoardInput,
-            annotations: {
-                title: "Get board",
-                readOnlyHint: true,
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.getBoard(actor, input)));
         server.registerTool("node_links_list", {
             title: "List node links",
             description: "List authorized outgoing links and backlinks for one node.",
@@ -356,65 +308,8 @@ export async function handleMcp(request, deps) {
                 openWorldHint: false,
             },
         }, async (input) => text(await deps.nodes.create(actor, input)));
-        /**
-         * ⚠️ There is no longer ANY tool result in Intel that contains a secret, and that is the whole
-         * of D29 seen from here. Until #207 this one tool answered with the Application key in plain
-         * text — a deliberate exception, because the result WAS the credential and a redacted answer
-         * would have meant "an agent you can create but never run". The exception is gone rather than
-         * weakened: the key now travels from Gate into the agent runtime over Intel's service binding
-         * inside this call, so there is nothing left to hand to a model. `agent_create`, `agent_get`,
-         * `agent_list` and every node read answer with `applicationId` alone, which names the principal
-         * without authenticating it.
-         */
-        server.registerTool("agent_create", {
-            title: "Create agent",
-            description: "Create an agent node with its first definition, and the Gate application it runs as. The definition names nodes and their role, schedules and a model — never accounts, secrets or channels. The agent's application key is handed to the agent runtime internally and never appears in this result; the agent can run straight away. A repeated idempotency key returns the existing agent and mints nothing.",
-            inputSchema: CreateAgentInput,
-            annotations: {
-                title: "Create agent",
-                readOnlyHint: false,
-                destructiveHint: false,
-                idempotentHint: true,
-                // Creating an agent creates a principal in Gate, which is a system outside Intel.
-                openWorldHint: true,
-            },
-        }, async (input) => text(await deps.nodes.createAgent(actor, input, { token: deps.bearer })));
     }
     if (permits(deps.authorization, "knowledge", "write")) {
-        server.registerTool("agent_update", {
-            title: "Update agent definition",
-            description: "Append an immutable definition version to an agent using an optimistic base version.",
-            inputSchema: SaveAgentDefinitionInput,
-            annotations: {
-                title: "Update agent definition",
-                readOnlyHint: false,
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.saveAgentDefinition(actor, input, { token: deps.bearer })));
-        /**
-         * The MCP half of the "Replace key" action in the agent profile (D29, #207).
-         *
-         * ⚠️ `knowledge/write` like `agent_update`, not `agents/run`: which principal an agent acts as
-         * is a property of the agent, changed by whoever may change the agent. And the result names the
-         * principal and the moment — never the key, which went to the runtime and nowhere else.
-         */
-        server.registerTool("agent_rotate_key", {
-            title: "Replace an agent's application key",
-            description: "Issue a new Gate application key for an agent and give it to the agent runtime. The previous key stops working immediately. Use it when a run fails with agent_key_missing, or when a key may have been exposed. The key itself is never returned.",
-            inputSchema: RotateAgentKeyInput,
-            annotations: {
-                title: "Replace an agent's application key",
-                readOnlyHint: false,
-                // The old key stops working the moment this runs, and anything still using it breaks.
-                destructiveHint: true,
-                // Asking twice issues twice, and the second answer invalidates the first key.
-                idempotentHint: false,
-                // The principal lives in Gate, which is a system outside Intel.
-                openWorldHint: true,
-            },
-        }, async (input) => text(await deps.nodes.rotateAgentKey(actor, input, { token: deps.bearer })));
         server.registerTool("node_save", {
             title: "Save node version",
             description: "Append an immutable content version using an optimistic base version.",
@@ -528,93 +423,6 @@ export async function handleMcp(request, deps) {
                 openWorldHint: false,
             },
         }, async (input) => text(await deps.nodes.redefineTable(actor, input)));
-        /**
-         * The board's write surface (#285). No `knowledge_*` alias on any of them — these are new under
-         * the post-#125 naming.
-         *
-         * ⚠️ Not one of them takes a `baseVersionId`, and the descriptions say so. That is the property
-         * an agent has to be able to rely on: two agents working the same board at the same time touch
-         * different tasks, and neither is asked to read the whole board first or to retry a conflict
-         * that says nothing about what they were doing. The server applies each call by task id to the
-         * board as it stands at that moment.
-         */
-        server.registerTool("board_configure", {
-            title: "Configure board statuses",
-            description: 'Write the board\'s whole status list, in the order it should be drawn. Adding, renaming and reordering columns are all this call. The "archived" status is part of every board and cannot be removed, and a status that tasks still sit in cannot be removed either. Set "terminal" on a column to say that standing in it means the work is finished — that is what decides whether a task waiting on another is still blocked. Several columns may be terminal; "archived" always is and cannot be set otherwise. Omitting it leaves an ordinary column not terminal.',
-            inputSchema: ConfigureBoardInput,
-            annotations: {
-                title: "Configure board statuses",
-                readOnlyHint: false,
-                // Removing a column is possible here, so this is not a purely additive write.
-                destructiveHint: true,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.configureBoard(actor, input)));
-        server.registerTool("board_task_add", {
-            title: "Add board task",
-            description: "Add one task to a board. The server assigns its id and its place in the order; name afterTaskId or beforeTaskId to put it between two cards, or neither to put it last in its column. parentId makes it a subtask of another task on the same board, dependsOn names tasks of the same board it waits for, and references names Intel nodes. dependsOn, labels and references are sets: naming the same task, word or node twice is refused rather than quietly folded together. Needs no baseVersionId: tasks are addressed by id, so parallel writers do not collide.",
-            inputSchema: AddBoardTaskInput,
-            annotations: {
-                title: "Add board task",
-                readOnlyHint: false,
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.addBoardTask(actor, input)));
-        server.registerTool("board_task_update", {
-            title: "Update board task",
-            description: "Change what a task says: title, assignee, labels, dates, dependencies, description or references. Where a task SITS — its status, its parent, its order — is board_task_move instead. Every named field replaces its current value whole; fields that are not named stay as they are. dependsOn, labels and references are sets: appending to a list this task already holds is refused rather than quietly folded together, so read the current value before you write it back.",
-            inputSchema: UpdateBoardTaskInput,
-            annotations: {
-                title: "Update board task",
-                readOnlyHint: false,
-                // Every named field replaces what stood there; the version history keeps it, the task
-                // does not.
-                destructiveHint: true,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.updateBoardTask(actor, input)));
-        server.registerTool("board_task_move", {
-            title: "Move board task",
-            description: 'Move one task: into another status, under another parent, or between two neighbours. Archiving a task is this call with status "archived" — there is no separate verb, and nothing is deleted by it. Two moves on two different tasks both go through.',
-            inputSchema: MoveBoardTaskInput,
-            annotations: {
-                title: "Move board task",
-                readOnlyHint: false,
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.moveBoardTask(actor, input)));
-        server.registerTool("board_task_delete", {
-            title: "Delete board task",
-            description: 'Remove a task AND every subtask under it, recursively. The answer counts everything that went, and dependsOn entries in the remaining tasks that pointed at a deleted one are removed with it. To take a task off the board without losing it, move it to the "archived" status instead.',
-            inputSchema: DeleteBoardTaskInput,
-            annotations: {
-                title: "Delete board task",
-                readOnlyHint: false,
-                destructiveHint: true,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.deleteBoardTask(actor, input)));
-        server.registerTool("board_repair_task_ids", {
-            title: "Repair repeated board task ids",
-            description: "Give a fresh id to every task entry on a board that repeats an id another entry already used. Only a board imported from a hand-written or foreign bundle can hold such a pair, and it cannot be repaired with the other calls: they address a task by id, so they would read, write or remove both entries at once. The first entry under an id keeps it — that is the one every parentId and dependsOn on the board already means — and each later one becomes its own task with everything else it carries, so nothing is lost and no edge is invented. The answer names each pair. A board that names every task once is refused rather than rewritten. Repeated STATUS ids are repaired with board_configure instead, by writing the status list with distinct ids.",
-            inputSchema: RepairBoardTaskIdsInput,
-            annotations: {
-                title: "Repair repeated board task ids",
-                readOnlyHint: false,
-                // Nothing is removed and nothing is overwritten: one entry gains an id of its own and
-                // every other field on every task stays exactly as it stood.
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.nodes.repairBoardTaskIds(actor, input)));
         server.registerTool("node_update", {
             title: "Update node",
             description: "Rename, move, or describe a node.",
@@ -965,101 +773,6 @@ export async function handleMcp(request, deps) {
             },
         }, async (input) => text(await deps.flows.cancelRun(flowActor, input)));
     }
-    /**
-     * Driving an agent, over the same door the screen uses.
-     *
-     * ⚠️ The three below are the MCP half of the two head actions on the agent page — the repository's
-     * "one business layer, three thin surfaces" rule, kept in the same delivery. They call the runtime
-     * through `deps.agents`, which resolves the resource ACL and forwards the CALLER's bearer; a tool
-     * that reached the runtime with anything else would be Intel acting as somebody it is not.
-     */
-    if (permits(deps.authorization, "agents", "run")) {
-        server.registerTool("agent_pause", {
-            title: "Pause agent",
-            description: "Stop an agent from acting on its own: no schedule fires, no task and no mail is taken. Its chat keeps answering, and nothing is queued up for later.",
-            inputSchema: PauseAgentInput,
-            annotations: {
-                title: "Pause agent",
-                readOnlyHint: false,
-                // Nothing is deleted, and yet work that would have happened does not — a client deciding
-                // whether to ask first has to be told that.
-                destructiveHint: true,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.agents.request({
-            actor: agentActor,
-            token: deps.bearer,
-            agentId: input.nodeId,
-            method: "POST",
-            path: "/pause",
-            body: "{}",
-        })));
-        server.registerTool("agent_resume", {
-            title: "Resume agent",
-            description: "Let a paused agent act again. Its schedules are armed from the definition as it stands now; nothing that was due while it stood still is caught up.",
-            inputSchema: PauseAgentInput,
-            annotations: {
-                title: "Resume agent",
-                readOnlyHint: false,
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.agents.request({
-            actor: agentActor,
-            token: deps.bearer,
-            agentId: input.nodeId,
-            method: "POST",
-            path: "/resume",
-            body: "{}",
-        })));
-        /**
-         * ⚠️ The MCP half of the profile's cost figures, in the same delivery slice — the repository's
-         * "every user-visible capability has an Intel MCP equivalent" rule.
-         *
-         * ⚠️ Under `agents/run` beside pause and resume, not under `knowledge/read`. What an agent
-         * spends is as sensitive as what it did, and this answer stands beside the run list rather than
-         * beside the node.
-         *
-         * ⚠️ `status` travels with the numbers and is not flattened away. A client that read an empty
-         * `runs` list as "this agent is free" would be reporting a Cloudflare outage as a saving.
-         */
-        server.registerTool("agent_costs", {
-            title: "Agent costs",
-            description: "What one agent has actually cost, read from Cloudflare's AI Gateway log: per run, and as a total over the last 7 and 30 days. `status` says whether the numbers were read at all — `not_configured` and `unreadable` both mean no figures, never zero cost. `partial` means the read hit its page limit, so the totals are a floor.",
-            inputSchema: PauseAgentInput,
-            annotations: {
-                title: "Agent costs",
-                readOnlyHint: true,
-                destructiveHint: false,
-                idempotentHint: true,
-                openWorldHint: false,
-            },
-        }, async (input) => text(await deps.agentCosts.read(agentActor, input.nodeId)));
-        server.registerTool("agent_run_now", {
-            title: "Run agent now",
-            description: "Fire one of the agent's own schedules straight away, against the document or flow it names. The run appears in the agent's run list; a target the agent does not schedule is refused.",
-            inputSchema: RunAgentNowInput,
-            annotations: {
-                title: "Run agent now",
-                readOnlyHint: false,
-                destructiveHint: false,
-                // Every run is a new run, so asking twice runs it twice.
-                idempotentHint: false,
-                // The agent may reach whatever its own definition grants it, so what a run touches is not
-                // knowable from this schema.
-                openWorldHint: true,
-            },
-        }, async (input) => text(await deps.agents.request({
-            actor: agentActor,
-            token: deps.bearer,
-            agentId: input.nodeId,
-            method: "POST",
-            path: "/run",
-            body: JSON.stringify({ target: input.target }),
-        })));
-    }
     if (permits(deps.authorization, "tools", "read")) {
         server.registerTool("tools_catalog_list", {
             title: "List tools",
@@ -1073,9 +786,7 @@ export async function handleMcp(request, deps) {
                 openWorldHint: false,
             },
         }, async () => text(await deps.tools.catalog(toolActor)));
-        // The MCP twin of the picker in the agent profile (D30): whole servers, so an agent can be
-        // given tools from a client instead of from the screen. Assigning and removing is
-        // `agent_update` — a delegation is a field of the definition, not a surface of its own.
+        // The servers behind the same live list (D30), as the portal itself names them.
         server.registerTool("tools_servers_list", {
             title: "List tool servers",
             description: "List the MCP servers the calling user reaches through the portal, as the portal itself names them. These are the handles an agent definition may delegate.",

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";
 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 [];