@eventmodelers/cli 1.0.76 → 1.0.78

package/cli.js

@@ -3535,7 +3535,6 @@ program
         headers: {
           'Content-Type': 'application/json',
           'x-token': cfg.token,
-          'x-board-id': cfg.boardId,
           'x-user-id': 'cli-set-slice-status',
           ...agentHeaders(cfg),
         },

package/lib/adapters/spec-kitty-adapter.js

@@ -51,7 +51,7 @@ async function fetchFullSliceData(cfg, contextName) {
   const agentId = cfg.agentId || process.env.EVENTMODELERS_AGENT_ID || '';
   const res = await fetch(url, {
     headers: {
-      'x-token': cfg.token, 'x-board-id': cfg.boardId, 'x-user-id': 'spec-kitty-adapter',
+      'x-token': cfg.token, 'x-user-id': 'spec-kitty-adapter',
       ...(agentId ? { 'x-agent-id': agentId } : {}),
     },
   });

package/lib/fetch.js

@@ -76,7 +76,7 @@ export async function runFetch({ cwd, kitDir, cfg, opts = {} }) {
   // sending it everywhere keeps one rule instead of a per-call judgment about which calls count.
   const agentId = cfg.agentId || process.env.EVENTMODELERS_AGENT_ID || '';
   const headers = {
-    'x-token': cfg.token, 'x-board-id': cfg.boardId, 'x-user-id': 'cli-fetch',
+    'x-token': cfg.token, 'x-user-id': 'cli-fetch',
     ...(agentId ? { 'x-agent-id': agentId } : {}),
   };
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "1.0.76",
+  "version": "1.0.78",
   "description": "Eventmodelers CLI — real-time Claude agent + skills for Claude Code, for any stack (Node, Supabase, Axon, OpenCQRS, UmaDB, Kurrent, or modeling-only)",
   "type": "module",
   "bin": {

package/shared/build-kit/lib/ralph.js

@@ -181,7 +181,7 @@ function slugify(str) {
 async function fetchAndPersistSlices(cfg, kitDir) {
   const url = `${cfg.baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/slicedata/slices`;
   const { slices } = await fetchJSON(url, {
-    headers: { 'x-token': cfg.token, 'x-board-id': cfg.boardId, ...agentHeaders(cfg) },
+    headers: { 'x-token': cfg.token, ...agentHeaders(cfg) },
   });
   const slicesDir = join(kitDir, '.slices');
   mkdirSync(slicesDir, { recursive: true });
@@ -498,7 +498,7 @@ async function blockStuckSlice(kitDir, cfg, credentialed, planned, attempts) {
     try {
       await fetchJSON(`${cfg.baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/nodes/events`, {
         method: 'POST',
-        headers: { 'Content-Type': 'application/json', 'x-token': cfg.token, 'x-board-id': cfg.boardId, 'x-user-id': 'ralph-loop', ...agentHeaders(cfg) },
+        headers: { 'Content-Type': 'application/json', 'x-token': cfg.token, 'x-user-id': 'ralph-loop', ...agentHeaders(cfg) },
         body: JSON.stringify([{
           id: randomUUID(),
           eventType: 'node:changed',

package/shared/skills/connect/SKILL.md

@@ -22,7 +22,7 @@ After running, the following variables are available for the rest of the session
 | Variable | Header sent to API | Description |
 |----------|--------------------|-------------|
 | `TOKEN` | `x-token` | API token UUID |
-| `BOARD_ID` | `x-board-id` | Target board UUID |
+| `BOARD_ID` | — | Target board UUID (used in all board-scoped URLs) |
 | `ORG_ID` | — | Organization UUID (used in all board-scoped URLs) |
 | `BASE_URL` | — | Base URL, e.g. `http://localhost:3000` |
 | `AGENT_ID` | `x-agent-id` | This agent process's own id, when running as one (Step 0.5). Optional — skip the header when there is no value. |
@@ -30,7 +30,6 @@ After running, the following variables are available for the rest of the session
 Every curl-fallback call in every skill must include these headers:
 ```
 x-token: <TOKEN>
-x-board-id: <BOARD_ID>
 x-user-id: <skill-name>   ← set by each skill individually
 x-agent-id: <AGENT_ID>    ← only when AGENT_ID resolved; omit the line entirely otherwise
 ```
@@ -243,7 +242,6 @@ Otherwise (no MCP tools visible yet this session), fall back to the equivalent c
 ```bash
 curl -s -o /dev/null -w "%{http_code}" \
   -H "x-token: <TOKEN>" \
-  -H "x-board-id: <BOARD_ID>" \
   -H "x-user-id: connect-skill" \
   "<BASE_URL>/api/org/<ORG_ID>/boards/<BOARD_ID>/nodes?type=CHAPTER"
 ```

package/shared/skills/learn-eventmodelers-api/SKILL.md

@@ -9,7 +9,7 @@ You now have complete knowledge of the eventmodelers platform API. This is a ref
 
 **Load this once per session, on demand — not as a mandatory preamble.** Every other skill already documents the exact API calls it needs inline; none of them require this full reference to be loaded before they can run. Reach for this skill only when you hit a specific endpoint, field, or element type that a skill's own instructions don't cover, and don't reload it again later in the same session once you have.
 
-**Two transports exist for board operations: MCP tools (preferred) and raw REST/curl (fallback).** The `connect` skill registers the MCP server in `.mcp.json`. Once `mcp__eventmodelers__*` tools are visible in your tool list, use them — they need no `x-token`/`x-board-id`/`x-user-id` headers (auth and org resolution happen server-side from the registered token) and return the same data as the REST endpoints below. Fall back to the numbered REST sections only when MCP tools aren't connected yet, or for the handful of endpoints (prompts lifecycle, snapshots, user management, board/extension CRUD) the MCP server intentionally doesn't expose — it only covers board-content operations (nodes, timelines, slices, comments, screens). This preference is about *which transport a skill's own instructions should use*, never about whether to invoke the skill in the first place.
+**Two transports exist for board operations: MCP tools (preferred) and raw REST/curl (fallback).** The `connect` skill registers the MCP server in `.mcp.json`. Once `mcp__eventmodelers__*` tools are visible in your tool list, use them — they need no `x-token`/`x-user-id` headers (auth and org resolution happen server-side from the registered token) and return the same data as the REST endpoints below. Fall back to the numbered REST sections only when MCP tools aren't connected yet, or for the handful of endpoints (prompts lifecycle, snapshots, user management, board/extension CRUD) the MCP server intentionally doesn't expose — it only covers board-content operations (nodes, timelines, slices, comments, screens). This preference is about *which transport a skill's own instructions should use*, never about whether to invoke the skill in the first place.
 
 ---
 
@@ -25,7 +25,7 @@ Server name: `eventmodelers`. Every tool takes `boardId` explicitly; none need `
 | `get_node_comments` | `boardId`, `nodeId` | List comments on a node | §1 `GET .../nodes/:nodeId/comments` |
 | `get_board_events` | `boardId` | All board events, in sequence | §1 `GET .../events` |
 | `search_board_events` | `boardId`, `name` | Search events by node name | §1 `GET .../events/search` |
-| `submit_node_events` | `boardId`, `events[]`, `autoConnect?`, `compact?` | Create/update nodes (raw `NodeChangeEvent`/edge events). `autoConnect: false` places freshly-created nodes without wiring them to their own/previous-column neighbors (avoids a stray nearest-left edge); `compact: true` returns `{persisted: <count>}` instead of the per-node hash map | §3 `POST .../nodes/events` |
+| `submit_node_events` | `boardId`, `events[]`, `autoConnect?`, `compact?` | Create/update nodes (raw `NodeChangeEvent`/edge events). Every event property is described on the tool's own `events[]` schema — read that rather than this skill when all you need is the event shape. `autoConnect: false` places freshly-created nodes without wiring them to their own/previous-column neighbors (avoids a stray nearest-left edge); `compact: true` returns `{persisted: <count>}` instead of the per-node hash map | §3 `POST .../nodes/events` |
 | `delete_node` | `boardId`, `nodeId` | Delete a node. Deleting a chapter (timeline) cascades — every node placed in one of its cells, plus any node parented to it (e.g. SLICE_BORDER), is deleted too, along with all their edges | (via `node:deleted` event, §3) |
 | `create_drawing` / `create_drawings` | `boardId`, `kind`, `x`, `y`, `width`, `height`, ... (plural: `drawings[]`) | Freehand canvas annotation (path/rect/text/sticky) — never placed in a cell. Use the plural form whenever an annotation is more than one stroke (a loop plus its arrows and label is one annotation, not three calls) | — (REST `POST .../drawing/draw` accepts a single drawing or an array) |
 | `find_nodes_in_drawing` | `boardId`, `drawingId` | Nodes fully contained inside a drawing's bounding box | — (no REST equivalent; MCP-only) |
@@ -44,6 +44,7 @@ Server name: `eventmodelers`. Every tool takes `boardId` explicitly; none need `
 | `create_slice_definition` | `boardId`, `timelineId`, `columnId`, `title`, `status?`, `data?`, `meta?` | Create a SLICE_BORDER over an existing column. `status` sets its `sliceStatus` straight away instead of a follow-up `update_slice_status` | §5 `POST .../slice-definitions` |
 | `place_element` / `place_elements` | `boardId`, `timelineId`, `elementType`, `title`, `fields?`, `lane?`, `columnIndex?`, `compact?`, `autoConnect?` (plural: `elements[]`) | Find/create an empty cell in the right lane and place a COMMAND/READMODEL/EVENT. `fields` writes the element's attributes in the same call — don't follow a placement with a `submit_node_events` just to set them. The plural form places a whole slice's or column run's worth in one call, applied in order so each entry sees the columns the previous one added. `autoConnect: false` places without wiring to timeline neighbors — wire the edges yourself | — (MCP-only convenience; composes §2+§3) |
 | `list_slices` | `boardId` | List slices (id, title, status) | §8 `GET .../slicedata/slices` |
+| `get_slice_rework` | `boardId`, `contextId` | How much each slice of one context has been reworked: changes, steps backwards, and reopens after Done, most reworked first, plus planning metrics over them. `contextId` is a MODEL_CONTEXT or a timeline (a timeline resolves to the context it belongs to). Always per context — there is no board-wide form | §8 `GET .../reporting/rework/contexts/:contextId` |
 | `update_slice_status` | `boardId`, `newStatus`, plus exactly one of `sliceId` / `sliceTitle` / `columnId` | Change a SLICE_BORDER's `sliceStatus`. With a title or column id there is no need to call `list_slices` first; an ambiguous title comes back with its candidates. A slice being created takes its status from `create_slice`/`create_slice_definition` instead | — (via `node:changed` event, §3) |
 | `get_slice_data` | `boardId`, `contextName?`, `contextId?`, `sliceId?` | Full element graph for slices in a context | §8 `GET /slicedata` |
 | `get_spec_info` | `boardId`, `timelineId`, `elementTypes?` | EVENT/COMMAND/READMODEL nodes valid in GWT steps. Pass `elementTypes` (subset of `EVENT`/`COMMAND`/`READMODEL`) to avoid pulling the full element list when only one or two types are needed — filtered server-side, not just after a full fetch | §6 `GET .../spec-info` |
@@ -57,7 +58,7 @@ Server name: `eventmodelers`. Every tool takes `boardId` explicitly; none need `
 | `link_element` | `boardId`, `nodeId`, plus either `targetNodeId` or `timelineId` (+ `columnIndex?`, `lane?`) | Turn a node into a linked copy of `nodeId` — it receives a full copy of that node's meta plus `meta.linkedTo`. Name an existing `targetNodeId`, or pass `timelineId` to have the copy placed and linked in this one call (inheriting the original's type and title), which is what a translation or automation chain wants | §3 `POST .../nodes/:nodeId/link` |
 | `add_comment` / `add_comments` | `boardId`, `nodeId`, `text`, `type?` (`'COMMENT'\|'TASK'\|'QUESTION'`), `author?` (plural: `comments[]`, each with its own `nodeId`) | Add a comment — `QUESTION` is the type for a gap/edge case raised during review. Use the plural form for a review that has a question per element: all of them go in one call | §1 `POST .../boards/:boardId/comments` (batch) |
 | `update_comment` | `boardId`, `nodeId`, `commentId`, `action` (`'resolve'\|'delete'`) | Resolve or delete a comment | — (via comment events) |
-| `create_screen` | `boardId`, `contentType` (`'image'\|'sketch'\|'html'`), `nodeId?`, `chapterId`, `cellId?`/`cellName?`, plus content fields (`imageBase64`/`mimeType`, `elements[]`, or `pages[]`/`backgroundColor`), `description?`, `fields?`, `autoConnect?` | Create + place a new screen node (SCREEN or HTML_SCREEN) atomically, in one call. Batch form `create_screens` takes `screens[]` (HTML only) + `autoConnect?`. `autoConnect: false` places without wiring to timeline neighbors | §4 `POST .../images/:id/sketch` + `image-nodes` |
+| `create_screen` | `boardId`, `contentType` (`'image'\|'sketch'\|'html'`), `nodeId?`, `chapterId`, `cellId?`/`cellName?`, plus content fields (`imageBase64`/`mimeType`, `elements[]`, or `pages[]`/`backgroundColor`), `title?`, `description?`, `fields?`, `autoConnect?` | Create + place a new screen node (SCREEN or HTML_SCREEN) atomically, in one call. `title` names the node (`meta.title`) in the same call — no follow-up `node:changed` just to label the screen; `create_screens` takes it per entry. Batch form `create_screens` takes `screens[]` (HTML only) + `autoConnect?`. `autoConnect: false` places without wiring to timeline neighbors | §4 `POST .../images/:id/sketch` + `image-nodes` |
 | `render_screen` | `boardId`, `nodeId`, `elements[]?` (SCREEN) or `pages[]?`+`backgroundColor?` (HTML_SCREEN), `description?` | Update an existing screen's content — exactly one of `elements`/`pages` | §4 `POST .../images/:id/sketch` + `image-nodes` |
 | `add_field_examples` | `boardId`, `nodeId?`, `name?`, `cellName?`, `timelineId?` | Fill empty field examples using linked-node context | — (MCP-only convenience) |
 | `get_attribute_chain` | `boardId`, `timelineId`, `targetCellName`, `sourceCellName` | Resolve every node between two cells, ordered target→source | — (MCP-only convenience) |
@@ -514,7 +515,7 @@ Update an image snapshot.
 ### POST `/api/org/:orgId/boards/:boardId/image-nodes/:nodeId`
 Create an image node.
 
-**Request**: `multipart/form-data` — fields: `file`, `chapterId`, `cellName`  
+**Request**: `multipart/form-data` — fields: `file`, `chapterId`, `cellName`, `title?` (label shown on the node, `meta.title`)  
 **Response**: `204`
 
 ---
@@ -543,6 +544,7 @@ Create a SCREEN node from a sketch description.
   cellName: string
   description: { elements: object[] }
   semanticDescription?: string
+  title?: string               // label shown on the node (meta.title)
 }
 ```
 **Response**: `204` OR `400` (validation error)
@@ -730,6 +732,30 @@ List all slices on a board.
 
 ---
 
+### GET `/api/org/:orgId/boards/:boardId/reporting/rework/contexts/:contextId`
+**File**: `src/slices/change/reporting/rework/routes.ts`
+
+How much each slice of one context has been reworked — read-only, derived from the board event log; nothing is stored
+for it.
+
+A slice's rework is read from its own SLICE_BORDER history. Going backwards means a step down the progress order
+(Created → Planned → Assigned → InProgress → Review → Done), or reaching `Blocked` from `Review`/`Done`;
+`Informational` is never scored. `reopens` counts transitions leading away from `Done`, `changes` counts writes to the
+slice itself. This says nothing about edits to the elements inside a slice.
+
+`contextId` is a MODEL_CONTEXT node id, or a timeline id — a timeline resolves through the board's own effective
+context (the same rule `slicedata` uses), so one that inherits a context is reported under that context and one with
+none is its own. Any other node type is rejected. Always scoped to one context; there is no board-wide form.
+
+**Response**: `200` — `{ contextId, contextName, metrics, slices[] }`, slices most reworked first.
+`slices[]` = `{ sliceId, title, status, changes, reopens, regressions, everReachedDone }`.
+`metrics` = `{ slices, everReachedDone, reopenedAfterDone, firstTimeRightRate, currentlyReopened, avgReopensPerSlice,
+avgChangesPerSlice }` — `firstTimeRightRate` is the share of the slices that reached Done and never came back, or
+`null` when none got there yet.
+`400` `CONTEXT_ID_REQUIRED` / `CONTEXT_NODE_INVALID` · `404` `CONTEXT_NOT_FOUND`
+
+---
+
 ## 9. Extensions
 
 **File**: `src/slices/extensions/routes.ts`
@@ -970,7 +996,7 @@ The same `agent_id` belongs in the `x-agent-id` header of every board call this
 ---
 
 ### GET `/api/org/:orgId/boards/:boardId/agent-alive`
-Check whether an agent has pinged for a board within the last 45s. Auth: `x-token` (bot) or a Supabase JWT (`Authorization: Bearer`) — either works.
+Check whether an agent has pinged for a board within the last 45s. Auth: Supabase JWT (`Authorization: Bearer`) — same as the heartbeat above; a raw `x-token` alone is not accepted here either.
 
 **Response**: `200` — `{ alive: boolean, agentTypes: string[], agents: { agentId: string, agentType: string, agentName: string | null }[] }` — one `agents` entry per live agent process, `agentTypes` the de-duplicated set of their types
 

package/shared/skills/load-slice/SKILL.md

@@ -43,7 +43,6 @@ mcp__eventmodelers__get_slice_data { "boardId": "<BOARD_ID>", "contextName": "<n
 ```bash
 curl -s \
   -H "x-token: <TOKEN>" \
-  -H "x-board-id: <BOARD_ID>" \
   -H "x-user-id: load-slice-skill" \
   "<BASE_URL>/api/org/<ORG_ID>/boards/<BOARD_ID>/slicedata/slices"
 ```

package/shared/skills/request-feedback/SKILL.md

@@ -72,7 +72,6 @@ mcp__eventmodelers__list_slices { "boardId": "<BOARD_ID>" }
 ```bash
 curl -s \
   -H "x-token: <TOKEN>" \
-  -H "x-board-id: <BOARD_ID>" \
   -H "x-user-id: request-feedback-skill" \
   "<BASE_URL>/api/org/<ORG_ID>/boards/<BOARD_ID>/slicedata/slices"
 ```
@@ -124,7 +123,6 @@ SLICE_BORDER node's meta directly:
 curl -s -X POST "<BASE_URL>/api/org/<ORG_ID>/boards/<BOARD_ID>/nodes/events" \
   -H "Content-Type: application/json" \
   -H "x-token: <TOKEN>" \
-  -H "x-board-id: <BOARD_ID>" \
   -H "x-user-id: request-feedback-skill" \
   -d '[{
     "id": "<new-random-uuid>",

package/shared/skills/update-slice-status/SKILL.md

@@ -48,7 +48,6 @@ mcp__eventmodelers__list_slices { "boardId": "<BOARD_ID>" }
 ```bash
 curl -s \
   -H "x-token: <TOKEN>" \
-  -H "x-board-id: <BOARD_ID>" \
   -H "x-user-id: update-slice-status-skill" \
   "<BASE_URL>/api/org/<ORG_ID>/boards/<BOARD_ID>/slicedata/slices"
 ```
@@ -85,7 +84,6 @@ A slice that is being *created* takes its status straight from `create_slice`/`c
 curl -s -X POST "<BASE_URL>/api/org/<ORG_ID>/boards/<BOARD_ID>/nodes/events" \
   -H "Content-Type: application/json" \
   -H "x-token: <TOKEN>" \
-  -H "x-board-id: <BOARD_ID>" \
   -H "x-user-id: update-slice-status-skill" \
   -d '[{
     "id": "<new-random-uuid>",

package/stacks/modeling-kit/templates/.claude/skills/analyze-existing-model/references/api-fallback.md

@@ -7,7 +7,6 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 ```bash
 curl -s \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: analyze-existing-model" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/slicedata/slices"
 ```
@@ -19,7 +18,6 @@ Response: `{ "slices": [{ "id": "<uuid>", "title": "<name>", "status": "<status>
 ```bash
 curl -s \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: analyze-existing-model" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=MODEL_CONTEXT"
 ```
@@ -29,7 +27,6 @@ curl -s \
 ```bash
 curl -s \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: analyze-existing-model" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/slicedata?contextName=<CONTEXT_NAME>"
 ```
@@ -46,21 +43,18 @@ Each response contains a `slices` array. Each slice entry includes:
 # 1. List slices
 curl -s \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: analyze-existing-model" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/slicedata/slices"
 
 # 2. Fetch MODEL_CONTEXT nodes
 curl -s \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: analyze-existing-model" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=MODEL_CONTEXT"
 
 # 3. Fetch full slice data for a context
 curl -s \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: analyze-existing-model" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/slicedata?contextName=Ordering"
 ```

package/stacks/modeling-kit/templates/.claude/skills/attributes/references/api-fallback.md

@@ -6,7 +6,7 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 
 ```bash
 curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$EDGE_SOURCE_ID" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: attributes-skill"
+  -H "x-token: $TOKEN" -H "x-user-id: attributes-skill"
 ```
 
 ## Step 4 — Apply the Change to Each Node in the Chain
@@ -33,7 +33,6 @@ EOF
 curl -s -w "\n%{http_code}" -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
   -H "Content-Type: application/json" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: attributes-skill" \
   --data-binary @/tmp/attributes_payload.json
 ```

package/stacks/modeling-kit/templates/.claude/skills/discover-storyboard/SKILL.md

@@ -309,6 +309,7 @@ mcp__eventmodelers__create_screen {
   "nodeId": "<SCREEN_NODE_ID>",
   "chapterId": "<CHAPTER_ID>",
   "cellId": "<CELL_ID>",
+  "title": "<screen.title>",
   "pages": ["<reconstructed HTML fragment for this screen>"],
   "description": "<screen.description — 'Shows X. Arrived via: Y. Actions: user can do A, user can do B.'>"
 }
@@ -325,6 +326,7 @@ mcp__eventmodelers__create_screen {
   "nodeId": "<SCREEN_NODE_ID>",
   "chapterId": "<CHAPTER_ID>",
   "cellName": "<CELL_NAME>",
+  "title": "<screen.title>",
   "imageBase64": "<base64-encoded contents of screen.filepath, no data: URI prefix>",
   "mimeType": "image/png",
   "description": "<screen.description — 'Shows X. Arrived via: Y. Actions: user can do A, user can do B.'>"

package/stacks/modeling-kit/templates/.claude/skills/discover-storyboard/references/api-fallback.md

@@ -16,7 +16,6 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/chapters" \
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: discover-storyboard" \
   -H "Content-Type: application/json" \
   -d '[{
@@ -43,7 +42,6 @@ curl -s -H "x-token: $TOKEN" \
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$CHAPTER_ID/columns" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: discover-storyboard" \
   -H "Content-Type: application/json" \
   -d '{}'
@@ -58,6 +56,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/image-nodes/$SCREEN_
   -H "x-token: $TOKEN" \
   -F "file=@<screen.filepath>" \
   -F "chapterId=$CHAPTER_ID" \
-  -F "cellName=$CELL_NAME"
+  -F "cellName=$CELL_NAME" \
+  -F "title=<screen.title>"
 ```
 For the HTML path with no MCP, use the `html-screen-nodes` endpoint per the `html-screen` skill's fallback mechanics instead.

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-brainstorming-events/references/api-fallback.md

@@ -5,14 +5,14 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 ## Board Context — Check existing EVENT nodes
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=EVENT"
 ```
 
 ## Board Context — Check existing CHAPTER nodes
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=CHAPTER"
 ```
 
@@ -20,7 +20,7 @@ curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/chapters" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+  -H "x-token: $TOKEN" \
   -H "Content-Type: application/json" -d '{}'
 # → { timelineId: "<chapterId>", ... }
 ```
@@ -29,7 +29,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/chapters" \
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+  -H "x-token: $TOKEN" \
   -H "x-user-id: brainstorming-events" -H "Content-Type: application/json" \
   -d '[{
     "id": "<uuid>",
@@ -45,7 +45,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
 
 ```bash
 curl -s -X PUT "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$TL/position" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+  -H "x-token: $TOKEN" \
   -H "Content-Type: application/json" \
   -d '{"x": 0, "y": 1200}'   # first chapter: y=0, second: y=1200, third: y=2400, …
 ```
@@ -56,7 +56,7 @@ No batch form exists over REST; one call per event:
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$CHAPTER_ID/columns" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: brainstorming-events" \
+  -H "x-token: $TOKEN" -H "x-user-id: brainstorming-events" \
   -H "Content-Type: application/json" -d '{}'
 # → { "columnId": "<colUuid>", "index": <n>, "totalColumns": <n> }
 ```
@@ -64,7 +64,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$CHAPTER_I
 ## Mode A — Step B: Fetch the chapter to find the swimlane row ID
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$CHAPTER_ID"
 # → node.meta.timelineData.rows — find the row where type === "swimlane"
 ```

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-checking-completeness/references/api-fallback.md

@@ -6,17 +6,17 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 
 ```bash
 # All nodes (events, commands, read models, screens)
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=EVENT"
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=COMMAND"
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=READMODEL"
 ```
 
 ## 4. Check Slice Coverage
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=SLICE_BORDER"
 ```

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-designing-automation-chains/references/api-fallback.md

@@ -10,7 +10,7 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 4. Create the node:
    ```bash
    curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-     -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: designing-automation-chains" \
+     -H "x-token: $TOKEN" -H "x-user-id: designing-automation-chains" \
      -H "Content-Type: application/json" \
      -d '[{
        "id":"<event-uuid>","eventType":"node:created","nodeId":"<node-uuid>",

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-identifying-inputs/references/api-fallback.md

@@ -6,14 +6,14 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 
 **Step A — Find the event's column ID.** Query the event node to read its current cell:
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$EVENT_NODE_ID"
 # → node.meta.cellId is "<someRowId>-<columnId>" — extract the columnId part
 ```
 
 **Step B — Fetch the chapter to find the interaction row ID:**
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$CHAPTER_ID"
 # → timelineData.rows — find the row where type === "interaction"
 ```
@@ -28,7 +28,7 @@ cellId = interactionRow.id + "-" + columnId
 
 ```bash
 curl -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: identifying-inputs" \
+  -H "x-token: $TOKEN" -H "x-user-id: identifying-inputs" \
   -H "Content-Type: application/json" \
   -d '[{
     "id": "<event-uuid>",
@@ -54,12 +54,12 @@ curl -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
 
 ```bash
 curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?cellId=<actorRowId>-<columnId>" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: eventmodeling-identifying-inputs"
+  -H "x-token: $TOKEN" -H "x-user-id: eventmodeling-identifying-inputs"
 ```
 If a SCREEN node exists, connect it:
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/connections" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: eventmodeling-identifying-inputs" \
+  -H "x-token: $TOKEN" -H "x-user-id: eventmodeling-identifying-inputs" \
   -H "Content-Type: application/json" \
   -d '{"source":"<screenNodeId>","target":"<commandNodeId>"}'
 ```
@@ -68,12 +68,12 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/connections" \
 
 ```bash
 curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?cellId=<swimlaneRowId>-<columnId>" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: eventmodeling-identifying-inputs"
+  -H "x-token: $TOKEN" -H "x-user-id: eventmodeling-identifying-inputs"
 ```
 Connect command to its resulting event:
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/connections" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: eventmodeling-identifying-inputs" \
+  -H "x-token: $TOKEN" -H "x-user-id: eventmodeling-identifying-inputs" \
   -H "Content-Type: application/json" \
   -d '{"source":"<commandNodeId>","target":"<eventNodeId>"}'
 ```

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-identifying-outputs/references/api-fallback.md

@@ -6,21 +6,21 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 
 1. Find the column where the consumer SCREEN or AUTOMATION lives. For an AUTOMATION, the read model's target column is always the one immediately **before** it (skip straight to inserting that column — its interaction row is guaranteed occupied by the automation's own COMMAND). For a SCREEN, target the screen's own column. Fetch the timeline to get the interaction row ID:
    ```bash
-   curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+   curl -s -H "x-token: $TOKEN" \
      "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$CHAPTER_ID"
    # → timelineData.rows — find the row where type === "interaction"
    ```
 2. Check if the target interaction cell is already occupied (existing COMMAND):
    ```bash
    curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?cellId=<interactionRowId>-<columnId>" \
-     -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID"
+     -H "x-token: $TOKEN"
    ```
    If a COMMAND occupies that cell, insert a new column immediately **before** it (`{"index": currentIndex}` — this shifts the consumer's column, and everything after it, one to the right) and use that new column's ID instead. The read model must end up upstream of (to the left of) its consumer, never downstream of it.
 3. `cellId = interactionRow.id + "-" + columnId`
 4. Create the READMODEL:
    ```bash
    curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-     -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: identifying-outputs" \
+     -H "x-token: $TOKEN" -H "x-user-id: identifying-outputs" \
      -H "Content-Type: application/json" \
      -d '[{
        "id": "<event-uuid>",
@@ -38,12 +38,12 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 
 ```bash
 curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?cellId=<swimlaneRowId>-<columnId>" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: eventmodeling-identifying-outputs"
+  -H "x-token: $TOKEN" -H "x-user-id: eventmodeling-identifying-outputs"
 ```
 Connect it:
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/connections" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: eventmodeling-identifying-outputs" \
+  -H "x-token: $TOKEN" -H "x-user-id: eventmodeling-identifying-outputs" \
   -H "Content-Type: application/json" \
   -d '{"source":"<eventNodeId>","target":"<readmodelNodeId>"}'
 ```
@@ -52,7 +52,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/connections" \
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/connections" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: eventmodeling-identifying-outputs" \
+  -H "x-token: $TOKEN" -H "x-user-id: eventmodeling-identifying-outputs" \
   -H "Content-Type: application/json" \
   -d '{"source":"<readmodelNodeId>","target":"<screenNodeId>"}'
 ```
@@ -61,7 +61,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/connections" \
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/connections" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: eventmodeling-identifying-outputs" \
+  -H "x-token: $TOKEN" -H "x-user-id: eventmodeling-identifying-outputs" \
   -H "Content-Type: application/json" \
   -d '{"source":"<readmodelNodeId>","target":"<automationNodeId>"}'
 ```

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-orchestrating-event-modeling/references/api-fallback.md

@@ -6,7 +6,7 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 
 ```bash
 for TYPE in EVENT COMMAND READMODEL SCREEN AUTOMATION; do
-  curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+  curl -s -H "x-token: $TOKEN" \
     "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=$TYPE"
 done
 ```
@@ -15,7 +15,7 @@ done
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: orchestrator" \
+  -H "x-token: $TOKEN" -H "x-user-id: orchestrator" \
   -H "Content-Type: application/json" \
   -d '[{"id":"<uuid>","eventType":"node:changed","nodeId":"<nodeId>","boardId":"<BOARD_ID>",
         "timestamp":1234567890,"chapterId":"<chapterId>","cellId":"<rowId>-<colId>",
@@ -26,14 +26,14 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
 
 ```bash
 curl -s -X DELETE "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/<nodeId>" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID"
+  -H "x-token: $TOKEN"
 ```
 
 ## Step 11 — Document Reasoning — Add a feedback lane
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$CHAPTER_ID/lanes" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: orchestrator" \
+  -H "x-token: $TOKEN" -H "x-user-id: orchestrator" \
   -H "Content-Type: application/json" \
   -d '{"type":"feedback","label":"Notes"}'
 # → { laneId, type, label, index, totalLanes }
@@ -43,7 +43,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$CHAPTER_I
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: orchestrator" \
+  -H "x-token: $TOKEN" -H "x-user-id: orchestrator" \
   -H "Content-Type: application/json" \
   -d '[{"id":"<event-uuid>","eventType":"node:created","nodeId":"<node-uuid>","boardId":"<BOARD_ID>",
         "timestamp":1234567890,"chapterId":"<CHAPTER_ID>","cellId":"<feedbackLaneId>-<firstColumnId>",

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-plotting-events/references/api-fallback.md

@@ -5,6 +5,6 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 ## Chapters and Timelines — Resolve the Target Timeline
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=CHAPTER"
 ```

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-storyboarding-events/references/api-fallback.md

@@ -5,16 +5,16 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 ## Board Integration — Check existing screen nodes
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=HTML_SCREEN"
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=SCREEN"
 ```
 
 ## Resolve One Actor Lane Per Human Role — Step 1: Fetch the chapter's actor rows
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$CHAPTER_ID"
 ```
 
@@ -22,7 +22,7 @@ curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$CHAPTER_ID/lanes" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: storyboarding-events" \
+  -H "x-token: $TOKEN" -H "x-user-id: storyboarding-events" \
   -H "Content-Type: application/json" \
   -d '{"type": "actor", "label": "<Role Name>"}'
 ```
@@ -31,11 +31,12 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$CHAPTER_I
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/html-screen-nodes/<node-uuid>" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: storyboarding-events" \
+  -H "x-token: $TOKEN" -H "x-user-id: storyboarding-events" \
   -H "Content-Type: application/json" \
   -d '{
     "chapterId": "<CHAPTER_ID>",
     "cellId": "<actorRowId>-<columnId>",
+    "title": "<Screen Title>",
     "pages": ["<div>...</div>"]
   }'
 ```
@@ -45,7 +46,7 @@ Then, over REST only (no `fields` param on the HTML-screen endpoint), still set
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: storyboarding-events" \
+  -H "x-token: $TOKEN" -H "x-user-id: storyboarding-events" \
   -H "Content-Type: application/json" \
   -d '[{
     "id": "<event-uuid>",
@@ -63,7 +64,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/images/$NODE_ID/sketch" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: storyboarding-events" \
+  -H "x-token: $TOKEN" -H "x-user-id: storyboarding-events" \
   -H "Content-Type: application/json" \
   -d '{
     "description": "<concise description of what this screen shows>",

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-validating-event-models/references/api-fallback.md

@@ -5,10 +5,10 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 ## Board Context
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=EVENT"
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=COMMAND"
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=READMODEL"
 ```

package/stacks/modeling-kit/templates/.claude/skills/eventmodeling-validating-event-models-checklist/references/api-fallback.md

@@ -5,10 +5,10 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 ## Board Context
 
 ```bash
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=EVENT"
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=COMMAND"
-curl -s -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+curl -s -H "x-token: $TOKEN" \
   "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes?type=READMODEL"
 ```

package/stacks/modeling-kit/templates/.claude/skills/examples/references/api-fallback.md

@@ -112,7 +112,6 @@ EOF
 curl -s -w "\n%{http_code}" -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
   -H "Content-Type: application/json" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: examples-skill" \
   --data-binary @/tmp/examples_payload.json
 ```

package/stacks/modeling-kit/templates/.claude/skills/handle-comment/references/api-fallback.md

@@ -6,7 +6,7 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$NODE_ID/comments" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" \
+  -H "x-token: $TOKEN" \
   -H "Content-Type: application/json" \
   -d '{"text":"<text>","type":"<type>","author":"<author>"}'
 ```
@@ -17,19 +17,19 @@ Response: `201 {"id":"<commentId>"}`
 
 ```bash
 curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$NODE_ID/comments" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID"
+  -H "x-token: $TOKEN"
 ```
 
 ## Action: resolve — Step B (resolve)
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$NODE_ID/comments/$COMMENT_ID/resolve" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID"
+  -H "x-token: $TOKEN"
 ```
 
 ## Action: delete — Step C (delete)
 
 ```bash
 curl -s -X DELETE "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$NODE_ID/comments/$COMMENT_ID" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID"
+  -H "x-token: $TOKEN"
 ```

package/stacks/modeling-kit/templates/.claude/skills/html-screen/references/api-fallback.md

@@ -7,7 +7,6 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 ```bash
 curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$NODE_ID" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent"
 ```
 
@@ -16,7 +15,6 @@ curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/$NODE_ID" \
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/html-screens/$NODE_ID" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '{"pages": ["<div>...</div>", "<div>...</div>"]}'
@@ -28,17 +26,16 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/html-screens/$NODE_I
 NODE_ID=$(uuidgen)
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/html-screen-nodes/$NODE_ID" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
-  -d '{"chapterId": "'"$CHAPTER_ID"'", "cellName": "'"$CELL_NAME"'", "pages": ["<div>...</div>"]}'
+  -d '{"chapterId": "'"$CHAPTER_ID"'", "cellName": "'"$CELL_NAME"'", "title": "<Screen Title>", "pages": ["<div>...</div>"]}'
 ```
 
 ## Step 5 — Define field data lineage
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: agent" \
+  -H "x-token: $TOKEN" -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '[{
     "id": "<event-uuid>", "eventType": "node:changed", "nodeId": "<NODE_ID>",

package/stacks/modeling-kit/templates/.claude/skills/place-element/SKILL.md

@@ -278,6 +278,7 @@ mcp__eventmodelers__create_screen {
   "nodeId": "<node-uuid>",
   "chapterId": "<TIMELINE_ID>",
   "cellId": "<CELL_ID>",
+  "title": "<title>",
   "pages": ["<div>...</div>"],
   "description": "<title — what this screen shows>"
 }
@@ -296,6 +297,7 @@ mcp__eventmodelers__create_screen {
   "nodeId": "<node-uuid>",
   "chapterId": "<TIMELINE_ID>",
   "cellId": "<CELL_ID>",
+  "title": "<title>",
   "elements": [...],
   "description": "<title — what this screen shows>"
 }
@@ -307,7 +309,7 @@ Pass whichever cell reference you already resolved — `CELL_ID` from Step 6, or
 
 ### Step 7b — All other element types
 
-Include `x-token`, `x-board-id`, and `x-user-id: agent` on every call to `/nodes/events`.
+Include `x-token` and `x-user-id: agent` on every call to `/nodes/events`.
 
 This step applies to `SCREEN` (view/output conflict case), `AUTOMATION`, `SCENARIO`-adjacent cleanup, and to `COMMAND`/`READMODEL`/`EVENT` whenever the "Prefer MCP — `place_element`" fast path above doesn't apply (explicit `cellName`, `"after <title>"` positioning, or conflict-insertion cases resolved manually in Step 6).
 

package/stacks/modeling-kit/templates/.claude/skills/place-element/references/api-fallback.md

@@ -45,7 +45,6 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$TL/column
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$TIMELINE_ID/columns" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '{}'
@@ -75,7 +74,7 @@ No relative-insertion equivalent over REST (unlike MCP's `afterNodeId`) — comp
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$TIMELINE_ID/columns" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: agent" \
+  -H "x-token: $TOKEN" -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '{"index": <currentColumnIndex + 1>}'
 ```
@@ -89,12 +88,12 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$TIMELINE_
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/html-screen-nodes/<node-uuid>" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '{
     "chapterId": "<TIMELINE_ID>",
     "cellId": "<CELL_ID>",
+    "title": "<title>",
     "pages": ["<div>...</div>"]
   }'
 ```
@@ -104,12 +103,12 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/html-screen-nodes/<n
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/image-nodes/<node-uuid>/sketch" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '{
     "chapterId": "<TIMELINE_ID>",
     "cellId": "<CELL_ID>",
+    "title": "<title>",
     "description": {"elements": [...]},
     "semanticDescription": "<title — what this screen shows>"
   }'
@@ -117,12 +116,11 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/image-nodes/<node-uu
 
 ## Step 7b — Create any other node type (normal path, `cellId`)
 
-Include `x-token`, `x-board-id`, and `x-user-id: agent` on every call to `/nodes/events`.
+Include `x-token` and `x-user-id: agent` on every call to `/nodes/events`.
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '[{
@@ -147,7 +145,6 @@ Same as above, but `cellName` replaces `cellId` — nothing else in the payload
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '[{

package/stacks/modeling-kit/templates/.claude/skills/storyboard/SKILL.md

@@ -183,6 +183,7 @@ mcp__eventmodelers__create_screen {
   "nodeId": "<SCREEN_NODE_ID>",
   "chapterId": "<CHAPTER_ID>",
   "cellId": "<actorCellId>",
+  "title": "<screenTitle>",
   "pages": ["<div>...</div>"],
   "description": "<screenTitle — what this screen shows>"
 }
@@ -201,6 +202,7 @@ mcp__eventmodelers__create_screen {
   "nodeId": "<SCREEN_NODE_ID>",
   "chapterId": "<CHAPTER_ID>",
   "cellId": "<actorCellId>",
+  "title": "<screenTitle>",
   "elements": [...],
   "description": "<screenTitle — what this screen shows>"
 }

package/stacks/modeling-kit/templates/.claude/skills/storyboard/references/api-fallback.md

@@ -33,12 +33,12 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/timelines/$CHAPTER_I
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/html-screen-nodes/$SCREEN_NODE_ID" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '{
     "chapterId": "<CHAPTER_ID>",
     "cellId": "<actorCellId>",
+    "title": "<screenTitle>",
     "pages": ["<div>...</div>"]
   }'
 ```
@@ -48,12 +48,12 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/html-screen-nodes/$S
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/image-nodes/$SCREEN_NODE_ID/sketch" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '{
     "chapterId": "<CHAPTER_ID>",
     "cellId": "<actorCellId>",
+    "title": "<screenTitle>",
     "description": {"elements": [...]},
     "semanticDescription": "<screenTitle — what this screen shows>"
   }'
@@ -63,7 +63,7 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/image-nodes/$SCREEN_
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: agent" \
+  -H "x-token: $TOKEN" -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '[{
     "id": "<event-uuid>", "eventType": "node:changed", "nodeId": "<SCREEN_NODE_ID>",

package/stacks/modeling-kit/templates/.claude/skills/storyboard-screen/references/api-fallback.md

@@ -7,7 +7,6 @@ Only needed when MCP is not connected. Every call below has an MCP equivalent in
 ```bash
 curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/images/$NODE_ID/description" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent"
 ```
 
@@ -19,7 +18,6 @@ curl -s "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/images/$NODE_ID/description"
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/images/$NODE_ID/sketch" \
   -H "x-token: $TOKEN" \
-  -H "x-board-id: $BOARD_ID" \
   -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '{"description": "<what this screen shows>", "elements": [...]}'
@@ -31,7 +29,7 @@ Expect `204 No Content` on success.
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
-  -H "x-token: $TOKEN" -H "x-board-id: $BOARD_ID" -H "x-user-id: agent" \
+  -H "x-token: $TOKEN" -H "x-user-id: agent" \
   -H "Content-Type: application/json" \
   -d '[{
     "id": "<event-uuid>", "eventType": "node:changed", "nodeId": "<NODE_ID>",

package/stacks/modeling-kit/templates/.claude/skills/wdyt/SKILL.md

@@ -146,7 +146,7 @@ Only post questions that are **genuinely unclear or missing** — don't post obs
 
 **Prefer MCP:** `mcp__eventmodelers__create_drawing` — one call per drawing, no auth headers needed.
 
-**Fallback (no MCP):** `POST /api/org/{orgId}/boards/{boardId}/drawing/draw` (auth headers same as every other call — `x-token`, `x-board-id`, `x-user-id: wdyt`). Same fields as the tool args below.
+**Fallback (no MCP):** `POST /api/org/{orgId}/boards/{boardId}/drawing/draw` (auth headers same as every other call — `x-token`, `x-user-id: wdyt`). Same fields as the tool args below.
 
 There are two kinds — no text-callout kind; a drawing never carries the question itself, only the shape of the concern:
 

package/stacks/react/templates/build-kit/lib/ralph.js

@@ -178,7 +178,7 @@ function slugify(str) {
 async function fetchAndPersistSlices(cfg, kitDir) {
   const url = `${cfg.baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/slicedata/slices`;
   const { slices } = await fetchJSON(url, {
-    headers: { 'x-token': cfg.token, 'x-board-id': cfg.boardId, ...agentHeaders(cfg) },
+    headers: { 'x-token': cfg.token, ...agentHeaders(cfg) },
   });
   const slicesDir = join(kitDir, '.slices');
   mkdirSync(slicesDir, { recursive: true });
@@ -400,7 +400,7 @@ async function blockStuckSlice(kitDir, cfg, credentialed, planned, attempts) {
     try {
       await fetchJSON(`${cfg.baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/nodes/events`, {
         method: 'POST',
-        headers: { 'Content-Type': 'application/json', 'x-token': cfg.token, 'x-board-id': cfg.boardId, 'x-user-id': 'ralph-loop', ...agentHeaders(cfg) },
+        headers: { 'Content-Type': 'application/json', 'x-token': cfg.token, 'x-user-id': 'ralph-loop', ...agentHeaders(cfg) },
         body: JSON.stringify([{
           id: randomUUID(),
           eventType: 'node:changed',