@rayburst/cc 1.0.26 → 1.0.28

package/commands/rb/discover.md

@@ -77,11 +77,13 @@ Print a warning:
 
 If a feature-atlas key is found, proceed to Step 1 using this derived prefix.
 
----
-
-**Level 3 (curl-only fallback)**
+If no feature-atlas server is found in either `rb-config.md` or `.mcp.json`, stop immediately:
+```
+ERROR: rb:discover requires an MCP server assigned to the `feature-atlas` role.
 
-Only if no feature-atlas server is found in either `rb-config.md` or `.mcp.json`: fall back to curl JSON-RPC using the Bearer token of the first HTTP MCP server in `.mcp.json`. Note that all subsequent MCP calls in the workflow will use curl JSON-RPC instead of MCP tool calls.
+Run /rb:init to configure MCP server role assignments.
+The feature-atlas role must be mapped to an MCP server in .mcp.json before running discovery.
+```
 
 ---
 
@@ -94,7 +96,15 @@ Call:
 ```
 
 - **Success** → proceed with MCP tool calls
-- **Failure** → switch to curl fallback for all remaining MCP calls; do NOT stop the workflow
+- **Failure** → stop immediately:
+  ```
+  ERROR: The MCP server for the feature-atlas role is not loaded in this session.
+
+  The MCP server '<server-name>' must be available. Try:
+  1. Start a new Claude session (MCP servers load at session start)
+  2. Verify the server entry exists in .mcp.json
+  3. Re-run /rb:init to confirm role assignments
+  ```
 
 ---
 

package/commands/rb/implement.md

@@ -57,7 +57,13 @@ Read `.claude/rb-config.md` and parse the `## MCP Role Assignments` table. Find
   ```
   Example: if the server name is `rayburst-rb-engineer-780086`, then `MCP_PREFIX = mcp__rayburst-rb-engineer-780086__`.
 
-- If `.claude/rb-config.md` does not exist or the role is `unassigned`, set `MCP_PREFIX = ""` and use the curl fallback for all MCP calls (see "MCP Curl Fallback" section). Read the API key from `.mcp.json` under the first HTTP MCP server entry.
+- If `.claude/rb-config.md` does not exist or the role is `unassigned`, stop immediately:
+  ```
+  ERROR: rb:implement requires an MCP server assigned to the `engineer` role.
+
+  Run /rb:init to configure MCP server role assignments.
+  The engineer role must be mapped to an MCP server in .mcp.json before implementing cards.
+  ```
 
 All MCP tool calls below use `<MCP_PREFIX>` as a stand-in for the resolved prefix.
 
@@ -69,7 +75,15 @@ All MCP tool calls below use `<MCP_PREFIX>` as a stand-in for the resolved prefi
 <MCP_PREFIX>ping()
 ```
 
-If ping fails (tool not found), fall back to curl JSON-RPC for the entire workflow. If ping via curl also fails, stop and report the error.
+If ping fails (tool not found or error), stop immediately:
+```
+ERROR: The MCP server for the engineer role is not loaded in this session.
+
+The MCP server '<server-name>' must be available. Try:
+1. Start a new Claude session (MCP servers load at session start)
+2. Verify the server entry exists in .mcp.json
+3. Re-run /rb:init to confirm role assignments
+```
 
 ---
 
@@ -257,44 +271,6 @@ Run `/rb:validate-card <cardId>` to run QA validation.
 
 ---
 
-## MCP Curl Fallback
-
-When MCP tools are unavailable, use curl JSON-RPC. Read the API key from `.mcp.json` under the server assigned to the `engineer` role (or the first HTTP server entry).
-
-```bash
-# Ping
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ping","arguments":{}}}'
-
-# Get card
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_card","arguments":{"cardId":"<cardId>"}}}'
-
-# Move card
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"move_card","arguments":{"cardId":"<cardId>","status":"in-progress"}}}'
-
-# Add comment
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"add_comment","arguments":{"cardId":"<cardId>","content":"<comment>"}}}'
-```
-
-Parse the `data:` line from the SSE response to extract the JSON result.
-
----
-
 ## Constraints
 
 - **Full UUIDs only** — short hashes return NOT_FOUND

package/commands/rb/plan.md

@@ -9,6 +9,23 @@ allowed-tools:
 
 # rb:plan — Task-Driven PM Session
 
