kanbo-cli 0.1.0 → 0.1.2

package/dist/lib/mcp/index.cjs

@@ -1,5 +1,5 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_manifest = require("../manifest-CpZOcB_6.cjs");
+const require_manifest = require("../manifest-CmiuDqH-.cjs");
 const require_migrations_path = require("../migrations-path-CZxVOgeD.cjs");
 let zod = require("zod");
 //#region src/mcp/http-transport.ts
@@ -171,6 +171,7 @@ function createHttpTransport(input) {
 //#endregion
 exports.KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI = require_manifest.KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI;
 exports.KANBO_CAPABILITIES_RESOURCE_URI = require_manifest.KANBO_CAPABILITIES_RESOURCE_URI;
+exports.KANBO_MCP_INSTRUCTIONS = require_manifest.KANBO_MCP_INSTRUCTIONS;
 exports.KANBO_MCP_SERVER_NAME = require_manifest.KANBO_MCP_SERVER_NAME;
 exports.KANBO_TOOLS = require_manifest.KANBO_TOOLS;
 exports.KANBO_TOOL_CLI_EQUIVALENTS = require_manifest.KANBO_TOOL_CLI_EQUIVALENTS;

package/dist/lib/mcp/index.d.cts

@@ -1,5 +1,5 @@
-import { s as IssueRun, t as Issue } from "../schema-fsHqNAip.cjs";
-import { i as KanboToolName, n as KANBO_TOOL_NAMES, r as KanboToolCliEquivalent, s as EntryRule, t as KANBO_TOOL_CLI_EQUIVALENTS } from "../tool-names-9cmCn0gP.cjs";
+import { s as IssueRun, t as Issue } from "../schema-D0MyXcej.cjs";
+import { i as KanboToolName, n as KANBO_TOOL_NAMES, r as KanboToolCliEquivalent, s as EntryRule, t as KANBO_TOOL_CLI_EQUIVALENTS } from "../tool-names-WfH4IURz.cjs";
 import { z } from "zod";
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { CallToolResult } from "@modelcontextprotocol/sdk/types.js";
@@ -233,13 +233,27 @@ interface KanboHttpTransportInput {
    */
   workspaceId: () => string;
 }
-declare function createHttpTransport(input: KanboHttpTransportInput): KanboToolTransport;
+export declare function createHttpTransport(input: KanboHttpTransportInput): KanboToolTransport;
+//#endregion
+//#region src/mcp/instructions.d.ts
+/**
+ * What `kanbo mcp` tells a client when it connects — the `instructions` of the
+ * MCP initialize result, which a client hands its model before any tool is
+ * called. An agent with nothing but this server connected learns from it how
+ * to work the board, with no instruction file in the project.
+ *
+ * Static on purpose: it is sent before any board is resolved, so it says
+ * nothing about columns — `kanbo_prime` returns those. The rules are the
+ * sentences `ops/agent-rules.ts` holds for every surface, with the tool beside
+ * each; the full manifest stays a resource.
+ */
+export declare const KANBO_MCP_INSTRUCTIONS: string;
 //#endregion
 //#region src/mcp/resources.d.ts
 /** The URI a client reads the manifest as JSON from. */
-declare const KANBO_CAPABILITIES_RESOURCE_URI = "kanbo://capabilities";
+export declare const KANBO_CAPABILITIES_RESOURCE_URI = "kanbo://capabilities";
 /** The URI a client reads the same manifest from, laid out as Markdown. */
-declare const KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI = "kanbo://capabilities.md";
+export declare const KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI = "kanbo://capabilities.md";
 /**
  * The board's own capabilities manifest, as two MCP resources rather than a
  * tool: a client reads it once, before it ever calls a board tool, to learn
@@ -253,7 +267,7 @@ declare const KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI = "kanbo://capabilities.m
  * with no server around it still gets the manifest from the one server it is
  * talking to.
  */
-declare function registerKanboCapabilitiesResources(server: McpServer): void;
+export declare function registerKanboCapabilitiesResources(server: McpServer): void;
 //#endregion
 //#region src/mcp/tools/tool.d.ts
 /**
@@ -297,7 +311,7 @@ interface KanboTool {
  * whether they run against a server or against the board directly, and the
  * only thing a host decides is which of them it publishes.
  */
-declare const KANBO_TOOLS: readonly KanboTool[];
+export declare const KANBO_TOOLS: readonly KanboTool[];
 /** What a host decides about the board's tools. */
 interface KanboToolOptions {
   /** Publish `kanbo_run_start` and `kanbo_run_finish`. False for a host that manages runs itself. */
@@ -315,11 +329,11 @@ interface KanboToolRegistration {
  * to publish the tool, and the transport is only called when a client actually
  * calls one.
  */
-declare function buildKanboTools(transport: KanboToolTransport, options: KanboToolOptions): KanboToolRegistration[];
+export declare function buildKanboTools(transport: KanboToolTransport, options: KanboToolOptions): KanboToolRegistration[];
 //#endregion
 //#region src/mcp/server.d.ts
 /** The name a client sees this server under. */
-declare const KANBO_MCP_SERVER_NAME = "kanbo";
+export declare const KANBO_MCP_SERVER_NAME = "kanbo";
 /**
  * Add the board's tools to a server that already exists.
  *
@@ -327,7 +341,7 @@ declare const KANBO_MCP_SERVER_NAME = "kanbo";
  * tool an agent has, and the board's are part of that inventory rather than a
  * second server the runtime would have to be told about.
  */
-declare function registerKanboTools(server: McpServer, transport: KanboToolTransport, options: KanboToolOptions): void;
+export declare function registerKanboTools(server: McpServer, transport: KanboToolTransport, options: KanboToolOptions): void;
 /**
  * A server that is only the board — what `kanbo mcp` serves to a client that
  * brings no board tools of its own: an editor, an agent CLI, another machine.
@@ -339,8 +353,11 @@ declare function registerKanboTools(server: McpServer, transport: KanboToolTrans
  * function: it documents its capabilities its own way, and adding a second
  * `kanbo://` resource namespace to an inventory that is not only the board's
  * is a decision for that server to make, not this one.
+ *
+ * For the same reason it alone sends `KANBO_MCP_INSTRUCTIONS` in the initialize
+ * result: the instructions of a server that is only the board.
  */
-declare function createKanboMcpServer(transport: KanboToolTransport, options: KanboToolOptions): McpServer;
+export declare function createKanboMcpServer(transport: KanboToolTransport, options: KanboToolOptions): McpServer;
 //#endregion
-export { KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI, KANBO_CAPABILITIES_RESOURCE_URI, KANBO_MCP_SERVER_NAME, KANBO_TOOLS, KANBO_TOOL_CLI_EQUIVALENTS, KANBO_TOOL_NAMES, type KanboActiveRunResult, type KanboCardResult, type KanboColumnResult, type KanboCommentResult, type KanboHttpRequest, type KanboHttpTransportInput, type KanboPullRequestResult, type KanboRunResult, type KanboTool, type KanboToolCliEquivalent, type KanboToolName, type KanboToolOptions, type KanboToolRegistration, type KanboToolResult, type KanboToolTransport, buildKanboTools, createHttpTransport, createKanboMcpServer, registerKanboCapabilitiesResources, registerKanboTools };
+export { KANBO_TOOL_CLI_EQUIVALENTS, KANBO_TOOL_NAMES, type KanboActiveRunResult, type KanboCardResult, type KanboColumnResult, type KanboCommentResult, type KanboHttpRequest, type KanboHttpTransportInput, type KanboPullRequestResult, type KanboRunResult, type KanboTool, type KanboToolCliEquivalent, type KanboToolName, type KanboToolOptions, type KanboToolRegistration, type KanboToolResult, type KanboToolTransport };
 //# sourceMappingURL=index.d.cts.map

package/dist/lib/mcp/index.d.mts

@@ -1,5 +1,5 @@
-import { s as IssueRun, t as Issue } from "../schema-fsHqNAip.mjs";
-import { i as KanboToolName, n as KANBO_TOOL_NAMES, r as KanboToolCliEquivalent, s as EntryRule, t as KANBO_TOOL_CLI_EQUIVALENTS } from "../tool-names-Dxg1UTUl.mjs";
+import { s as IssueRun, t as Issue } from "../schema-D0MyXcej.mjs";
+import { i as KanboToolName, n as KANBO_TOOL_NAMES, r as KanboToolCliEquivalent, s as EntryRule, t as KANBO_TOOL_CLI_EQUIVALENTS } from "../tool-names-3q_GEZej.mjs";
 import { z } from "zod";
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { CallToolResult } from "@modelcontextprotocol/sdk/types.js";
@@ -233,13 +233,27 @@ interface KanboHttpTransportInput {
    */
   workspaceId: () => string;
 }
-declare function createHttpTransport(input: KanboHttpTransportInput): KanboToolTransport;
+export declare function createHttpTransport(input: KanboHttpTransportInput): KanboToolTransport;
+//#endregion
+//#region src/mcp/instructions.d.ts
+/**
+ * What `kanbo mcp` tells a client when it connects — the `instructions` of the
+ * MCP initialize result, which a client hands its model before any tool is
+ * called. An agent with nothing but this server connected learns from it how
+ * to work the board, with no instruction file in the project.
+ *
+ * Static on purpose: it is sent before any board is resolved, so it says
+ * nothing about columns — `kanbo_prime` returns those. The rules are the
+ * sentences `ops/agent-rules.ts` holds for every surface, with the tool beside
+ * each; the full manifest stays a resource.
+ */
+export declare const KANBO_MCP_INSTRUCTIONS: string;
 //#endregion
 //#region src/mcp/resources.d.ts
 /** The URI a client reads the manifest as JSON from. */
-declare const KANBO_CAPABILITIES_RESOURCE_URI = "kanbo://capabilities";
+export declare const KANBO_CAPABILITIES_RESOURCE_URI = "kanbo://capabilities";
 /** The URI a client reads the same manifest from, laid out as Markdown. */
-declare const KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI = "kanbo://capabilities.md";
+export declare const KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI = "kanbo://capabilities.md";
 /**
  * The board's own capabilities manifest, as two MCP resources rather than a
  * tool: a client reads it once, before it ever calls a board tool, to learn
@@ -253,7 +267,7 @@ declare const KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI = "kanbo://capabilities.m
  * with no server around it still gets the manifest from the one server it is
  * talking to.
  */
-declare function registerKanboCapabilitiesResources(server: McpServer): void;
+export declare function registerKanboCapabilitiesResources(server: McpServer): void;
 //#endregion
 //#region src/mcp/tools/tool.d.ts
 /**
@@ -297,7 +311,7 @@ interface KanboTool {
  * whether they run against a server or against the board directly, and the
  * only thing a host decides is which of them it publishes.
  */
-declare const KANBO_TOOLS: readonly KanboTool[];
+export declare const KANBO_TOOLS: readonly KanboTool[];
 /** What a host decides about the board's tools. */
 interface KanboToolOptions {
   /** Publish `kanbo_run_start` and `kanbo_run_finish`. False for a host that manages runs itself. */
@@ -315,11 +329,11 @@ interface KanboToolRegistration {
  * to publish the tool, and the transport is only called when a client actually
  * calls one.
  */
-declare function buildKanboTools(transport: KanboToolTransport, options: KanboToolOptions): KanboToolRegistration[];
+export declare function buildKanboTools(transport: KanboToolTransport, options: KanboToolOptions): KanboToolRegistration[];
 //#endregion
 //#region src/mcp/server.d.ts
 /** The name a client sees this server under. */
-declare const KANBO_MCP_SERVER_NAME = "kanbo";
+export declare const KANBO_MCP_SERVER_NAME = "kanbo";
 /**
  * Add the board's tools to a server that already exists.
  *
@@ -327,7 +341,7 @@ declare const KANBO_MCP_SERVER_NAME = "kanbo";
  * tool an agent has, and the board's are part of that inventory rather than a
  * second server the runtime would have to be told about.
  */
-declare function registerKanboTools(server: McpServer, transport: KanboToolTransport, options: KanboToolOptions): void;
+export declare function registerKanboTools(server: McpServer, transport: KanboToolTransport, options: KanboToolOptions): void;
 /**
  * A server that is only the board — what `kanbo mcp` serves to a client that
  * brings no board tools of its own: an editor, an agent CLI, another machine.
@@ -339,8 +353,11 @@ declare function registerKanboTools(server: McpServer, transport: KanboToolTrans
  * function: it documents its capabilities its own way, and adding a second
  * `kanbo://` resource namespace to an inventory that is not only the board's
  * is a decision for that server to make, not this one.
+ *
+ * For the same reason it alone sends `KANBO_MCP_INSTRUCTIONS` in the initialize
+ * result: the instructions of a server that is only the board.
  */
-declare function createKanboMcpServer(transport: KanboToolTransport, options: KanboToolOptions): McpServer;
+export declare function createKanboMcpServer(transport: KanboToolTransport, options: KanboToolOptions): McpServer;
 //#endregion
-export { KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI, KANBO_CAPABILITIES_RESOURCE_URI, KANBO_MCP_SERVER_NAME, KANBO_TOOLS, KANBO_TOOL_CLI_EQUIVALENTS, KANBO_TOOL_NAMES, type KanboActiveRunResult, type KanboCardResult, type KanboColumnResult, type KanboCommentResult, type KanboHttpRequest, type KanboHttpTransportInput, type KanboPullRequestResult, type KanboRunResult, type KanboTool, type KanboToolCliEquivalent, type KanboToolName, type KanboToolOptions, type KanboToolRegistration, type KanboToolResult, type KanboToolTransport, buildKanboTools, createHttpTransport, createKanboMcpServer, registerKanboCapabilitiesResources, registerKanboTools };
+export { KANBO_TOOL_CLI_EQUIVALENTS, KANBO_TOOL_NAMES, type KanboActiveRunResult, type KanboCardResult, type KanboColumnResult, type KanboCommentResult, type KanboHttpRequest, type KanboHttpTransportInput, type KanboPullRequestResult, type KanboRunResult, type KanboTool, type KanboToolCliEquivalent, type KanboToolName, type KanboToolOptions, type KanboToolRegistration, type KanboToolResult, type KanboToolTransport };
 //# sourceMappingURL=index.d.mts.map

package/dist/lib/mcp/index.mjs

@@ -1,4 +1,4 @@
-import { U as normalizeStatusName, _ as projectKanboRun, c as registerKanboTools, d as KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI, f as KANBO_CAPABILITIES_RESOURCE_URI, g as projectKanboPullRequest, h as projectKanboColumn, i as KANBO_TOOL_NAMES, l as KANBO_TOOLS, m as projectKanboCard, o as KANBO_MCP_SERVER_NAME, p as registerKanboCapabilitiesResources, r as KANBO_TOOL_CLI_EQUIVALENTS, s as createKanboMcpServer, u as buildKanboTools, v as projectKanboSprint, y as projectKanboSubCard } from "../manifest-C0EcwwgO.mjs";
+import { G as normalizeStatusName, _ as projectKanboPullRequest, b as projectKanboSubCard, c as registerKanboTools, d as KANBO_MCP_INSTRUCTIONS, f as KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI, g as projectKanboColumn, h as projectKanboCard, i as KANBO_TOOL_NAMES, l as KANBO_TOOLS, m as registerKanboCapabilitiesResources, o as KANBO_MCP_SERVER_NAME, p as KANBO_CAPABILITIES_RESOURCE_URI, r as KANBO_TOOL_CLI_EQUIVALENTS, s as createKanboMcpServer, u as buildKanboTools, v as projectKanboRun, y as projectKanboSprint } from "../manifest-NRhhhOkC.mjs";
 import { a as BoardError } from "../migrations-path-Ciwan537.mjs";
 import { z } from "zod";
 //#region src/mcp/http-transport.ts
@@ -168,6 +168,6 @@ function createHttpTransport(input) {
 	};
 }
 //#endregion
-export { KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI, KANBO_CAPABILITIES_RESOURCE_URI, KANBO_MCP_SERVER_NAME, KANBO_TOOLS, KANBO_TOOL_CLI_EQUIVALENTS, KANBO_TOOL_NAMES, buildKanboTools, createHttpTransport, createKanboMcpServer, registerKanboCapabilitiesResources, registerKanboTools };
+export { KANBO_CAPABILITIES_MARKDOWN_RESOURCE_URI, KANBO_CAPABILITIES_RESOURCE_URI, KANBO_MCP_INSTRUCTIONS, KANBO_MCP_SERVER_NAME, KANBO_TOOLS, KANBO_TOOL_CLI_EQUIVALENTS, KANBO_TOOL_NAMES, buildKanboTools, createHttpTransport, createKanboMcpServer, registerKanboCapabilitiesResources, registerKanboTools };
 
 //# sourceMappingURL=index.mjs.map