@calibrate-ds/cli 0.1.87 → 0.1.88

package/README.md

@@ -768,6 +768,6 @@ See [PTB.md](./PTB.md) for architecture, type definitions, the generator interfa
 ```bash
 pnpm install
 pnpm build
-pnpm test            # 586 tests across core, generator, and CLI
+pnpm test            # 593 tests across core, generator, and CLI
 node apps/cli/dist/index.js --help
 ```

package/dist/mcp/tools/action-tools.js

@@ -293,7 +293,9 @@ DIVISION OF LABOR WITH FIGMA MCP (composite workflow — most accurate):
 TYPICAL WORKFLOW:
 1. Call start_work("<name>") — read blockedBy and tokenConflicts first
 2. For each blocker: call start_work("<dep>"), implement, call submit_work("<dep>")
-3. Read contextFile for the full implementation brief
+3. Read contextFile for the full implementation brief (it contains promptText, the
+   render tree, and variantDiffs — these are intentionally NOT inlined in this
+   response because they exceed the tool-call size limit on large components)
 4. Implement the requested component
 5. Call submit_work("<name>") when done`, { name: z.string().describe("Component to start working on, e.g. 'SearchBar'") }, async ({ name }) => {
             let ctx;
@@ -411,7 +413,11 @@ TYPICAL WORKFLOW:
                                 layout: context.layout,
                                 size: context.size,
                                 docs: buildDocsPayload(context, codeName, ctx),
-                                promptText: promptPackage.promptText,
+                                // NEW-8: promptText (often 100 KB+) is NOT inlined here — it blew the
+                                // MCP tool-call token limit (94.7% of the payload) and failed the call
+                                // outright on large component-sets. The full brief lives in contextFile
+                                // (unchanged — it still contains promptText and every detail); read it
+                                // from there. Only the compact instructions/summary travel in the payload.
                                 instructions: promptPackage.instructions,
                                 structureSummary: promptPackage.structureSummary,
                                 // Token conflicts: slots where PTB's resolved token hex differs from
@@ -700,7 +706,9 @@ recursively when you call it for that dependency.`, { name: z.string().describe(
                                 layout: context.layout,
                                 size: context.size,
                                 docs: buildDocsPayload(context, codeName, ctx),
-                                promptText: promptPackage.promptText,
+                                // NEW-8: promptText is NOT inlined (it exceeds the MCP tool-call token
+                                // limit on large components). The full brief — including promptText — is
+                                // in contextFile, which is unchanged; read it from there.
                                 instructions: promptPackage.instructions,
                                 structureSummary: promptPackage.structureSummary,
                                 ...(context.tokenConflicts?.length

package/dist/mcp/tools/info-tools.js

@@ -3,6 +3,13 @@ import * as path from "node:path";
 import { z } from "zod";
 import { resolveToken } from "@calibrate-ds/core";
 const UPGRADE_CHECKLIST = {
+    "0.1.88": [
+        "0.1.87 audit fixes (docs/PTB_0187_REPORT.md). Closes the last functional beta blocker plus the emitter-parity residuals. Six-plus releases, zero regressions.",
+        "FIX (NEW-8, open since .79 — was FAILING HARD): start_work's MCP response inlined promptText (100 KB+, 94.7% of the payload), so start_work on a large component-set EXCEEDED the tool-call token limit and the call failed outright. promptText is no longer inlined in the response. The contextFile on disk is UNCHANGED — it still contains promptText and every detail; read the full brief from there (the tool description says so). This unblocks the primary agent entry point.",
+        "FIX (E-19 parity): multi-mode themes (e.g. Light/Dark) reached the canonical tokens.css but NOT the per-collection css/<name>.css or the TS export <name>.ts. All three emitters now emit every mode — per-collection CSS gets [data-theme] blocks; the TS export carries a valuesByMode field per token.",
+        "FIX (E-9 parity): a malformed hex value (e.g. #GGGGGG) was dropped from CSS but still leaked into the TS export. It's now skipped by every emitter, including <name>.ts. A shared token-value guard + a cross-emitter parity test prevent this fix-one-emitter class from recurring.",
+        "Re-run 'ptb generate-tokens' (or let start_work regenerate) to pick up the emitter fixes. No re-scan needed for these. Restart your IDE's MCP server for the start_work payload change. 593 tests.",
+    ],
     "0.1.87": [
         "LICENSE CHANGE release — no code changes. Calibrate is now licensed under the Functional Source License (FSL-1.1-MIT), a source-available license, instead of Apache-2.0.",
         "What it means: you may still read, use, copy, modify, and redistribute the software freely for any purpose EXCEPT a Competing Use (offering it as a commercial product/service that substitutes for Calibrate). Each version additionally becomes MIT-licensed two years after its release.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@calibrate-ds/cli",
-  "version": "0.1.87",
+  "version": "0.1.88",
   "license": "FSL-1.1-MIT",
   "type": "module",
   "main": "dist/index.js",
@@ -44,10 +44,10 @@
     "commander": "^14.0.3",
     "openai": "^6.34.0",
     "zod": "^4.3.6",
-    "@calibrate-ds/figma-client": "^0.1.87",
-    "@calibrate-ds/generator-react": "^0.1.87",
-    "@calibrate-ds/core": "^0.1.87",
-    "@calibrate-ds/shared-types": "^0.1.87"
+    "@calibrate-ds/core": "^0.1.88",
+    "@calibrate-ds/figma-client": "^0.1.88",
+    "@calibrate-ds/generator-react": "^0.1.88",
+    "@calibrate-ds/shared-types": "^0.1.88"
   },
   "devDependencies": {
     "@types/node": "^22.13.5",