@rayburst/cc 3.1.6 → 3.1.8

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.1.6"
+    "version": "3.1.8"
   },
   "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.1.6",
+      "version": "3.1.8",
       "author": {
         "name": "Rayburst"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rayburst",
-  "version": "3.1.6",
+  "version": "3.1.8",
   "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/hooks/posttooluse.mjs

@@ -46,14 +46,13 @@ if (toolName !== "Write" && toolName !== "Edit") {
   process.exit(0);
 }
 var activeFeature = readCache("active-feature");
-if (!activeFeature) {
-  process.exit(0);
-}
 var filePath = toolInput?.file_path || toolInput?.path || "unknown";
 function escapeXml(str) {
   return (str || "").replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;").replace(/"/g, "&quot;");
 }
-var contextBlock = `<rayburst_post_implementation_reminder>
+var contextBlock;
+if (activeFeature) {
+  contextBlock = `<rayburst_post_implementation_reminder>
   <action_required>You just modified ${escapeXml(filePath)}. Before continuing to the next task or responding to the user, you MUST update the Rayburst feature atlas NOW:
     1. Call rb_add_criterion for any new behaviors introduced
     2. Call rb_update_criterion to mark criteria as passing/failing
@@ -61,6 +60,16 @@ var contextBlock = `<rayburst_post_implementation_reminder>
   Do NOT proceed without completing this step. This is a mandatory workflow requirement.</action_required>
   <active_feature>${escapeXml(activeFeature.title)} (${activeFeature.id})</active_feature>
 </rayburst_post_implementation_reminder>`;
