@unovis/mcp 1.7.0-mcp.2 → 1.7.0

package/docs/troubleshooting.md

@@ -29,21 +29,10 @@ used for measuring must match the font used for drawing.
 ## The client rejects the whole tool list
 
 If a client refuses to start with something like `input_schema: JSON schema is
-invalid. It must match JSON Schema draft 2020-12`, a tool schema is using a
-construct that only exists in draft-07. One bad schema takes down every tool,
-not just its own, because the tool list is validated as a unit.
-
-The SDK converts Zod v3 through `zod-to-json-schema`, which targets draft-07.
-Most of that output is valid 2020-12 as well; two things are not, and both are
-enforced by `test/tool-schemas.test.ts`:
-
-- **`z.tuple([a, b])`** lowers to the draft-07 array form of `items`, where
-  2020-12 requires `items` to be a schema. Use `z.array(a).length(2)`.
-- **Reusing one schema instance** inside a tool makes the converter emit
-  `$ref: #/properties/…`. That's valid, but clients that flatten refs drop the
-  subschema, leaving a property with no type — an array argument then arrives as
-  a string. Shared leaves (`fieldName()`, `hexColor()`) are factories so every
-  use site gets a fresh instance.
+invalid. It must match JSON Schema draft 2020-12`, one tool schema is invalid —
+and it takes down every tool, not just its own, because clients validate the
+tool list as a unit. Released versions guard against this, so if you see it,
+please report it with the client name and the full error message.
 
 ## A chart is blank
 
@@ -86,16 +75,12 @@ it would mean `outputType: "html"` silently producing a broken chart.
 > `@unovis/dagre-layout` ≥ 0.8.8-3. Earlier releases shipped extensionless ESM
 > imports that no standards-compliant Node loader could resolve.
 
-## The `tsx` loader can't load graph layouts
+## Graph charts time out under the `tsx` loader
 
-Running this package's **source** through `tsx` fails on the dynamic imports
-inside Unovis's graph layouts: the layout promise never settles, so the render
-times out after 20 seconds with "component layout never completed". Plain Node
-and vitest both work.
-
-That's why `pnpm dev` and `pnpm samples` build first and run the compiled
-output. `pnpm dev:tsx` is available for fast iteration, with the caveat that
-graph charts will not render under it.
+Running your script with `tsx` breaks the dynamic imports inside Unovis's
+graph layouts: the layout promise never settles, so a graph render times out
+after 20 seconds with "component layout never completed". Every other chart
+type is unaffected. Compile first and run plain Node (vitest also works).
 
 ## PNG has a transparent background
 
@@ -110,8 +95,9 @@ The `png` output type does this for you.
 
 ## Interactive output doesn't render in my client
 
-`outputType: "interactive"` depends on MCP UI resource support, which is
-experimental and unevenly implemented. Use `outputType: "html"` — it works
+`outputType: "interactive"` depends on the MCP Apps extension
+(`io.modelcontextprotocol/ui`) — official since protocol revision 2026-07-28,
+but host adoption is still uneven. Use `outputType: "html"` — it works
 everywhere because it's just a file.
 
 ## Large datasets
@@ -139,22 +125,5 @@ that safe. If you need byte-stable output (snapshot tests), pass a constant
 ## Something renders differently than in the browser
 
 Report it. The headless environment reimplements browser geometry, so a mismatch
-is a real bug in this package (or occasionally in Unovis, where several have
-already been found and fixed upstream). Useful details: the chart spec, the
+is a real bug in this package. Useful details: the chart spec, the
 output, and what you expected.
-
-## What the tests don't cover
-
-Worth knowing before you trust a green suite:
-
-- **Touch devices.** The Chromium smoke lane (`pnpm test:browser`) covers real
-  layout, paint, mouse hover and clicks — added after a crosshair bug passed
-  every jsdom test — but taps, drags and tooltip-linger semantics on actual
-  touch hardware remain untested.
-- **MCP UI widget rendering** in an actual client.
-- **Pixel baselines are light-theme.** Visual regression rasterizes every
-  fixture against committed baselines; dark theme is exercised structurally and
-  in `pnpm samples`, not pixel-compared.
-- **Non-`ts` code targets aren't compiled.** The vanilla-TypeScript output is
-  type-checked against `@unovis/ts`; the JSX and template targets are checked
-  structurally only.

package/docs/webview.md

@@ -72,14 +72,12 @@ app builds.
 ## Security posture
 
 The bundle contains no `fetch`, `XMLHttpRequest`, `WebSocket` or dynamic
-imports — asserted by a test on the built artifact — so the WebView needs no
-network access at all. Combined with local-asset loading, the chart surface
-adds zero egress.
+imports, so the WebView needs no network access at all. Combined with
+local-asset loading, the chart surface adds zero egress.
 
 ## Touch behavior
 
 Interaction events (`events: true`) report taps the same way clicks are
 reported in a browser. Two knowns: lines and areas have no per-datum element
-(the crosshair is their readout — it tracks touch-drag), and Unovis binds
-user event handlers through a throttled pass, active within ~500ms of the
-render settling.
+(the crosshair is their readout — it tracks touch-drag), and tap handlers
+become active within ~500ms of the render settling.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@unovis/mcp",
   "description": "MCP server that renders Unovis charts to SVG locally in Node — no browser, no remote services",
-  "version": "1.7.0-mcp.2",
+  "version": "1.7.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/f5/unovis.git",
@@ -42,7 +42,7 @@
       "default": "./dist/render/spec.js"
     },
     "./package.json": "./package.json",
-    "./chart-spec.schema.json": "./schema/chart-spec.v1.json"
+    "./chart-spec.schema.json": "./schema/chart-spec.v0.1.json"
   },
   "engines": {
     "node": ">=20"
@@ -57,10 +57,11 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.17.0",
     "zod": "^3.25.0",
-    "@unovis/ssr": "1.7.0-mcp.2",
-    "@unovis/ts": "1.7.0-mcp.2"
+    "@unovis/ssr": "1.7.0",
+    "@unovis/ts": "1.7.0"
   },
   "devDependencies": {
+    "@modelcontextprotocol/ext-apps": "^1.7.5",
     "@types/jsdom": "^21.1.7",
     "@types/node": "^20.17.0",
     "@types/pngjs": "^6.0.5",

package/schema/{chart-spec.v1.baseline.json → chart-spec.v0.1.baseline.json}

@@ -1,14 +1,14 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://unovis.dev/schema/chart-spec.v1.json",
+  "$id": "https://unovis.dev/schema/chart-spec.v0.1.json",
   "title": "Unovis ChartSpec",
-  "description": "The @unovis/mcp chart spec contract, version 1. Additions are non-breaking; the version moves only on breaking changes.",
+  "description": "The @unovis/mcp chart spec contract, version 0.1. While the major is 0, breaking changes bump the minor; from 1.0 on, additions are non-breaking and only the major breaks.",
   "type": "object",
   "properties": {
     "specVersion": {
-      "type": "integer",
-      "minimum": 1,
-      "description": "ChartSpec contract version (see SPEC_VERSION); additions are non-breaking, the integer moves only on breaking changes"
+      "type": "string",
+      "pattern": "^\\d+\\.\\d+$",
+      "description": "ChartSpec contract version as major.minor (see SPEC_VERSION). While the major is 0, breaking changes bump the minor; from 1.0 on, minors are additive and only the major breaks"
     },
     "container": {
       "type": "string",

package/schema/{chart-spec.v1.json → chart-spec.v0.1.json}

@@ -1,14 +1,14 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://unovis.dev/schema/chart-spec.v1.json",
+  "$id": "https://unovis.dev/schema/chart-spec.v0.1.json",
   "title": "Unovis ChartSpec",
-  "description": "The @unovis/mcp chart spec contract, version 1. Additions are non-breaking; the version moves only on breaking changes.",
+  "description": "The @unovis/mcp chart spec contract, version 0.1. While the major is 0, breaking changes bump the minor; from 1.0 on, additions are non-breaking and only the major breaks.",
   "type": "object",
   "properties": {
     "specVersion": {
-      "type": "integer",
-      "minimum": 1,
-      "description": "ChartSpec contract version (see SPEC_VERSION); additions are non-breaking, the integer moves only on breaking changes"
+      "type": "string",
+      "pattern": "^\\d+\\.\\d+$",
+      "description": "ChartSpec contract version as major.minor (see SPEC_VERSION). While the major is 0, breaking changes bump the minor; from 1.0 on, minors are additive and only the major breaks"
     },
     "container": {
       "type": "string",