@bicharts/chart-mcp 0.6.49 → 0.6.50

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bicharts/chart-mcp",
-  "version": "0.6.49",
+  "version": "0.6.50",
   "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). Requires a BIC trial or paid account.",
   "keywords": [
     "mcp",
@@ -47,8 +47,8 @@
     "zod": "^3.23.0"
   },
   "devDependencies": {
-    "@bicharts/chart-host": "^0.6.49",
-    "@bicharts/shape-core": "^0.6.49",
+    "@bicharts/chart-host": "^0.6.50",
+    "@bicharts/shape-core": "^0.6.50",
     "@types/node": "^20.0.0",
     "@types/papaparse": "^5.3.14",
     "esbuild": "^0.28.1",

package/skills/bic-charts/SKILL.md

@@ -454,6 +454,94 @@ Add `@using MyCharts.Components` to `_Imports.razor`, then on a page:
   (`@media (prefers-color-scheme: dark) { ... }` on `body` or the chart's card) and the charts follow
   on the next `change` of the media query.
 
+## 3a. A Microsoft Fabric App (the Rayfin `dataapp` template)
+
+A Fabric App built from Rayfin's `dataapp` template is a React app over a semantic model. The golden
+path above applies unchanged; these are the places a data app differs, each one measured on a real
+build.
+
+**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
+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.
+
+**2. Profile and generate from THE WHOLE RESULT of that query - every row, never a few pasted in.**
+Eligibility reads row, region and category counts. A bivariate country map needs at least 24
+countries, so the same 40-country query shown as 8 sample rows hides it, and nothing fails - you are
+simply offered other charts. Save the result to a file and pass `csv_path`, or pass all of it as
+`data`.
+
+**3. Rename the query's columns to plain names first, and keep the map.** Results come back as
+`DimCountry[CountryCode]` and `[Revenue per Capita]`. Generate on `CountryCode` and
+`RevenuePerCapita`, and apply the SAME rename to the live rows at run time - the chart reads columns by
+name. Pass the model's metadata as you rename: `isMeasure`, `format` and `description` (from
+`INFO.VIEW.MEASURES()` / `INFO.VIEW.COLUMNS()`) go on each column in `data`, which is the context a
+Power BI visual gets for free.
+
+**4. Ask before choosing, then choose what answers the question.** `list_eligible_charts` on that
+data. The catalogue goes past the template's own charts, and these are the ones people describe
+without naming:
+
+| the request sounds like | ask for |
+| --- | --- |
+| "compare A with B by country" | Bivariate World Choropleth |
+| "the shipping lanes / flows between countries" | Origin-Destination Flow Map |
+| "a projection I can steer with a growth rate, against our target" | What-if projection - the rate and horizon sliders are drawn inside the chart; there is no slider to build |
+| "how far apart the outcomes of several growth rates land" | What-if scenarios |
+
+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.
+
+**5. Render live rows through the group, with the binding the generation returned.** The template
+queries at run time (`useSemanticModelQuery`), so the payload is rebuilt from live rows every time -
+never hand-built. `generate_chart` returns `binding` (`geo`, `point`, `destination`); pass all three:
+
+```tsx
+import * as d3 from "d3";
+import { BicChart, BicChartGroup } from "@bicharts/chart-host/react";
+import code from "@/charts/country-map/chart.js?raw";
+// Saved from the generate_chart result: columns = data.columns, binding = binding, geoKind = geo.kind.
+import { columns, binding, geoKind } from "@/charts/country-map/meta";
+
+// The SAME rename the chart was generated on.
+const RENAME = { "DimCountry[CountryCode]": "CountryCode", "DimCountry[Country]": "Country",
+                 "[Revenue per Capita]": "RevenuePerCapita", "[Return Rate %]": "ReturnRate" };
+
+function CountryMap({ table, onPick }) {          // table = the live query result
+  const rows = table.rows.map(r => Object.fromEntries(
+    table.columns.map((c, i) => [RENAME[c.name] ?? c.name, r[i]])));
+  return (
+    <BicChartGroup columns={columns} rows={rows}
+                   geo={binding.geo} point={binding.point} destination={binding.destination}>
+      <BicChart id="map" code={code} d3={d3} geoKind={geoKind}
+                options={{ width, height }}
+                onSelect={idxs => onPick(idxs.length ? rows[idxs[0]].CountryCode : null)} />
+    </BicChartGroup>
+  );
+}
+```
+
+- **`columns`** can be the generation payload's columns as they are: the group drops any
+  `__rowIdx__` / `__geo*` column it is handed and builds its own from the live rows and the binding.
+- **`geoKind` comes from the result's `geo.kind`**, not from `binding.geo`: a point map has a
+  basemap but no join, so its `binding.geo` is null.
+- **`<BicChartGroup destination>` needs `@bicharts/chart-host` 0.6.50 or later.** Before it, a flow
+  map's far end is not built.
+
+**6. Cross-filter across queries by KEY, not by row.** Charts fed by different queries don't share a
+row space, so one group can't span them. Put each query's charts in their own group, turn a click
+into the model's key (`CountryCode` above), keep it in app state, and filter the other queries with
+it. Anything saved against a mark - a note, a flag - is keyed the same way, never by `__rowIdx__`
+(see the row-index hazard above).
+
+**7. A reader's choice inside a chart is view state.** A what-if chart's rate and horizon are its
+own controls, reported through `viewState` on `<BicChart>` (`uiState` / `setUiState` in the
+integration contract). To save a named scenario, store that - don't rebuild the slider beside it.
+
+**8. What stays the template's job:** sign-in, the query hooks, the app's database, `VisualContainer`
+headers, deployment (`npx rayfin up`). The chart is a function you render inside them.
+
 ## 4. Things that will otherwise cost you time
 
 - **Place names, not coordinates.** If your data has city/state/ZIP but no lat/lon, pass a