@rayburst/cc 3.2.1 → 3.2.3

package/.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "Always-on product context for Claude Code — features, acceptance criteria, and board cards injected automatically.",
-    "version": "3.2.1"
+    "version": "3.2.3"
   },
   "plugins": [
     {
       "name": "rayburst",
       "source": "./",
       "description": "Always-on product context for Claude Code. Automatically injects your Rayburst Product Requirement Registry (features, Gherkin acceptance criteria, board cards) into every coding session.",
-      "version": "3.2.1",
+      "version": "3.2.3",
       "author": {
         "name": "Rayburst"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rayburst",
-  "version": "3.2.1",
+  "version": "3.2.3",
   "description": "Always-on product context for Claude Code. Automatically injects feature atlas and acceptance criteria into every coding session — no slash commands needed.",
   "author": {
     "name": "Rayburst",

package/README.md

@@ -8,6 +8,20 @@
   <img src="claude_code_x_rayburst_prr.png" alt="Claude Code x Rayburst Product Requirement Registry" width="100%">
 </p>
 
+## Install
+
+```bash
+claude plugin add Dubwoof/rayburst-cc
+```
+
+Restart Claude Code, then run `/rb:init`. The setup wizard walks you through three steps:
+
+1. **Paste your API key** — grab one from [rayburst.app/profile](https://www.rayburst.app/profile?tab=mcp-agents)
+2. **Pick your projects** — the wizard lists your org's projects, just select by number
+3. **Pick a board** — same thing, select from the list
+
+That's it — every session now has your product context automatically.
+
 ## The Problem
 
 You're building a feature. Claude Code writes the code, but has no idea what the feature is supposed to do. It doesn't know the acceptance criteria. It doesn't know which board card it's working on. Every conversation starts from zero — you re-explain the requirements, the edge cases, the definition of done.
@@ -90,31 +104,6 @@ The server uses a lazy client pattern — it doesn't connect to the API at start
 
 Claude decides when to call these tools based on the rules injected by the SessionStart hook. The user never needs to invoke them manually.
 
-## Install
-
-**Prerequisites:** Claude Code v1.0.33+ and a [Rayburst](https://rayburst.app) account with an API key.
-
-```bash
-claude plugin add Dubwoof/rayburst-cc
-```
-
-Restart Claude Code, then run the one-time setup:
-
-```
-/rb:init
-```
-
-This prompts for:
-- **Rayburst API key** — get one at [https://www.rayburst.app/profile?tab=mcp-agents](https://www.rayburst.app/profile?tab=mcp-agents) (starts with `rb_user_`)
-- **Project URL** — the base URL of your running app (e.g. `http://localhost:3000`)
-- **Board** — picks from your org's boards via the API
-- **Project IDs** — frontend and backend project UUIDs
-- **User credentials** — username/password for browser-based validation (passwords can reference env vars with `$VAR_NAME`)
-
-Config is saved to `.claude/rb-config.md`. **Add this to `.gitignore`** — it contains your API key.
-
-That's it. Every Claude Code session in this project now has product context automatically.
-
 ## How a Session Looks
 
 ```

package/hooks/sessionstart.mjs

@@ -185,12 +185,14 @@ ${cardLines}
 }
 function buildEmptyAtlasBlock() {
   return `<rayburst_empty_atlas>
-  <warning>The Rayburst feature atlas is EMPTY \u2014 no product features have been defined yet.</warning>
-  <required_action>You MUST NOT write or edit any code this session until you have created at least one feature in the atlas.
-    1. Ask the user what feature or behavior you are about to implement
-    2. Call rb_create_feature to register it (with user confirmation first)
-    3. Add acceptance criteria via rb_add_criterion
-    4. Only then proceed with implementation
+  <warning>The Rayburst feature atlas appears EMPTY \u2014 the session-start fetch returned no features. This may mean no features exist yet, OR that a config/API issue prevented loading them.</warning>
+  <required_action>You MUST NOT write or edit any code this session until you have verified the atlas and registered the feature you are implementing.
+    1. Call rb_list_features (with an empty or broad search term) to verify the atlas is truly empty \u2014 do NOT skip this step even if the summary says 0 features
+    2. If features exist, call rb_get_feature on the best match and work against its criteria
+    3. If the atlas is genuinely empty, ask the user what feature or behavior you are about to implement
+    4. Call rb_create_feature to register it (with user confirmation first)
+    5. Add acceptance criteria via rb_add_criterion
+    6. Only then proceed with implementation
   This applies to ALL changes \u2014 bug fixes, refactors, visual tweaks, and new features alike. There are no exceptions.</required_action>
 </rayburst_empty_atlas>`;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayburst/cc",
-  "version": "3.2.1",
+  "version": "3.2.3",
   "type": "module",
   "description": "Always-on product context for Claude Code. Automatically injects feature atlas and acceptance criteria into every coding session.",
   "author": {