@bicharts/chart-mcp 0.6.66 → 0.6.68

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bicharts/chart-mcp",
-  "version": "0.6.66",
+  "version": "0.6.68",
   "description": "MCP (Model Context Protocol) stdio server for BIC AI charts: profile a dataset locally, then generate chart code that has passed the BIC backend's render gates. Works with any MCP-capable client (Claude Code, Claude Desktop, Cursor, Copilot Studio). An account pays to author charts; the code it writes is yours and runs with no licence.",
   "keywords": [
     "mcp",
@@ -13,6 +13,10 @@
     "bic"
   ],
   "homepage": "https://bizintelligencechampions.com/regiabi/developers?loc=npmmcp",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/codexguy/regiabi-plugins.git"
+  },
   "mcpName": "com.regiabi/chart-mcp",
   "author": "CodeX Enterprises LLC",
   "license": "SEE LICENSE IN LICENSE.txt",

package/skills/bic-charts/SKILL.md

@@ -170,7 +170,8 @@ Asking for these in `prompt` prose instead is the most expensive mistake availab
 routinely costs two or three extra generations, and each one is minutes of wall-clock.
 
 Other parameters worth knowing: `chart_type` (a preference, honored unless the data shape
-disqualifies it), `renderer: "D3"` for a web app, `width`/`height`, and
+disqualifies it), `renderer` (a JavaScript or TypeScript project gets D3 without asking, because D3 is what
+`@bicharts/chart-host` draws), `width`/`height`, and
 `reasoning_mode: "1P"` when you want the cheapest, fastest pass.
 
 **Generation takes minutes.** Fire the calls for independent charts **in parallel** rather
@@ -796,9 +797,13 @@ off its `BicChartPanel`, so pass no size unless you mean another one. A `WARNING
 label cut off at that size: deal with it before you call the chart done. The reply says whether more room fixes it.
 Never edit the generated chart code by hand: if something's wrong with a generated chart, regenerate it
 (`generate_chart` with a prompt describing the fix) or report it.
+Then run `check_app` once on the whole app, before every deploy: it reads how the page uses the library (selection
+through `useBicFilter` + `selects`, a chart's own controls through `useBicControls`, notes through `annotations`, every
+chart in a `BicChartPanel`), draws every chart together, and compares the stack with npm. Each finding names the file,
+the line and the call to use instead; fix the ERRORs in the app's own files before deploying.
 You don't need to deploy to check a chart. The template's `validate:visual` checks `VegaVisual` factories; a
-RegiaBI chart's check is `check_chart` - don't list it there. And `check_chart` checks the chart, not the app: the
-template's app-validation in the portal embed still applies. Then `npx tsc -b` and the tests. To test the page's behaviour,
+RegiaBI chart's check is `check_chart` - don't list it there. `check_chart` and `check_app` check the charts and how
+the app uses them; the template's app-validation in the portal embed still applies. Then `npx tsc -b` and the tests. To test the page's behaviour,
 `@bicharts/chart-host/testing` has a reader's gestures - `clickMark`, `clickEmpty`, `selectedRows` - for the checks
 worth keeping: a second click on a mark clears its filter, and a page Clear clears the chart's marks. Deploying (`npx rayfin up`), on Rayfin 1.36.1:
 - Signed in? `npx rayfin login status` (a subcommand, not a `--status` flag); `npx rayfin login` if not.