@bicharts/chart-mcp 0.5.106 → 0.5.108

package/README.md

@@ -54,6 +54,7 @@ only render text); `structuredContent` is for code, so nothing has to string-par
 | `geo` / `geoPoint` | region/basemap wiring, and how many points actually placed |
 | `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
 cannot reconstruct from the source data — so a geo chart needs either it or `files.data`.
@@ -134,6 +135,7 @@ Two ways to supply them — env wins over the file:
 | `BIC_URL` | override backend (default `https://bizintelligencechampions.com`) |
 | `BIC_MCP_REASONING` | OPTIONAL override of the default reasoning mode (else `""` = leave-to-visual, same as the PBI visual) |
 | `BIC_MCP_MODEL` | OPTIONAL override of the default model (else `""` = the account's IsDefault model, same as the visual) |
+| `BIC_MCP_TIMEOUT_MS` | OPTIONAL: how long one `generate_chart` call waits, recovery included (default `900000`, 15 minutes) |
 
 **Defaults match the Power BI visual.** Unset, the MCP sends `model=""` (server
 resolves the `IsDefault` model), `reasoning_mode=""` (leave-to-visual heuristic), and
@@ -156,8 +158,13 @@ needs**:
 - Fallback for hosts that don't reset on progress: raise the host's per-tool
   timeout (Claude Code: `MCP_TOOL_TIMEOUT` in ms, set in the environment Claude
   Code itself runs in — e.g. the `env` block of `settings.json`).
-- (Planned) retrieve an already-generated result by `correlationId` so a dropped
-  connection recovers the billed code instead of re-generating.
+- **Built in:** when the response stream is cut *after* the server accepted the
+  request, the MCP does not give up or re-generate. Inside the same tool call it
+  checks for the finished chart by its `correlationId` (a fetch that can never call a
+  model), backing off between checks, until the chart arrives or the recovery window
+  or `BIC_MCP_TIMEOUT_MS` runs out, whichever is sooner. A recovered chart carries
+  `recoveredAfterMs`; when nothing arrives, the error keeps the `correlationId` to
+  quote to support.
 
 `BIC_MCP_REASONING=CP`/`1P` *would* finish faster, but that trades away visual parity
 (no validator) — prefer raising the timeout.