@blueprint-chart/docs 1.0.0 → 1.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blueprint-chart/docs",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "description": "Public documentation for Blueprint Chart — handbook, guide, BPC DSL spec, and lib API reference.",
   "type": "module",
   "license": "MIT",
@@ -49,8 +49,8 @@
     "vitepress": "^1.5.0",
     "vitest": "^3.2.4",
     "vue": "^3.5",
-    "@blueprint-chart/lib": "1.0.0",
-    "@blueprint-chart/ui": "1.0.0"
+    "@blueprint-chart/lib": "1.2.0",
+    "@blueprint-chart/ui": "1.2.0"
   },
   "scripts": {
     "dev": "vitepress dev src --host 0.0.0.0 --port 4445",

package/src/guide/getting-started.md

@@ -89,7 +89,7 @@ From here you wire the `data` and `options` into the renderer of your choice —
 If you don't need the programmatic API, use the bundled runtime. It picks up every `<script type="application/blueprint-chart">` tag and replaces it with a sandboxed iframe containing the rendered chart.
 
 ```html
-<script src="https://unpkg.com/@blueprint-chart/lib/dist/runtime.iife.js"></script>
+<script src="https://unpkg.com/@blueprint-chart/lib/dist/lib/lib.iife.js"></script>
 
 <script type="application/blueprint-chart">
   chart donut {

package/src/guide/mcp.md

@@ -85,6 +85,28 @@ claude mcp add blueprint-chart -- npx -y @blueprint-chart/mcp
 }
 ```
 
+```json [Windsurf]
+{
+  "mcpServers": {
+    "blueprint-chart": {
+      "command": "npx",
+      "args": ["-y", "@blueprint-chart/mcp"]
+    }
+  }
+}
+```
+
+```json [Cline]
+{
+  "mcpServers": {
+    "blueprint-chart": {
+      "command": "npx",
+      "args": ["-y", "@blueprint-chart/mcp"]
+    }
+  }
+}
+```
+
 :::
 
 Any other MCP client works too — run `npx -y @blueprint-chart/mcp` over stdio and drop it into

package/src/guide/scenes.md

@@ -194,7 +194,7 @@ that follow.
 The controller is decoupled from the nav DOM it inserts — you can ignore the built-in buttons and call `next()`, `previous()`, or `goTo(index)` from any custom UI:
 
 ```ts
-import { createSceneController } from '@blueprint-chart/lib/dist/runtime'
+import { createSceneController } from '@blueprint-chart/lib/runtime'
 
 const controller = createSceneController(container, scenes, (scene, index) => {
   renderChart(canvas, scene.data, true)
@@ -212,7 +212,7 @@ Call `controller.destroy()` to remove the injected nav when tearing the chart do
 
 ## API surface
 
-Exported from `@blueprint-chart/lib/dist/runtime`:
+Exported from `@blueprint-chart/lib/runtime`:
 
 | Symbol | One-liner |
 | --- | --- |

package/src/reference/api/index.md

@@ -232,8 +232,8 @@ Each `ChartSample` exposes:
 
 ```ts
 // Available only from the IIFE bundle (auto-initialized) or:
-import { initBlueprint, createSceneController, createStepController } from '@blueprint-chart/lib/dist/runtime'
-import type { SceneDefinition, SceneController, StepDefinition, StepController } from '@blueprint-chart/lib/dist/runtime'
+import { initBlueprint, createSceneController, createStepController } from '@blueprint-chart/lib/runtime'
+import type { SceneDefinition, SceneController, StepDefinition, StepController } from '@blueprint-chart/lib/runtime'
 ```
 
 | Symbol | Purpose |
@@ -278,13 +278,18 @@ Drop a BPC source into the page inside a typed `<script>` tag, then call `initBl
 </script>
 
 <script type="module">
-  import { initBlueprint } from '@blueprint-chart/lib/dist/runtime'
+  // Each chart renders inside a sandboxed iframe that reloads the standalone
+  // runtime bundle. In the IIFE form that URL is detected automatically; in the
+  // module form `document.currentScript` is null, so point the runtime at the
+  // IIFE bundle explicitly before calling initBlueprint().
+  globalThis.BLUEPRINT_CHART_RUNTIME_URL = 'https://unpkg.com/@blueprint-chart/lib/dist/lib/lib.iife.js'
+  import { initBlueprint } from '@blueprint-chart/lib/runtime'
   initBlueprint()
 </script>
 ```
 
 ::: info BPC source from `packages/lib/src/samples/bitcoin-price.bpc`
-The IIFE bundle (`@blueprint-chart/lib/dist/lib/lib.iife.js`) calls `initBlueprint()` for you on `DOMContentLoaded`. Import the module form when you want to control timing or re-initialize after DOM updates.
+The IIFE bundle (`@blueprint-chart/lib/dist/lib/lib.iife.js`) calls `initBlueprint()` for you on `DOMContentLoaded`. Import the module form when you want to control timing or re-initialize after DOM updates; set `globalThis.BLUEPRINT_CHART_RUNTIME_URL` to the IIFE bundle URL so each generated iframe can load the runtime.
 :::
 
 ## Versioning