+> **HARD STOP — READ BEFORE ANYTHING ELSE**
+>
+> This command is **PM-only**. It MUST NOT touch any code or files outside `.claude/rb-config.md`.
+>
+> The following actions are **absolutely forbidden** for the duration of this command:
+> - Writing, editing, or creating any code file (no Edit, no Write, no file changes)
+> - Running build, test, lint, or npm commands
+> - Making git commits or git operations
+> - Suggesting implementation steps or architectural decisions
+> - Moving cards to `in-progress` or `done`
+>
+> If you feel tempted to implement anything — **stop immediately and return to Step 4 (Create Board Card)**.
+>
+> The CLAUDE.md "PM Feature Sync" rule does NOT apply here — skip it entirely. This command IS the PM step.
+
+---
+
 Given a task description, act as a PM to set it up in the feature atlas and on the board. This command **never implements anything** — it only does PM + board setup.
 
 ## Reference Data
@@ -165,15 +182,6 @@ Always use the full UUID from the `create_card` response — never a short hash.
 
 ---
 
-## What `/rb:plan` Must NOT Do
-
-- Never write, edit, or create code files
-- Never run implementation commands (npm, git commits, builds, tests)
-- Never suggest implementation steps or architectural decisions
-- Never move cards to `in-progress` or `done`
-
----
-
 ## Feature Quality Rules
 
 **Titles:**

package/commands/rb/validate-card.md

@@ -61,7 +61,13 @@ Read `.claude/rb-config.md` and parse the `## MCP Role Assignments` table. Find
   ```
   Example: if the server name is `rayburst-rb-qa-engineer-55ae0f`, then `MCP_PREFIX = mcp__rayburst-rb-qa-engineer-55ae0f__`.
 
-- If `.claude/rb-config.md` does not exist or the role is `unassigned`, set `MCP_PREFIX = ""` and use the curl fallback for all MCP calls (see "MCP Curl Fallback" section below). Read the API key from `.mcp.json` under the first HTTP MCP server entry.
+- If `.claude/rb-config.md` does not exist or the role is `unassigned`, stop immediately:
+  ```
+  ERROR: rb:validate-card requires an MCP server assigned to the `qa-engineer` role.
+
+  Run /rb:init to configure MCP server role assignments.
+  The qa-engineer role must be mapped to an MCP server in .mcp.json before validating cards.
+  ```
 
 All MCP tool calls below use `<MCP_PREFIX>` as a stand-in for the resolved prefix.
 
@@ -73,22 +79,15 @@ All MCP tool calls below use `<MCP_PREFIX>` as a stand-in for the resolved prefi
 <MCP_PREFIX>ping()
 ```
 
-**If the MCP tool is not found** (error: "No such tool available"), the MCP server did not load in this session. Do NOT stop — fall back to curl JSON-RPC for the entire workflow:
-
-```bash
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <API_KEY_FROM_.mcp.json>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ping","arguments":{}}}'
+**If the MCP tool is not found** (error: "No such tool available"), stop immediately:
 ```
+ERROR: The MCP server for the qa-engineer role is not loaded in this session.
 
-Read the API key from `.mcp.json` under the server assigned to the `qa-engineer` role (from `rb-config.md`), or the first HTTP server entry if config is missing.
-Parse the SSE response: result is in the `data:` line as `{"result":{"content":[{"type":"text","text":"..."}]}}`.
-
-If ping via curl also fails (network error), stop and report the error.
-
-**Use curl for ALL subsequent MCP calls** (get_card, list_cards, list_card_features, get_feature, add_comment, submit_validation, move_card) whenever MCP tools are unavailable.
+The MCP server '<server-name>' must be available. Try:
+1. Start a new Claude session (MCP servers load at session start)
+2. Verify the server entry exists in .mcp.json
+3. Re-run /rb:init to confirm role assignments
+```
 
 ### Step 2: Resolve the Card
 
@@ -222,7 +221,7 @@ After testing each criterion, record locally:
 })
 ```
 
-**Comment rules (critical when using curl fallback):**
+**Comment rules:**
 - Keep comments under 500 characters
 - Plain prose only — no backtick code, no raw code snippets, no JSON in comment strings (causes `INTERNAL_ERROR`)
 - Reference files as plain text: "ComponentName.tsx line 79" not a code excerpt
@@ -281,44 +280,6 @@ Report ID: <report-id>
 
 ---
 