+} else {
+  contextBlock = `<rayburst_post_implementation_reminder>
+  <action_required>You just modified ${escapeXml(filePath)} but NO active feature was matched for this task. This likely means you skipped the mandatory feature lookup step. You MUST now:
+    1. Call rb_list_features with a search term related to the area you just changed
+    2. Call rb_get_feature on the best match to load its criteria
+    3. Call rb_add_criterion or rb_update_criterion to reflect what you built
+    4. Call rb_update_feature if the feature description needs updating
+  ALL changes \u2014 including visual, layout, and icon changes \u2014 require feature atlas updates. Do NOT skip this.</action_required>
+</rayburst_post_implementation_reminder>`;
+}
 console.log(
   JSON.stringify({
     hookSpecificOutput: {

package/hooks/pretooluse.mjs

@@ -24,12 +24,12 @@ function readCache(type) {
 }
 
 // src/hooks/product-context-block.ts
-function buildCodingReminderBlock(activeFeature2, filePath2, relatedFeatures2) {
+function buildCodingReminderBlock(activeFeature2, filePath2, relatedFeatures) {
   if (!activeFeature2) return "";
   const criteria = (activeFeature2.criteria || []).map((c) => `  - [ ] ${escapeXml(c.title || c.description || "")}`).join("\n");
   let relatedNote = "";
-  if (relatedFeatures2 && relatedFeatures2.length > 0) {
-    const names = relatedFeatures2.map((f) => `"${escapeXml(f.title)}"`).join(", ");
+  if (relatedFeatures && relatedFeatures.length > 0) {
+    const names = relatedFeatures.map((f) => `"${escapeXml(f.title)}"`).join(", ");
     relatedNote = `
   <related_features>This file may also relate to: ${names}. Check that your changes don't break their criteria.</related_features>`;
   }
@@ -42,6 +42,16 @@ ${criteria}
   <post_implementation_required>Before submitting your response, you MUST update the Rayburst feature atlas: add/update criteria for any new behaviors via rb_add_criterion, update the feature description if it changed via rb_update_feature. You will be reminded again after writing. Do NOT skip this step.</post_implementation_required>
 </rayburst_coding_reminder>`;
 }
+function buildNoFeatureWarningBlock(filePath2) {
+  return `<rayburst_no_feature_warning>
+  <warning>You are about to modify ${escapeXml(filePath2 || "a file")} but NO feature from the Rayburst atlas was matched to your current task. This means you skipped the mandatory feature lookup step.</warning>
+  <required_action>BEFORE writing this code, you MUST:
+    1. Call rb_list_features with a search term related to the area you are changing
+    2. Call rb_get_feature on the best match to load its acceptance criteria
+    3. Work against those criteria
+  ALL changes \u2014 including visual, layout, icon, and styling changes \u2014 require a feature lookup. There are no exceptions.</required_action>
+</rayburst_no_feature_warning>`;
+}
 function escapeXml(str) {
   return (str || "").replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;").replace(/"/g, "&quot;");
 }
@@ -69,29 +79,31 @@ if (toolName !== "Write" && toolName !== "Edit") {
   process.exit(0);
 }
 var activeFeature = readCache("active-feature");
-if (!activeFeature) {
-  process.exit(0);
-}
 var filePath = toolInput?.file_path || toolInput?.path || "";
-var featureList = readCache("features") || [];
-var relatedFeatures = [];
-if (filePath) {
-  const fileBasename = filePath.split("/").pop() || "";
-  const fileDir = filePath.split("/").slice(-2, -1)[0] || "";
-  for (const f of featureList) {
-    if (f.id === activeFeature.id) continue;
-    const desc = (f.description || "").toLowerCase();
-    const title = (f.title || "").toLowerCase();
-    if (desc.includes(fileBasename.toLowerCase()) || desc.includes(fileDir.toLowerCase()) || title.includes(fileBasename.toLowerCase().replace(/\.\w+$/, ""))) {
-      relatedFeatures.push(f);
+var contextBlock;
+if (activeFeature) {
+  const featureList = readCache("features") || [];
+  const relatedFeatures = [];
+  if (filePath) {
+    const fileBasename = filePath.split("/").pop() || "";
+    const fileDir = filePath.split("/").slice(-2, -1)[0] || "";
+    for (const f of featureList) {
+      if (f.id === activeFeature.id) continue;
+      const desc = (f.description || "").toLowerCase();
+      const title = (f.title || "").toLowerCase();
+      if (desc.includes(fileBasename.toLowerCase()) || desc.includes(fileDir.toLowerCase()) || title.includes(fileBasename.toLowerCase().replace(/\.\w+$/, ""))) {
+        relatedFeatures.push(f);
+      }
     }
   }
+  contextBlock = buildCodingReminderBlock(
+    activeFeature,
+    filePath,
+    relatedFeatures.slice(0, 3)
+  );
+} else {
+  contextBlock = buildNoFeatureWarningBlock(filePath);
 }
-var contextBlock = buildCodingReminderBlock(
-  activeFeature,
-  filePath,
-  relatedFeatures.slice(0, 3)
-);
 if (contextBlock) {
   console.log(
     JSON.stringify({

package/hooks/sessionstart.mjs

@@ -153,11 +153,10 @@ function buildProductContextBlock(features, cards) {
   return `<rayburst_product_context>
   <rules>
     <rule>You have access to a Rayburst feature atlas \u2014 a knowledge graph of product features with Gherkin acceptance criteria. Use it to understand what you're building.</rule>
-    <rule>Before implementing any task, check if a matching feature exists in the atlas below. If found, read its criteria with rb_get_feature and work against them.</rule>
+    <rule>MANDATORY PRE-IMPLEMENTATION STEP: Before writing ANY code \u2014 regardless of task size, type, or complexity (including visual changes, icon swaps, layout tweaks, styling, refactoring) \u2014 you MUST: (1) call rb_list_features to search for a matching feature, (2) call rb_get_feature to load its criteria, (3) work against those criteria. There are NO exceptions. If no feature exists, create one with rb_create_feature before proceeding.</rule>
     <rule>If your changes may affect behaviors described in OTHER features' criteria, flag this to the user before proceeding.</rule>
     <rule>NEVER create, update, or delete features or criteria in the atlas without explicitly asking the user for confirmation first. Show them what you want to change and wait for approval.</rule>
-    <rule>When implementation is complete, summarize which acceptance criteria were addressed and which remain pending.</rule>
-    <rule>MANDATORY: After every implementation \u2014 in the same response as the code changes \u2014 you MUST update Rayburst without being asked: (1) update affected feature descriptions if behavior changed via rb_update_feature, (2) add new acceptance criteria for every new behavior introduced via rb_add_criterion, (3) update criterion status where applicable via rb_update_criterion. Do NOT wait for the user to ask. Skipping this step is a workflow violation.</rule>
+    <rule>MANDATORY POST-IMPLEMENTATION STEP: After every implementation \u2014 in the same response as the code changes \u2014 you MUST update Rayburst without being asked: (1) update affected feature descriptions if behavior changed via rb_update_feature, (2) add new acceptance criteria for every new behavior introduced via rb_add_criterion, (3) update criterion status where applicable via rb_update_criterion. Do NOT wait for the user to ask. A post-write hook will verify compliance.</rule>
     <rule>Use mcp__plugin_rayburst_rayburst__rb_* MCP tools to interact with the atlas. Use rb_get_feature to load full criteria for a specific feature.</rule>
   </rules>
 

package/package.json

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