@bicharts/chart-mcp 0.6.101 → 0.6.104

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bicharts/chart-mcp",
-  "version": "0.6.101",
+  "version": "0.6.104",
   "description": "AI Data Components for Power BI, Excel, Fabric Apps and the web, over MCP: bivariate maps, what-if projections and about 90 everyday chart types, with selection and cross-filtering already wired. It profiles your table locally; the code it writes is yours and runs with no license.",
   "keywords": [
     "mcp",
@@ -47,10 +47,10 @@
   },
   "// 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.99",
-    "@bicharts/shape-core": "^0.6.99",
+    "@bicharts/chart-host": "^0.6.103",
+    "@bicharts/shape-core": "^0.6.103",
     "@modelcontextprotocol/sdk": "^1.32.1",
-    "@types/node": "^20.0.0",
+    "@types/node": "^26.6.5",
     "@types/papaparse": "^5.3.14",
     "d3": "^7.9.0",
     "d3-hexbin": "^0.2.2",
@@ -59,7 +59,8 @@
     "esbuild": "^0.28.1",
     "happy-dom": "^20.14.5",
     "papaparse": "^5.4.1",
-    "typescript": "^5.4.0",
-    "zod": "^3.23.0"
+    "typescript": "^7.0.2",
+    "typescript5": "npm:typescript@^5.9.3",
+    "zod": "^4.6.7"
   }
 }

package/skills/bic-charts/SKILL.md

@@ -180,6 +180,12 @@ disqualifies it; leave it unset when they only asked for a chart, and the engine
 `@bicharts/chart-host` draws), `width`/`height`, and
 `reasoning_mode: "1P"` when you want the cheapest, fastest pass.
 
+**Check a named request before generating it.** When the person's request names a chart type or something
+specific (a date grain, a limit, an overlay, a column that must show), pass the same arguments to
+`check_request` first. It says, in the service's own words, which asks this data can't honor and why,
+with chart types that fit when the type itself is denied; tell the person what it denies and why rather
+than generating around it. It spends no generation credits and is metered like `list_eligible_charts`.
+
 **Settings are the user's to answer, not yours to guess.** Every `generate_chart` result carries a
 `structuredContent.settings` block: `applied` lists each setting that took effect and whose choice it
 was (`user`, `app`, `default`, `server-roll`, `from-prompt`), `askable` names the ones still open to
@@ -547,9 +553,21 @@ overwrites a file, and its reply ends with a worked example. Building notes on m
 data service is on (the notes recipe below, step a), run it again with `features: ["notes", "scenarios"]`: it writes
 those files finished.
 
+**The model's name is the `connection`.** Connect the semantic model the way the template's AGENTS.md says - before or
+after `setup_fabric_app`, whose reply names it either way. On the template's current layout the model is a Rayfin
+connector: `npx rayfin connector search "<model name>" --all-workspaces --type fabric-semanticmodel --json`, then the
+`npx rayfin connector add --type fabric-semanticmodel --name <name> --workspace-id <id> --item-id <id>` it prints (ids from
+the search, never guessed); the connector's name in `rayfin/rayfin.yml` is what `useSemanticModelQuery({ connection })`
+takes. On the template's older layout (a `fabric.yaml`, `@microsoft/fabric-app-data`) it is the model's alias in
+`fabric.yaml`. `query_semantic_model` and `suggest_charts` read it from whichever file the project has; pass `alias` only
+when the project declares more than one.
+
 **1. Pull each chart's rows at the chart's GRAIN, with a query written for that chart.** One row per
