agentvibes 2.0.13 → 2.0.15

package/.claude/github-star-reminder.txt

@@ -1 +1 @@
-20251009
+20251011

package/.claude/hooks/bmad-voice-manager.sh

@@ -104,6 +104,69 @@ SENTIMENT=$CURRENT_SENTIMENT
 EOF
 
     touch "$ENABLED_FLAG"
+
+    # Create activation-instructions file for BMAD agents
+    ACTIVATION_FILE=".claude/activation-instructions"
+    if [[ ! -f "$ACTIVATION_FILE" ]]; then
+        cat > "$ACTIVATION_FILE" <<'ACTIVATION_EOF'
+# BMAD Agent Activation Instructions
+
+When a BMAD agent activates, follow these steps EXACTLY:
+
+## STEP 3.5a: Create BMAD Context File (CRITICAL)
+
+**IMMEDIATELY after agent identification, create the context file:**
+
+```bash
+echo "$AGENT_ID" > .bmad-agent-context
+```
+
+Where `$AGENT_ID` is one of:
+- `pm` (Product Manager)
+- `dev` (Developer)
+- `qa` (QA)
+- `architect` (Architect)
+- `po` (Product Owner)
+- `analyst` (Analyst)
+- `sm` (Scrum Master)
+- `ux-expert` (UX Expert)
+- `bmad-master` (BMAD Master)
+- `bmad-orchestrator` (Orchestrator)
+
+**Example:**
+```bash
+# For Product Manager agent
+echo "pm" > .bmad-agent-context
+```
+
+This file allows AgentVibes to:
+1. Detect which BMAD agent is active
+2. Look up the correct voice mapping
+3. Automatically speak questions using the agent's assigned voice
+
+## STEP 10: Clean Up on Exit
+
+**Before exiting the agent, remove the context file:**
+
+```bash
+rm -f .bmad-agent-context
+```
+
+This ensures voice switching only happens when an agent is active.
+
+## Why This Matters
+
+Without the `.bmad-agent-context` file:
+- AgentVibes cannot detect which agent is active
+- Questions won't be spoken automatically
+- Voice switching won't work
+- The BMAD voice plugin becomes non-functional
+
+**This is MANDATORY for BMAD voice integration to work!**
+ACTIVATION_EOF
+        echo "📝 Created activation instructions: $ACTIVATION_FILE"
+    fi
+
     echo "✅ BMAD voice plugin enabled"
     echo "💾 Previous settings backed up:"
     echo "   Voice: $CURRENT_VOICE"

package/README.md

