@adobe/design-data-agent-mcp 1.14.0 → 1.14.2

package/README.md

@@ -2,6 +2,26 @@
 
 MCP server and Claude Code skill for the [Spectrum Design Data](../../packages/design-data/) agent surface. Read tools (`primer`, `resolve_token`, `query_tokens`, `suggest_token`, `describe_component`, `describe_guideline`, `list_guidelines`) run fully in-process via `@adobe/design-data-wasm` — no CLI binary required for those. `suggest_token` uses the wasm `suggest` API directly; `authoring_session_step_intent` still invokes the native binary for session-state-aware ranking within an authoring flow.
 
+## Testing guideline content
+
+Run `moon run design-data-agent-mcp:test`. For the packaged content contracts only,
+after `moon run sdk-wasm:build`, run:
+
+```sh
+pnpm --filter @adobe/design-data-agent-mcp exec ava test/packaged-guidelines.test.js
+```
+
+The suite uses `pnpm pack` to test the agent's publishable files, extracts the
+tarball into a fresh private tree, and vendors local runtime dependencies using
+the MCPB packaging allowlists. It initializes the packed server over stdio with
+no data overrides, checks the catalog against the canonical manifest, compares
+every guideline response to source JSON, and checks invalid-slug errors. An import
+guard rejects ESM imports and CommonJS requires outside the private tree.
+
+Dependencies come from the local build, not registry tarballs, so this is not a
+registry-install test. It does not assess model answer quality. The tests remove
+private staging trees afterward.
+
 ## Install
 
 ### Claude Code (skill + optional MCP)
@@ -74,8 +94,9 @@ node tools/design-data-agent-mcp/src/index.js
 | `DESIGN_DATA_PLATFORM`   | —             | Select a named `[platforms.<id>]` entry (needs `DESIGN_DATA_CONFIG`)           |
 
 > **Platform cascade.** If `DESIGN_DATA_CONFIG` is set, the server shells out to
-> the `design-data` CLI once at startup (`design-data query --filter "" --format
-> json`, run from the config's directory) to resolve its `.design-data.toml`
+> the `design-data` CLI once at startup
+> (`design-data query --filter "" --format json`, run from the config's directory)
+> to resolve its `.design-data.toml`
 > source (path/npm/github/git) and either its top-level `manifest` cascade or,
 > if `DESIGN_DATA_PLATFORM` is also set, that named `[platforms.<id>]` entry's
 > manifest — mirroring the CLI's own `--platform`/`DESIGN_DATA_PLATFORM`, then

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adobe/design-data-agent-mcp",
-  "version": "1.14.0",
+  "version": "1.14.2",
   "description": "MCP server and Claude Code skill for the design-data agent surface — read tools run in-process via wasm",
   "type": "module",
   "main": "./src/index.js",
@@ -30,9 +30,9 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.27.1",
-    "@adobe/design-data": "3.2.2",
-    "@adobe/design-data-wasm": "0.10.1",
-    "@adobe/spectrum-design-data": "3.3.0"
+    "@adobe/design-data-wasm": "0.10.3",
+    "@adobe/design-data": "3.2.4",
+    "@adobe/spectrum-design-data": "3.4.0"
   },
   "devDependencies": {
     "ava": "^6.0.1"

package/skills/design-data/SKILL.md

@@ -6,7 +6,7 @@ description: >
   system, token lookup, spec-conformance, drift detection, or token authoring on custom data.
 metadata:
   author: adobe
-  version: "1.14.0"
+  version: "1.14.2"
 when_to_use: >
   Trigger on: design system, design tokens, spec-conformant, drift, validate tokens, token
   authoring, custom dataset, DESIGN_DATA_PATH, design-data validate, design-data diff,