-## MCP Curl Fallback
-
-When MCP tools are unavailable, use this curl pattern. Read the API key from `.mcp.json` under the server assigned to the `qa-engineer` role (or the first HTTP server entry if config is missing):
-
-```bash
-# Get card
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_card","arguments":{"cardId":"<cardId>"}}}'
-
-# List card features
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_card_features","arguments":{"cardId":"<cardId>"}}}'
-
-# Submit validation (cardId, not featureId)
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"submit_validation","arguments":{"cardId":"<cardId>","results":[...],"overallComment":"..."}}}'
-
-# Move card to done
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"move_card","arguments":{"cardId":"<cardId>","status":"done"}}}'
-```
-
-Parse the `data:` line from the SSE response to extract the JSON result.
-
----
-
 ## Constraints
 
 - Full UUIDs only

package/commands/rb/validate-feature.md

@@ -61,7 +61,13 @@ Read `.claude/rb-config.md` and parse the `## MCP Role Assignments` table. Find
   ```
   Example: if the server name is `rayburst-rb-qa-engineer-55ae0f`, then `MCP_PREFIX = mcp__rayburst-rb-qa-engineer-55ae0f__`.
 
-- If `.claude/rb-config.md` does not exist or the role is `unassigned`, set `MCP_PREFIX = ""` and use the curl fallback for all MCP calls (see "MCP Curl Fallback" section below). Read the API key from `.mcp.json` under the first HTTP MCP server entry.
+- If `.claude/rb-config.md` does not exist or the role is `unassigned`, stop immediately:
+  ```
+  ERROR: rb:validate-feature requires an MCP server assigned to the `qa-engineer` role.
+
+  Run /rb:init to configure MCP server role assignments.
+  The qa-engineer role must be mapped to an MCP server in .mcp.json before validating features.
+  ```
 
 All MCP tool calls below use `<MCP_PREFIX>` as a stand-in for the resolved prefix.
 
@@ -73,22 +79,15 @@ All MCP tool calls below use `<MCP_PREFIX>` as a stand-in for the resolved prefi
 <MCP_PREFIX>ping()
 ```
 
-**If the MCP tool is not found** (error: "No such tool available"), the MCP server did not load in this session. Do NOT stop — fall back to curl JSON-RPC for the entire workflow:
-
-```bash
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <API_KEY_FROM_.mcp.json>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ping","arguments":{}}}'
+**If the MCP tool is not found** (error: "No such tool available"), stop immediately:
 ```
+ERROR: The MCP server for the qa-engineer role is not loaded in this session.
 
-Read the API key from `.mcp.json` under the server assigned to the `qa-engineer` role (from `rb-config.md`), or the first HTTP server entry if config is missing.
-Parse the SSE response: result is in the `data:` line as `{"result":{"content":[{"type":"text","text":"..."}]}}`.
-
-If ping via curl also fails (network error), stop and report the error.
-
-**Use curl for ALL subsequent MCP calls** (get_feature, list_boards, create_card, link_feature, submit_validation, update_feature) whenever MCP tools are unavailable.
+The MCP server '<server-name>' must be available. Try:
+1. Start a new Claude session (MCP servers load at session start)
+2. Verify the server entry exists in .mcp.json
+3. Re-run /rb:init to confirm role assignments
+```
 
 ### Step 2: Resolve the Feature
 
@@ -222,7 +221,7 @@ Rules:
 })
 ```
 
-**Comment rules (critical when using curl fallback):**
+**Comment rules:**
 - Keep comments under 500 characters
 - Plain prose only — no backtick code, no raw code snippets, no JSON in comment strings (causes `INTERNAL_ERROR`)
 - Reference files as plain text: "ComponentName.tsx line 79" not a code excerpt
@@ -270,22 +269,6 @@ Submitted via submit_validation (featureId: <id>)
 
 ---
 
-## MCP Curl Fallback
-
-When MCP tools are unavailable, use this curl pattern. Read the API key from `.mcp.json` under the server assigned to the `qa-engineer` role (or the first HTTP server entry if config is missing):
-
-```bash
-curl -s -X POST "https://api.rayburst.app/api/v1/mcp" \
-  -H "Authorization: Bearer <KEY>" \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_feature","arguments":{"featureId":"<id>"}}}'
-```
-
-Parse the `data:` line from the SSE response to extract the JSON result.
-
----
-
 ## Constraints
 
 - Full UUIDs only

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayburst/cc",
-  "version": "1.0.26",
+  "version": "1.0.28",
   "description": "Rayburst slash commands for Claude Code — /rb:init, /rb:plan, /rb:sync, /rb:status, /rb:validate-feature, /rb:validate-card, /rb:implement, /rb:discover",
   "bin": {
     "rayburst-cc": "bin/install.js"