-country for a country map, one per route for a flow map, one per month for a trend. The template's
-writing-phase command is `npx fabric-app-data query <alias> --query '<DAX>'`. Don't pull a fact
+country for a country map, one per route for a flow map, one per month for a trend. The template's own
+command runs a `.dax` file through the connector: `npx fabric-app-semantic-model-tools run-dax-query --dax <file.dax>
+--alias <connector>` (on its older layout, `npx fabric-app-data query <alias> --query '<DAX>'`).
+`query_semantic_model` runs the query through that same connector and the project's own sign-in, so a query it returned
+has passed the template's check: don't run it again with `run-dax-query`. Don't pull a fact
 table and aggregate it in the browser: the Execute Queries API refuses a response over 15 MB, and a
 column repeated on every fact row (a country's population on each sale) sums to nonsense.
 
@@ -567,12 +585,14 @@ name. Pass the model's metadata as you rename: `isMeasure`, `format` and `descri
 Power BI visual gets for free. In `INFO.VIEW.COLUMNS()` a column's name is `[Name]`, not `[Column]`.
 
 **Steps 1-3 are one call: `query_semantic_model`.** Give it the chart's DAX (`dax`, or a `.dax` file) and a
-`name`; it runs the query through the project's own `fabric-app-data` CLI, renames the headers (dropping the
+`name`; it runs the query through the project's own tooling - the model's Rayfin connector (through
+`@microsoft/fabric-app-semantic-model-tools`, else the Rayfin CLI), or on the older layout the `fabric-app-data` CLI - so
+it signs in and gets the reply the app will get. It renames the headers (dropping the
 table and any symbols: `[Occupancy %]` becomes `Occupancy`), saves every row to `.bic/data/<name>.csv`,
 reads each column's role, format and description from the model (`INFO.VIEW.MEASURES()` / `INFO.VIEW.COLUMNS()`),
 and profiles the result. Its reply ends with the arguments for the next two calls - `csv_path`, `measures`,
 `dimensions`, `formats`, `descriptions` - so pass them to `list_eligible_charts` and `generate_chart` as they
-are. The CLI returns at most 1,000 rows; the tool says so when it cut a result, and the fix is a query at the
+are. It keeps at most 1,000 rows of a query; the tool says so when it cut a result, and the fix is a query at the
 chart's grain.
 
 **4. Ask before choosing, then choose what answers the question.** `list_eligible_charts` on that
@@ -590,13 +610,15 @@ without naming:
 | every place drawn at the same size, because which are high or low matters more than where | World tile-grid cartogram (or US hex-tile cartogram for states) |
 | actual against a budget, plan or target, with the gap shown for each period or unit | Variance chart (budget vs actual) |
 | that same actual-against-target comparison across many accounts or nested groups, read as a table with subtotals | Variance grid (a preview type) - it needs a category to group by; a date series alone is the Variance chart |
-| a table with one row per item and each value DRAWN (bars, dots or icons in the cells), so a reader can scan down a column | Table with embedded |
-| a table a reader sorts, hides columns in and opens a row's detail from, with plain values, chips or links | Interactive table (a preview type) |
+| a table with one row per item and each value DRAWN (bars, dots or icons in the cells), compact, for scanning down a column and nothing more | Table with embedded |
+| a table a reader WORKS with: sorts, drags column widths, copies cells out, hides columns, scrolls a wide table sideways with frozen columns or rows, opens a row's detail; plain values by default, and where the request asks, data bars, chips, icons, or one value compared with several others as bars (this week against its averages) | Interactive table (a preview type) - name the cells to draw in `prompt`; widths, sort and hidden columns are the reader's, kept through the host's view state |
 | circling a group of points to see what sets them apart from the rest | Selection explainer (a preview type) - the lasso and the comparison are drawn inside the chart; put the other fields to compare in the same table (which ones: below); on a page, give it `selects` so a circled group filters the page (step 6) |
 
 If the list doesn't offer what you expected, read its notes: it names a type refused on a count
 when your table is small, and it says when `name_filter` hid description matches.
 
+The Interactive table and the Variance grid are preview types too, so either may be missing from the list. When the person asked for one and it isn't listed, say so and ask how to go on; don't build a table by hand in its place.
+
 The Selection explainer is a preview type: the server offers it only where it's switched on, so it may be missing from the
 list even when the data fits. When `list_eligible_charts` doesn't list it for your data, tell the person it isn't available
 for this data right now, and ask how they want to go on. Don't silently draw a plain scatter in its place, and don't write the
@@ -627,7 +649,8 @@ import { BicChartPanel } from "@/components/bic-chart-panel";
 import { useBicChartOptions } from "@/lib/bic-chart-options";
 import QUERY from "@/queries/overview/occupancy-map.dax?raw";   // the template's rule: DAX lives in .dax files
 
-const result = useSemanticModelQuery({ connection: "<alias>", query: QUERY });  // the DAX it was generated on
+// connection: the model's connector name in rayfin/rayfin.yml (fabric.yaml's alias on the older layout)
+const result = useSemanticModelQuery({ connection: "<connector name>", query: QUERY });  // the DAX it was generated on
 const options = useBicChartOptions();
 const country = useBicFilter("CountryIso3", { label: "Country", display: "CountryName" });   // step 6
 <BicChartPanel result={result}>
@@ -637,6 +660,11 @@ const country = useBicFilter("CountryIso3", { label: "Country", display: "Countr
 </BicChartPanel>
 ```
 
+**A reader's view outlives the page only if you keep it.** What a reader sets inside a chart - an Interactive table's sort,
+column widths and hidden columns, a 3D camera, an expanded row - lives while the chart is mounted and is gone on reload.
+Pass `rememberAs="<a key per chart>"` to keep it in that browser, or `viewState={{ load, save }}` to keep it per signed-in
+person on your server (a plain JSON bag). Hand-hosting `BicChart`, pass the same `viewState` prop.
+
 It is rewritten with the chart on every generation, so keep app logic outside it. What it does, if you
 host by hand instead - `generate_chart` returns `binding`; pass all three:
 
@@ -719,7 +747,7 @@ import FORECAST_DAX from "@/queries/overview/bookings-forecast.dax?raw";
 const country = useBicFilter("CountryIso3", { label: "Country", display: "CountryName" });
 const route = useBicFilter(["OriginCode", "DestinationCode"],
                           { label: "Route", display: ["OriginName", "DestinationName"] });
-const forecast = useSemanticModelQuery({ connection: "<alias>",
+const forecast = useSemanticModelQuery({ connection: "<connector name>",
   query: filterQuery(FORECAST_DAX, treatAs(country, "Geography[CountryIso3]")) });
 
 <BicFilterChips />                                   {/* "Country: Japan ×" - what's filtered, and its clear */}
@@ -786,8 +814,10 @@ npx rayfin init --services auth,data --auth-methods fabric --dialect mssql --ove
 Each flag is needed: without `--overwrite` it prints "Initialization cancelled" and exits 0 with no
 reason; without `--project-name` (pass the `id:` already in `rayfin/rayfin.yml`, so nothing is renamed)
 it stops with "--project-name is required in non-interactive mode". It rewrites `rayfin/rayfin.yml`
-and `.gitignore`, so `git diff` both and put back what's yours (on 1.36.1 it dropped the template's
-`src/fabric.generated.ts` line from `.gitignore`). It writes `rayfin/tsconfig.json` - keep its
+and `.gitignore`, so `git diff` both and put back what's yours: on the template's connector layout that is the
+`connectors:` list in `rayfin/rayfin.yml` (put it back, or run the same `npx rayfin connector add` again - without it
+the app and `query_semantic_model` have no model) and the template's `.gitignore` lines; on the older layout, on 1.36.1, it
+dropped the `src/fabric.generated.ts` line. It writes `rayfin/tsconfig.json` - keep its
 `outDir`, `.temp/compiled`, which is where the deploy reads the entities from - and no entities. On 1.36.2 it
 writes no `rayfin/data/schema.ts` either: don't write one by hand - `setup_fabric_app` with `features` (step c) writes it
 when `rayfin/rayfin.yml` shows the data service on.
@@ -796,9 +826,11 @@ when `rayfin/rayfin.yml` shows the data service on.
 - `rayfin/tsconfig.json`, in `compilerOptions`: `"tsBuildInfoFile": ".temp/tsconfig.tsbuildinfo"` and
   `"allowImportingTsExtensions": false` (it inherits both from the root: TS6377 and TS5096 otherwise).
 - the root `tsconfig.json`: `"references": [{ "path": "./rayfin" }]`.
-- type the client with your schema: `RayfinClient<AppSchema>` in `src/lib/rayfin-client.ts`
-  (`import type { AppSchema } from "../../rayfin/data/schema";`) and in the constructor of
-  `src/services/rayfin-auth.service.ts` (TS2345 otherwise).
+- type the client with your schema (`import type { AppSchema } from "../../rayfin/data/schema";`): in
+  `src/lib/rayfin-client.ts`, on the connector layout, `AppSchema` in place of `EntitySchema` as the first type argument
+  of `ConnectorsRayfinClient<EntitySchema, FunctionsSchema, AppConnectorsSchema>` (the older layout's file has
+  `RayfinClient<AppSchema>`); and `RayfinClient<AppSchema>` in the constructor of `src/services/rayfin-auth.service.ts`
+  (TS2345 otherwise).
 
 Check with `npx tsc -b`; a bare `tsc --noEmit` reports TS6305 until the `rayfin/` project is built. If a
 TS2345 names two copies of `rayfin-auth`, something installed only some Rayfin packages: run
@@ -818,8 +850,9 @@ never rewrites them:
   chart's card (a card has a fixed height and `overflow-hidden`, and clips it). The reader's text is cleared only once
   the save succeeds; a failure is shown with the text kept.
 
-*d. Badges on the marks: pass `annotations`, never measure the chart.* The host draws each badge on its key's mark
-after every render and keeps it there through filters, re-queries and zooms; it never reads a row position. A route is
+*d. Badges on the marks: pass `annotations`, never measure the chart.* The host draws each badge on its key's mark (on a
+table row, just after the row's label; on a chart type that asks for it, such as a tile map, a small dot inside the
+tile's top-right corner with the `label` and `title` in its tooltip) after every render and keeps it there through filters, re-queries and zooms; it never reads a row position. A route is
 keyed by BOTH of its ends with `where` - no key column to add, no query to change and no chart to regenerate:
 
 ```tsx