@@ -11,7 +11,7 @@
 [![Publish](https://github.com/paulpreibisch/AgentVibes/actions/workflows/publish.yml/badge.svg)](https://github.com/paulpreibisch/AgentVibes/actions/workflows/publish.yml)
 [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 
-**Author**: Paul Preibisch ([@997Fire](https://x.com/997Fire)) | **Version**: v2.0.13
+**Author**: Paul Preibisch ([@997Fire](https://x.com/997Fire)) | **Version**: v2.0.15
 
 ---
 
@@ -45,8 +45,8 @@
 
 ## 📰 Latest Release
 
-**[v2.0.0 - The Multi-Provider Revolution](https://github.com/paulpreibisch/AgentVibes/releases/tag/v2.0.13)** 🎉
-
+**[v2.0.15 - Release Notes](https://github.com/paulpreibisch/AgentVibes/releases/tag/v2.0.15)** 🎉
+This patch release fixes a critical bug where the BMAD voice plugin was not automatically enabled during installation, even when BMAD was detected. Users installing AgentVibes with BMAD present would find plugin files created but the plugin non-functional because the crucial `.claude/activation-instructions` file was missing and the plugin wasn't enabled. Now, when BMAD is detected, the installer automatically creates activation instructions, enables the plugin, and sets everything up to work out of the box.
 The biggest update ever! **Multi-provider TTS support** (ElevenLabs + Piper TTS), **30+ languages**, expanded voice library (27+ voices), advanced sentiment system, enhanced BMAD integration, and comprehensive multilingual support. Choose between premium ElevenLabs voices or free offline Piper TTS!
 
 **Key highlights:**

package/RELEASE_NOTES.md

@@ -1,5 +1,237 @@
 # 🎤 AgentVibes Release Notes
 
+## 📦 v2.0.15 - BMAD Plugin Auto-Enable Fix (2025-10-12)
+
+### 🤖 AI Summary
+
+This patch release fixes a critical bug where the BMAD voice plugin was not automatically enabled during installation, even when BMAD was detected. Users installing AgentVibes with BMAD present would find plugin files created but the plugin non-functional because the crucial `.claude/activation-instructions` file was missing and the plugin wasn't enabled. Now, when BMAD is detected, the installer automatically creates activation instructions, enables the plugin, and sets everything up to work out of the box.
+
+### 🐛 Bug Fixes
+
+#### BMAD Plugin Auto-Enable Not Working
+- **Fixed**: Plugin not enabled when BMAD detected during installation
+- **Fixed**: Missing `.claude/activation-instructions` file prevented BMAD agents from creating context
+- **Root Cause**: Installer created plugin files but never enabled the plugin or created activation instructions
+- **Impact**: BMAD voice integration was non-functional after fresh installs
+- **Solution**: Auto-enable plugin and create activation-instructions when BMAD detected
+
+**What Was Broken:**
+```bash
+# Before: Plugin files created but not actually working
+npx agentvibes install  # (with BMAD present)
+# ✓ Created .claude/plugins/bmad-voices.md
+# ✗ No .claude/plugins/bmad-voices-enabled.flag (plugin disabled!)
+# ✗ No .claude/activation-instructions (agents don't know what to do!)
+
+# Result: BMAD agents don't speak, voice switching doesn't work
+```
+
+**After Fix:**
+```bash
+# After: Plugin fully configured and working
+npx agentvibes install  # (with BMAD present)
+# ✓ Created .claude/plugins/bmad-voices.md
+# ✓ Created .claude/plugins/bmad-voices-enabled.flag (auto-enabled!)
+# ✓ Created .claude/activation-instructions (agents know what to do!)
+# 🎤 Auto-enabled BMAD voice plugin
+
+# Result: BMAD agents speak automatically with assigned voices!
+```
+
+#### Missing Activation Instructions
+- **Fixed**: `.claude/activation-instructions` not created by installer
+- **Fixed**: Manual `/agent-vibes:bmad enable` also didn't create instructions
+- **Impact**: BMAD agents couldn't create `.bmad-agent-context` file
+- **Solution**: Both installer and manual enable now create comprehensive activation instructions
+
+**Why This File Matters:**
+
+The `.claude/activation-instructions` file tells BMAD agents to:
+1. Create `.bmad-agent-context` file with agent ID when activating
+2. Clean up the context file when exiting
+3. This allows AgentVibes to detect which agent is active and switch voices
+
+Without this file, agents never create the context file, so AgentVibes can't detect them and voice switching fails silently.
+
+### 📝 Technical Changes
+
+**Modified: `src/installer.js`** (Lines 668-743)
+- Added auto-enable logic when BMAD detected
+- Creates `.claude/plugins/bmad-voices-enabled.flag` automatically
+- Creates `.claude/activation-instructions` with full BMAD agent instructions
+- Updates success message to reflect auto-enable status
+- Fixed command examples in BMAD detection box (was `/agent-vibes-bmad`, now `/agent-vibes:bmad`)
+
+**Modified: `.claude/hooks/bmad-voice-manager.sh`** (Lines 106-168)
+- Added automatic creation of `.claude/activation-instructions` when enabling
+- Uses heredoc to embed full activation instructions
+- Only creates file if it doesn't exist (preserves customizations)
+- Shows confirmation message when file created
+
+**Added: `templates/activation-instructions-bmad.md`**
+- Template file documenting the activation instructions
+- Reference for what gets created by the system
+- Explains why the file is critical for BMAD integration
+
+### 🎯 User Impact
+
+**Before v2.0.15:**
+- Fresh AgentVibes install with BMAD: Voice integration didn't work
+- Users had to manually debug why BMAD agents weren't speaking
+- Required manual creation of activation-instructions file
+- Plugin appeared "enabled" but wasn't actually functional
+
+**After v2.0.15:**
+- Fresh install with BMAD: Everything works immediately
+- BMAD agents speak automatically with assigned voices
+- Voice switching works out of the box
+- No manual configuration needed
+
+### 🔄 Opt-Out Design
+
+**Philosophy: Auto-enable with easy opt-out**
+- If you have BMAD installed, you probably want voice integration
+- Better to work by default than require manual setup
+- Users can easily disable with `/agent-vibes:bmad disable` if unwanted
+
+### 📊 Files Changed
+
+**Modified (2 files):**
+- `src/installer.js` (87 lines added, 6 lines removed)
+- `.claude/hooks/bmad-voice-manager.sh` (63 lines added)
+
+**Added (1 file):**
+- `templates/activation-instructions-bmad.md` (54 lines)
+
+**Total Changes:** 204 insertions, 6 deletions across 3 files
+
+### 🔄 Migration Notes
+
+**For New Users:**
+- No action needed - BMAD plugin auto-enables and works immediately
+- Just run `npx agentvibes install` in directory with BMAD
+
+**For Existing Users (v2.0.14 and earlier):**
+
+If you previously installed AgentVibes and found BMAD voice integration not working:
+
+```bash
+# Update AgentVibes
+/agent-vibes:update
+
+# The plugin will auto-enable on next install if BMAD detected
+# Or manually enable:
+/agent-vibes:bmad enable
+```
+
+**To Disable BMAD Plugin (if unwanted):**
+```bash
+/agent-vibes:bmad disable
+```
+
+### 💡 What Gets Created
+
+When BMAD is detected during installation, the system creates:
+
+1. **`.claude/plugins/bmad-voices.md`** - Voice-to-agent mappings
+2. **`.claude/plugins/bmad-voices-enabled.flag`** - Enables the plugin
+3. **`.claude/activation-instructions`** - Instructions for BMAD agents
+
+**Sample Activation Instructions:**
+```markdown
+## STEP 3.5a: Create BMAD Context File (CRITICAL)
+
+**IMMEDIATELY after agent identification, create the context file:**
+
+```bash
+echo "$AGENT_ID" > .bmad-agent-context
+```
+
+This allows AgentVibes to:
+1. Detect which BMAD agent is active
+2. Look up the correct voice mapping
+3. Automatically speak questions using the agent's assigned voice
+```
+
+### 🙏 Credits
+
+Thanks to the user who reported this issue in the md-presentations directory! This led to discovering that the BMAD plugin setup was incomplete for all fresh installations.
+
+---
+
+## 📦 v2.0.14 - README Version Fix for npm (2025-10-11)
+
+### 🤖 AI Summary
+
+This patch release updates the npm package's README to display the correct version numbers. Since v2.0.13 was published before the README was corrected, the npm website displayed outdated version information. This release ensures users see v2.0.14 everywhere.
+
+### 🐛 Bug Fixes
+
+#### npm README Version Display
+- **Fixed**: npm package page now shows correct version (v2.0.14)
+- **Root Cause**: v2.0.13 was published with uncorrected README
+- **Impact**: Users visiting npmjs.com/package/agentvibes now see accurate version info
+- **Solution**: Republish with corrected README
+
+### 📝 What Changed
+
+**Modified: `README.md`**
+- Author line now shows v2.0.14
+- Latest Release section shows v2.0.14
+
+**Modified: `package.json`, `package-lock.json`**
+- Bumped version from 2.0.13 to 2.0.14
+
+### 🔄 Migration Notes
+
+**For All Users:**
+- No functional changes - this is purely a documentation update
+- Update via `/agent-vibes:update` to get latest version
+- All features from v2.0.13 are identical
+
+---
+
+## 📦 v2.0.13 - Workflow Fix & Clean Release (2025-10-11)
+
+### 🤖 AI Summary
+
+This patch release fixes the npm publish workflow's README update patterns and provides a clean version without the experimental remote-SSH features that were accidentally included in v2.0.11 and v2.0.12. The workflow now correctly updates the README version information during releases, and users get a stable version based on v2.0.10.
+
+### 🐛 Bug Fixes
+
+#### Publish Workflow README Update Fix
+- **Fixed sed patterns** - Workflow now correctly matches and updates README release section
+- **Flexible pattern matching** - Handles different release title formats ("Multi-Provider Revolution" vs "Release Notes")
+- **Correct version display** - README now shows v2.0.13 in both author line and latest release section
+
+#### Clean Version Without Remote-SSH Features
+- **Skipped v2.0.11/v2.0.12** - These versions included experimental remote TTS forwarding features
+- **Based on v2.0.10** - This is a clean release from the stable master branch
+- **No breaking changes** - All existing functionality from v2.0.10 is preserved
+
+### 📝 Technical Changes
+
+**Modified: `.github/workflows/publish.yml`**
+- Updated sed pattern from exact "Release Notes" match to flexible `[^\]]*` pattern
+- Improved pattern to match any title format in release section header
+- Added comment explaining the flexible matching approach
+
+**Modified: `package.json`, `package-lock.json`**
+- Bumped version from 2.0.10 to 2.0.13
+
+### 🔄 Migration Notes
+
+**For All Users:**
+- Update via `/agent-vibes:update` or `npx agentvibes@latest install`
+- No breaking changes - all settings and configurations preserved
+- If you were on v2.0.12, this removes the remote-SSH code
+
+**Deprecation Notice:**
+- v2.0.12 includes experimental features and should be avoided
+- v2.0.13 is the recommended stable version
+
+---
+
 ## 📦 v2.0.10 - GitHub Star Reminder & Provider Fixes (2025-01-10)
 
 ### 🤖 AI Summary

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "agentvibes",
-  "version": "2.0.13",
+  "version": "2.0.15",
   "description": "Now your AI Agents can finally talk back! Professional TTS voice for Claude Code with multi-provider support.",
   "homepage": "https://agentvibes.org",
   "keywords": [

package/src/installer.js

@@ -665,16 +665,93 @@ async function install(options = {}) {
       bmadDetected = true;
     } catch {}
 
+    // Auto-enable BMAD plugin and create activation-instructions if BMAD detected
+    if (bmadDetected) {
+      const pluginsDir = path.join(claudeDir, 'plugins');
+      const enabledFlagPath = path.join(pluginsDir, 'bmad-voices-enabled.flag');
+      const activationInstructionsPath = path.join(claudeDir, 'activation-instructions');
+
+      // Auto-enable the plugin (create the flag file)
+      await fs.mkdir(pluginsDir, { recursive: true });
+      await fs.writeFile(enabledFlagPath, '');
+      console.log(chalk.green('🎤 Auto-enabled BMAD voice plugin'));
+
+      // Only create if doesn't exist (don't overwrite user customizations)
+      try {
+        await fs.access(activationInstructionsPath);
+      } catch {
+        // File doesn't exist - create it
+        const activationContent = `# BMAD Agent Activation Instructions
+
+When a BMAD agent activates, follow these steps EXACTLY:
+
+## STEP 3.5a: Create BMAD Context File (CRITICAL)
+
+**IMMEDIATELY after agent identification, create the context file:**
+
+\`\`\`bash
+echo "$AGENT_ID" > .bmad-agent-context
+\`\`\`
+
+Where \`$AGENT_ID\` is one of:
+- \`pm\` (Product Manager)
+- \`dev\` (Developer)
+- \`qa\` (QA)
+- \`architect\` (Architect)
+- \`po\` (Product Owner)
+- \`analyst\` (Analyst)
+- \`sm\` (Scrum Master)
+- \`ux-expert\` (UX Expert)
+- \`bmad-master\` (BMAD Master)
+- \`bmad-orchestrator\` (Orchestrator)
+
+**Example:**
+\`\`\`bash
+# For Product Manager agent
+echo "pm" > .bmad-agent-context
+\`\`\`
+
+This file allows AgentVibes to:
+1. Detect which BMAD agent is active
+2. Look up the correct voice mapping
+3. Automatically speak questions using the agent's assigned voice
+
+## STEP 10: Clean Up on Exit
+
+**Before exiting the agent, remove the context file:**
+
+\`\`\`bash
+rm -f .bmad-agent-context
+\`\`\`
+
+This ensures voice switching only happens when an agent is active.
+
+## Why This Matters
+
+Without the \`.bmad-agent-context\` file:
+- AgentVibes cannot detect which agent is active
+- Questions won't be spoken automatically
+- Voice switching won't work
+- The BMAD voice plugin becomes non-functional
+
+**This is MANDATORY for BMAD voice integration to work!**
+`;
+        await fs.writeFile(activationInstructionsPath, activationContent);
+        console.log(chalk.green('📝 Created BMAD activation instructions'));
+      }
+    }
+
     if (bmadDetected) {
       console.log(
         boxen(
           chalk.green.bold('🎉 BMAD Detected!\n\n') +
-          chalk.white('AgentVibes BMAD Plugin is automatically enabled!\n') +
-          chalk.gray('Each BMAD agent will now use its assigned voice.\n\n') +
+          chalk.white('✅ BMAD Voice Plugin: AUTO-ENABLED\n') +
+          chalk.gray('Each BMAD agent will automatically use its assigned voice\n') +
+          chalk.gray('and speak when activated!\n\n') +
           chalk.cyan('Commands:\n') +
-          chalk.gray('  • /agent-vibes-bmad status - View agent voices\n') +
-          chalk.gray('  • /agent-vibes-bmad set <agent> <voice> - Customize\n') +
-          chalk.gray('  • /agent-vibes-bmad disable - Turn off plugin'),
+          chalk.gray('  • /agent-vibes:bmad status - View agent voices\n') +
+          chalk.gray('  • /agent-vibes:bmad set <agent> <voice> - Customize\n') +
+          chalk.gray('  • /agent-vibes:bmad disable - Turn off if unwanted'),
           {
             padding: 1,
             margin: 1,

package/templates/activation-instructions-bmad.md

@@ -0,0 +1,54 @@
+# BMAD Agent Activation Instructions
+
+When a BMAD agent activates, follow these steps EXACTLY:
+
+## STEP 3.5a: Create BMAD Context File (CRITICAL)
+
+**IMMEDIATELY after agent identification, create the context file:**
+
+```bash
+echo "$AGENT_ID" > .bmad-agent-context
+```
+
+Where `$AGENT_ID` is one of:
+- `pm` (Product Manager)
+- `dev` (Developer)
+- `qa` (QA)
+- `architect` (Architect)
+- `po` (Product Owner)
+- `analyst` (Analyst)
+- `sm` (Scrum Master)
+- `ux-expert` (UX Expert)
+- `bmad-master` (BMAD Master)
+- `bmad-orchestrator` (Orchestrator)
+
+**Example:**
+```bash
+# For Product Manager agent
+echo "pm" > .bmad-agent-context
+```
+
+This file allows AgentVibes to:
+1. Detect which BMAD agent is active
+2. Look up the correct voice mapping
+3. Automatically speak questions using the agent's assigned voice
+
+## STEP 10: Clean Up on Exit
+
+**Before exiting the agent, remove the context file:**
+
+```bash
+rm -f .bmad-agent-context
+```
+
+This ensures voice switching only happens when an agent is active.
+
+## Why This Matters
+
+Without the `.bmad-agent-context` file:
+- AgentVibes cannot detect which agent is active
+- Questions won't be spoken automatically
+- Voice switching won't work
+- The BMAD voice plugin becomes non-functional
+
+**This is MANDATORY for BMAD voice integration to work!**