@bicharts/chart-mcp 0.6.11 → 0.6.12

package/README.md

@@ -50,13 +50,16 @@ only render text); `structuredContent` is for code, so nothing has to string-par
 | `code` | the `render()` source (omitted when `include_code: false`) |
 | `chartName`, `language`, `version`, `creditCost` | what was produced, and what it cost |
 | `correlationId` | the handle into the server-side log — quote it in any support request |
+| `outputHash` | the server's identity for this exact code (the same code always carries the same hash) — keep it with the chart |
 | `requiredD3Plugins` | packages the code calls, e.g. `["d3-sankey"]` — install them and pass the host **one** d3 that carries them, built with `assembleD3(d3, { ...plugins })` from `@bicharts/chart-host` (assigning onto an ES-module `d3` namespace throws), or the chart throws mid-render |
 | `geo` / `geoPoint` | region/basemap wiring, and how many points actually placed |
+| `geoPointDest` | present only for a route (an origin-destination flow map): the same count for each row's destination, which is geocoded apart from the origin |
 | `data` **or** `files` | the render payload inline, **or** the paths written — never both |
 | `hostContract`, `build` | the contract the code targets, and the bundle that served the call |
 | `recoveredAfterMs` | present only when the response stream was cut and the chart was fetched back by its correlation: milliseconds from the start of the call to delivery. `creditCost` is null then |
 
-`data` carries the appended `__geoIso__` / `__geoLat__` / `__geoLon__` columns, which a caller
+`data` carries the appended `__geoIso__` / `__geoLat__` / `__geoLon__` columns (and a route's
+`__geoLatD__` / `__geoLonD__`), which a caller
 cannot reconstruct from the source data — so a geo chart needs either it or `files.data`.
 
 ## Language & renderer