graphein-mcp 0.7.2 → 0.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "graphein-mcp",
-  "version": "0.7.2",
+  "version": "0.8.0",
   "type": "module",
   "description": "Model Context Protocol server for Graphein — wraps generate → validate → repair → render → critique into one tool call, and serves Graphein's schema + agent guide as resources so a model that never saw the API can still build correct charts.",
   "license": "MIT",
@@ -61,9 +61,9 @@
     "prepack": "tsup"
   },
   "dependencies": {
-    "@graphein/node": "^0.7.2",
+    "@graphein/node": "^0.8.0",
     "@modelcontextprotocol/sdk": "^1.20.0",
-    "graphein": "^0.7.2",
+    "graphein": "^0.8.0",
     "zod": "^3.23.0"
   }
 }

package/resources/agent-guide.md

@@ -540,9 +540,9 @@ const d = renderDashboard('#app', dash);
   a column that view's data lacks is **ignored for that view** (it is *not* blanked). So
   if you want a pre‑aggregated chart to react to a slicer, include that field in its
   rows (e.g. aggregate by `region × product`, not `region` alone).
-- **Chart clicks cross‑highlight** — clicking a mark emphasizes the matching subset in
-  views that encode the same field (and always self‑highlights). Highlight is per‑mark,
-  so it only applies where the field is plotted.
+- **Chart clicks cross‑filter** — clicking a mark subsets rows in every other view
+  (like a slicer), while the clicked chart dims its own unpicked marks instead of
+  hiding them. The source self‑highlights; peers are filtered.
 
 Opt out with `interactions:'none'`, or replace auto‑wiring with explicit links:
 

package/resources/chart-spec.schema.json

@@ -2319,7 +2319,7 @@
               }
             }
           ],
-          "description": "Cross-interaction policy:\n- 'auto' (default): slicers filter charts; chart clicks cross-highlight charts sharing the selected field.\n- 'none': views are laid out but not linked.\n- an array of InteractionLink: explicit wiring (replaces auto)."
+          "description": "Cross-interaction policy:\n- 'auto' (default): every source cross-filters the page — slicers and chart clicks both subset rows in the other views; the clicked chart dims its own unpicked marks instead of hiding them.\n- 'none': views are laid out but not linked.\n- an array of InteractionLink: explicit wiring (replaces auto)."
         }
       },
       "required": [

package/resources/spec-reference.md

@@ -1048,8 +1048,8 @@ per‑type defaults).
   field is subset by the slicer (a KPI, a table, a chart that inherits the dashboard
   data). A filter on a column a view's data doesn't contain is **ignored for that view**,
   not blanked — so a pre‑aggregated view only reacts to the dimensions it carries.
-- **Chart clicks cross‑highlight** — clicking a mark emphasizes the matching subset in
-  views that encode the same field, and always self‑highlights.
+- **Chart clicks cross‑filter** — clicking a mark subsets rows in every other view
+  (like a slicer); the clicked chart dims its own unpicked marks instead of hiding them.
 
 **Explicit links** replace auto‑wiring with an array of `InteractionLink`: