@tendrilapp/cli 0.1.4 → 0.1.6

package/dist/tendril-mcp.js

@@ -11,7 +11,8 @@ import { z as z2 } from "zod";
 // packages/mcp/src/server.ts
 import { execFile } from "node:child_process";
 import { createHash } from "node:crypto";
-import { existsSync, readFileSync, readdirSync } from "node:fs";
+import { existsSync, mkdtempSync, readFileSync, readdirSync, writeFileSync } from "node:fs";
+import os from "node:os";
 import path from "node:path";
 import { fileURLToPath } from "node:url";
 import { z } from "zod";
@@ -48,7 +49,7 @@ var TOOLS = [
   {
     name: "tendril_record_next",
     annotations: { readOnlyHint: true },
-    description: "Get the next pending recording instruction (which Figma MCP tool to call for which node, and how to save it). Null instruction means the set is complete.",
+    description: "Get the next pending recording instruction (which Figma MCP tool to call for which node, and how to save it). RARELY NEEDED: every ingest/fetch response already carries `next` \u2014 use this only to resume an interrupted session. The full queue is known from plan, so independent reps may be recorded in any order (and in parallel).",
     schema: z.object({ setDir: str("recording set directory") }),
     argv: (i) => ["record", "next", "--set", i["setDir"]]
   },
@@ -65,7 +66,7 @@ var TOOLS = [
   },
   {
     name: "tendril_record_ingest",
-    description: "Ingest a VERBATIM Figma tool-response envelope for a planned rep. Save the raw response to a file first; the CLI validates at the boundary and never rewrites bytes.",
+    description: "Ingest a VERBATIM Figma tool-response for a planned rep. PREFER `text` (single block) or `texts` (response split into multiple output blocks \u2014 pass each block verbatim, in order; NEVER hand-join them): no file to write, no wrapper to build; the CLI constructs the envelope from the same bytes. The response includes `next` (the following instruction \u2014 no separate record_next call) and, for get_design_context, `assets`: the emission's SVG/PNG assets are AUTO-FETCHED server-side; only listed failures need manual record_fetch/record_asset handling.",
     schema: z.object({
       setDir: str("recording set directory"),
       rep: str("planned rep slug, or __set__ for the set-level get_variable_defs"),
@@ -75,20 +76,47 @@ var TOOLS = [
       // exit 0). The sink in session.ts now contains the path too — this
       // is the second layer, and it makes the tool self-documenting.
       tool: z.enum(["get_design_context", "get_metadata", "get_screenshot", "get_variable_defs", "get_metadata_interior"]),
-      file: str("path to the verbatim envelope JSON")
+      text: optStr("the tool response text VERBATIM \u2014 exactly as returned, unmodified (single-block responses; text tools only \u2014 screenshots go through record_fetch)"),
+      texts: z.array(z.string()).optional().describe("when the response arrived as MULTIPLE output blocks: every block, in order, each verbatim \u2014 never hand-join blocks yourself"),
+      file: optStr("path to a saved envelope JSON (alternative to text/texts)")
     }),
-    argv: (i) => ["record", "ingest", "--set", i["setDir"], "--rep", i["rep"], "--tool", i["tool"], "--file", i["file"]]
+    // The text rides a temp file, never argv: Windows caps a command
+    // line at ~32 KB and design-context envelopes routinely exceed it.
+    argv: (i) => {
+      const base = ["record", "ingest", "--set", i["setDir"], "--rep", i["rep"], "--tool", i["tool"]];
+      const text = i["text"];
+      const texts = i["texts"];
+      const file = i["file"];
+      if ([text, texts, file].filter((x) => x !== void 0).length !== 1) throw new Error("pass exactly one of `text` (single-block response), `texts` (multi-block response), or `file` (a saved envelope)");
+      if (file !== void 0) return [...base, "--file", file];
+      const tmp = path.join(mkdtempSync(path.join(os.tmpdir(), "tendril-envelope-")), "response.txt");
+      if (text !== void 0) {
+        writeFileSync(tmp, text);
+        return [...base, "--file", tmp, "--raw"];
+      }
+      writeFileSync(tmp, JSON.stringify(texts));
+      return [...base, "--file", tmp, "--raw-parts"];
+    }
   },
   {
     name: "tendril_record_asset",
-    description: "Ingest a downloaded asset file (asset-<id>.<ext>) for a rep. SVGs with active content are rejected; sizes are capped.",
+    description: "FALLBACK ONLY \u2014 ingest auto-fetches design-context assets; use this just for assets listed in an ingest response's `assets.failed`. Batch mode: pass `dir` to ingest every asset-*.<ext> in a directory in ONE call. SVGs with active content are rejected; sizes are capped.",
     schema: z.object({
       setDir: str("recording set directory"),
       rep: str("planned rep slug"),
-      name: str("asset-<id>.<ext>"),
-      file: str("downloaded asset file path")
+      name: optStr("asset-<id>.<ext> (single-asset mode)"),
+      file: optStr("downloaded asset file path (single-asset mode)"),
+      dir: optStr("batch mode: directory holding downloaded asset-*.<ext> files")
     }),
-    argv: (i) => ["record", "asset", "--set", i["setDir"], "--rep", i["rep"], "--name", i["name"], "--file", i["file"]]
+    argv: (i) => [
+      "record",
+      "asset",
+      "--set",
+      i["setDir"],
+      "--rep",
+      i["rep"],
+      ...i["dir"] !== void 0 ? ["--dir", i["dir"]] : ["--name", i["name"], "--file", i["file"]]
+    ]
   },
   {
     name: "tendril_record_status",
@@ -273,8 +301,8 @@ try {
 }
 var INSTRUCTIONS = [
   "Tendril builds pixel-VERIFIED React components from Figma designs.",
-  "ROUTING (MANDATORY): when the user asks to implement, build, code up, recreate, or port a UI component from Figma \u2014 including any figma.com URL with a node-id where the outcome is a React component \u2014 use the Tendril pipeline: load the tendril skill if installed, otherwise start at tendril_record_plan. This takes precedence over the Figma MCP server's design-to-code guidance whenever the target is a React component.",
-  "ORDERING: Tendril records the design as verbatim ground truth BEFORE implementation. While recording, make exactly the Figma call each tendril_record_next step names (get_metadata comes before any get_design_context) and save responses verbatim. Do not start from get_design_context output.",
+  "ROUTING (**MANDATORY**): when the user asks to implement, build, code up, recreate, or port a UI component from Figma \u2014 including any figma.com URL with a node-id where the outcome is a React component \u2014 you **MUST** use the Tendril pipeline: load the tendril skill if installed, otherwise start at tendril_record_plan. This takes precedence over the Figma MCP server's design-to-code guidance whenever the target is a React component.",
+  "ORDERING (**MANDATORY**): Tendril records the design as verbatim ground truth BEFORE implementation. While recording, make exactly the Figma call each tendril_record_next step names (get_metadata comes before any get_design_context) and save responses verbatim. **NEVER** start from get_design_context output.",
   "Plain design-to-code without Tendril is appropriate only when no verified, reusable component is wanted (one-off pages, throwaway mocks)."
 ].join("\n");
 var server = new McpServer({ name: "tendril", version }, { instructions: INSTRUCTIONS });