@bicharts/chart-mcp 0.6.67 → 0.6.69

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bicharts/chart-mcp",
-  "version": "0.6.67",
+  "version": "0.6.69",
   "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",
@@ -43,8 +47,8 @@
   },
   "// dependencies": "NONE, deliberately. dist/ bundles every module the server uses, so a runtime dependency installs nothing it needs - it only makes npx fetch that package (and its tree) before the first start. Everything the bundle carries is a devDependency; scripts/verify-package.mjs fails the release if a dependency appears or a shipped file imports anything but Node's built-ins.",
   "devDependencies": {
-    "@bicharts/chart-host": "^0.6.66",
-    "@bicharts/shape-core": "^0.6.66",
+    "@bicharts/chart-host": "^0.6.69",
+    "@bicharts/shape-core": "^0.6.69",
     "@modelcontextprotocol/sdk": "^1.0.0",
     "@types/node": "^20.0.0",
     "@types/papaparse": "^5.3.14",

package/skills/bic-charts/SKILL.md

@@ -15,6 +15,12 @@ run time, no per-render cost, and no network call. `@bicharts/chart-host` runs i
 generates it. Generation happens **once, at build time, by you** — never in your users'
 browsers.
 
+**Signing in needs no setup.** The first call that needs an account (`list_eligible_charts`,
+`generate_chart`) opens the person's browser on a sign-in page, waits for them, and then finishes
+the call. Tell them a browser tab is about to open. If the call comes back with "Sign in to
+continue" and a link instead, give them that link, and call again once they've signed in. A key in
+the server's environment is only for machines with no browser, such as CI.
+
 ## 0. Decide what to pull (only if you are starting from a data MODEL)
 
 Skip this if you already have a table. If you are holding a semantic model, a warehouse schema or
@@ -797,9 +803,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.