@eventmodelers/cli 1.0.77 → 1.0.79

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.
 
 ---
 
@@ -996,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/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 '{}'

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,7 +31,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/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>",
@@ -46,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>",
@@ -64,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,7 +26,6 @@ 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"'", "title": "<Screen Title>", "pages": ["<div>...</div>"]}'
@@ -38,7 +35,7 @@ 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/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

@@ -309,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).