@bicharts/chart-mcp 0.6.122 → 0.6.124

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bicharts/chart-mcp",
-  "version": "0.6.122",
+  "version": "0.6.124",
   "description": "AI Data Components for Power BI, Excel, Fabric Apps and the web, over MCP: working what-if apps, interactive tables and bivariate maps first, plus 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",
@@ -51,8 +51,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.121",
-    "@bicharts/shape-core": "^0.6.121",
+    "@bicharts/chart-host": "^0.6.124",
+    "@bicharts/shape-core": "^0.6.124",
     "@modelcontextprotocol/sdk": "^1.32.1",
     "@types/node": "^26.6.5",
     "@types/papaparse": "^5.3.14",

package/skills/bic-charts/CHART-SHAPES.md

@@ -53,6 +53,7 @@ on the same picture, not a looser one.
 | Clustered heatmap | 2 categorical, 1 continuous | <=50 categories, needs 320x320 px | Plotly | Requires two variables for matrix values |
 | Connected scatterplot | 2 continuous, 6+ time points | needs 300x300 px | D3, PLOTLY | Best for the joint trajectory of two related metrics over time (e.g. units vs revenue, unemployment vs inflation) where the path shape is the insight |
 | Custom small multiples | 1 categorical, 1 continuous | <=16 categories, needs 320x240 px | D3, Matplotlib, Plotly, Seaborn | Best when comparing patterns across categories |
+| Customer segments | 1 categorical, 2 continuous | needs 294x420 px | D3 | One row per customer with days since the last order (or the last order date), a count of orders and a spend, ideally with other fields such as region or acquisition channel - at least a hundred customers |
 | Cutoff tuner | 1 continuous | needs 560x360 px | D3 | One row per case with a model score or rating and the actual yes/no outcome - churn, fraud, default, conversion - when the question is where to draw the line and what each choice costs |
 | Cycle plot | 1 continuous, 24+ time points | needs 320x280 px | D3, PLOTLY | Best for multi-year monthly/quarterly/weekly data where the question is seasonality vs trend ('is Q4 always highest, and is each Q4 growing?') |
 | Decomposition cards | 2 categorical, 1 continuous | needs 294x200 px | D3 | One measure that adds up and two or more category fields; a second measure shows each card's change |

package/skills/bic-charts/SKILL.md

@@ -624,8 +624,10 @@ column repeated on every fact row (a country's population on each sale) sums to
 
 **When the chart is about the records themselves, its grain IS the records.** A scatter of customers, a
 distribution, customer segments or a map of accounts takes one row per customer, account or order - the raw facts -
-and the engine does the shaping. For totals (revenue by region, a monthly trend) keep the chart's grain: given raw rows
-for a total, the engine reads the repeats as a spread to show, and bar, card and donut charts drop out of what fits.
+and the engine does the shaping. For totals (revenue by region, a monthly trend) the chart's grain is the simplest
+request. Raw rows work too where the list offers grains: the types that draw totals are then listed under "Fits once the
+rows are totalled", once per grain, and the person picks one (step 4). Where a list shows no such heading, raw rows for a
+total lose the bar, card and donut charts: query the chart's grain.
 Ratio measures (a growth %, an attainment %, a share) and measures from different fact tables stay as the model
 computes them: raw rows can't rebuild them.
 
@@ -779,6 +781,13 @@ without naming:
 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.
 
+**A grain is the person's choice, like the chart's form.** When the rows are finer than a type draws (raw rows where
+it wants one per category), the list offers that type under "Fits once the rows are totalled", once per grain: each row
+says how the rows are totalled first and carries a `projection` key, and a type listed twice is the same chart at two
+grains. Don't pick one yourself and don't re-query to total the rows in DAX: ask which grain they want in their own
+words ("revenue per country, or per region?"), then pass that row's name as `chart_type` and its key, copied exactly,
+as `projection`. The chart is drawn at that grain and says so.
+
 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