agentvibes 2.9.1 → 2.9.2

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

@@ -136,7 +136,18 @@ auto_enable_if_bmad_detected() {
 get_agent_voice() {
     local agent_id="$1"
 
-    # Auto-enable if BMAD is detected
+    # Check for BMAD v6 CSV file first (preferred, loose coupling)
+    # If this exists, use it directly without requiring plugin enable flag
+    local bmad_voice_map=".bmad/_cfg/agent-voice-map.csv"
+    if [[ -f "$bmad_voice_map" ]]; then
+        # Read from BMAD's standard _cfg directory
+        # CSV format: agent_id,voice_name
+        local voice=$(grep "^$agent_id," "$bmad_voice_map" | cut -d',' -f2)
+        echo "$voice"
+        return
+    fi
+
+    # Auto-enable if BMAD is detected (for legacy markdown config)
     auto_enable_if_bmad_detected
 
     if [[ ! -f "$ENABLED_FLAG" ]]; then
@@ -144,6 +155,7 @@ get_agent_voice() {
         return
     fi
 
+    # Fallback to legacy markdown config file
     if [[ ! -f "$VOICE_CONFIG_FILE" ]]; then
         echo ""  # Plugin file missing
         return

package/BMAD_PR_TESTING_INSTRUCTIONS.md

@@ -0,0 +1,130 @@
+# 🎙️ Testing Instructions for AgentVibes Party Mode PR
+
+## Prerequisites
+- Node.js and npm installed
+- Git installed
+- Fresh terminal session
+
+## Quick Test (5-10 minutes)
+
+### Step 1: Fork and Clone BMAD
+```bash
+# Fork the BMAD repo on GitHub first, then:
+git clone https://github.com/YOUR-USERNAME/BMAD-METHOD.git
+cd BMAD-METHOD
+```
+
+### Step 2: Merge the PR Branch
+```bash
+# Add the upstream remote
+git remote add upstream https://github.com/bmad-code-org/BMAD-METHOD.git
+
+# Fetch and merge the PR
+git fetch upstream pull/934/head:agentvibes-party-mode
+git checkout agentvibes-party-mode
+```
+
+### Step 3: Install BMAD from Your Fork
+```bash
+# Navigate to the CLI installer directory
+cd tools/cli
+
+# Install dependencies
+npm install
+
+# Link it globally so you can run 'bmad' command
+npm link
+
+# Navigate to where you want to create your BMAD project
+cd ~
+mkdir my-bmad-test
+cd my-bmad-test
+
+# Run the BMAD installer (now using your forked version with the PR)
+bmad install
+
+# When prompted about AgentVibes TTS:
+# - Answer "Yes" to enable TTS for agents
+# - Answer "Yes" to assign unique voices for party mode
+```
+
+### Step 4: Install AgentVibes (if not already installed)
+```bash
+# If you don't have AgentVibes yet:
+npx agentvibes@latest install
+
+# Follow the installer:
+# - Choose a TTS provider (ElevenLabs or Piper)
+# - For Piper (free): it will auto-download voices including 16Speakers
+# - For ElevenLabs: you'll need an API key
+```
+
+### Step 5: Test Party Mode! 🎉
+```bash
+# Start a Claude Code session in your BMAD project directory (my-bmad-test)
+# Then run party mode:
+/bmad:core:workflows:party-mode
+
+# You should hear each BMAD agent speak with their own unique voice!
+```
+
+## What to Test
+
+### ✅ Installation Flow
+- [ ] BMAD installer detects AgentVibes
+- [ ] Installer prompts about TTS setup
+- [ ] Voice assignment file `.bmad/agent-voice-assignments.json` is created
+- [ ] All agents have TTS markers injected
+
+### ✅ Party Mode Voices
+- [ ] Each agent speaks with a different voice
+- [ ] Voices match agent personalities (e.g., architect sounds professional)
+- [ ] No voice overlap between agents
+- [ ] TTS works smoothly during multi-agent discussions
+
+### ✅ Fallback Behavior
+- [ ] If you skip TTS setup, agents still work normally (no errors)
+- [ ] Party mode works without TTS (silent mode)
+
+## Troubleshooting
+
+**"bmad command not found"**
+- Make sure you ran `npm link` in `BMAD-METHOD/tools/cli`
+- Try running with full path: `node tools/cli/index.js install` from BMAD-METHOD root
+
+**"No TTS heard during party mode"**
+- Check `.claude/hooks/play-tts.sh` exists
+- Verify `.bmad/agent-voice-assignments.json` was created
+- Try: `/agent-vibes:whoami` to check active voice
+
+**"All agents sound the same"**
+- Check `.bmad/agent-voice-assignments.json` has unique voices per agent
+- For Piper: ensure 16Speakers model downloaded (has 16 voices)
+- Try: `/agent-vibes:list` to see available voices
+
+**"Installation fails"**
+- Make sure you're on the PR branch: `git branch` (should show `agentvibes-party-mode`)
+- Try clean install in tools/cli: `rm -rf node_modules package-lock.json && npm install`
+
+## Expected Output
+
+When party mode works correctly, you'll see something like:
+```
+🎭 architect speaking... (Voice: matthew)
+🎭 dev speaking... (Voice: ryan)
+🎭 pm speaking... (Voice: amy)
+```
+
+Each agent's responses will be spoken aloud with their assigned voice!
+
+## Report Issues
+
+Please comment on the PR with:
+- ✅ What worked
+- ❌ What didn't work
+- 📋 Your OS (Linux/Mac/Windows)
+- 🎤 TTS provider used (Piper/ElevenLabs)
+
+---
+
+**PR Link:** https://github.com/bmad-code-org/BMAD-METHOD/pull/934

package/package.json

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

package/test/piper-installation.bats

@@ -0,0 +1,142 @@
+#!/usr/bin/env bats
+#
+# File: test/piper-installation.bats
+#
+# Piper TTS Installation Tests
+# Tests the complete Piper installation flow including voice downloads
+#
+
+setup() {
+  # Test environment setup
+  export AGENTVIBES_TEST_MODE="true"
+
+  # For integration tests, use real HOME to allow Piper installation
+  # For unit tests, use temp HOME for isolation
+  if [ -z "$PIPER_INTEGRATION_TEST" ]; then
+    export HOME="${BATS_TEST_TMPDIR}/home"
+    mkdir -p "$HOME"
+  fi
+  # else: use real $HOME for integration tests
+
+  # Create temporary project directory
+  export TEST_PROJECT_DIR="${BATS_TEST_TMPDIR}/agentvibes-test"
+  mkdir -p "$TEST_PROJECT_DIR"
+  cd "$TEST_PROJECT_DIR"
+
+  # Copy necessary files for installation
+  cp -r "$BATS_TEST_DIRNAME/../.claude" "$TEST_PROJECT_DIR/"
+
+  # Expected voice models
+  export EXPECTED_VOICES=(
+    "en_US-lessac-medium"
+    "en_US-amy-medium"
+    "en_US-joe-medium"
+    "en_US-ryan-high"
+    "en_US-libritts-high"
+    "16Speakers"
+  )
+}
+
+teardown() {
+  # Cleanup test environment
+  cd "$BATS_TEST_DIRNAME"
+  rm -rf "$TEST_PROJECT_DIR"
+
+  # Only remove temp HOME for unit tests, not integration tests
+  if [ -z "$PIPER_INTEGRATION_TEST" ]; then
+    rm -rf "$HOME"
+  fi
+}
+
+@test "Piper installer script exists and is executable" {
+  [ -f "$TEST_PROJECT_DIR/.claude/hooks/piper-installer.sh" ]
+  [ -x "$TEST_PROJECT_DIR/.claude/hooks/piper-installer.sh" ]
+}
+
+@test "Piper voice downloader script exists and is executable" {
+  [ -f "$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh" ]
+  [ -x "$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh" ]
+}
+
+@test "Piper voice manager script exists" {
+  [ -f "$TEST_PROJECT_DIR/.claude/hooks/piper-voice-manager.sh" ]
+}
+
+@test "Non-interactive flag is supported in piper-installer.sh" {
+  run grep -q "NON_INTERACTIVE" "$TEST_PROJECT_DIR/.claude/hooks/piper-installer.sh"
+  [ "$status" -eq 0 ]
+}
+
+@test "Yes flag is supported in piper-download-voices.sh" {
+  run grep -q "AUTO_YES" "$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh"
+  [ "$status" -eq 0 ]
+}
+
+@test "Download script has explicit exit 0" {
+  run grep -q "exit 0" "$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh"
+  [ "$status" -eq 0 ]
+}
+
+@test "All expected voices are in COMMON_VOICES array" {
+  for voice in "${EXPECTED_VOICES[@]}"; do
+    run grep -q "\"$voice\"" "$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh"
+    [ "$status" -eq 0 ]
+  done
+}
+
+@test "16Speakers model is included in download list" {
+  run grep -q "16Speakers" "$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh"
+  [ "$status" -eq 0 ]
+}
+
+@test "Curl timeouts are configured in voice manager" {
+  run grep -q "\-\-connect-timeout" "$TEST_PROJECT_DIR/.claude/hooks/piper-voice-manager.sh"
+  [ "$status" -eq 0 ]
+
+  run grep -q "\-\-max-time" "$TEST_PROJECT_DIR/.claude/hooks/piper-voice-manager.sh"
+  [ "$status" -eq 0 ]
+}
+
+@test "Piper installer passes --non-interactive flag to voice downloader" {
+  run grep -q "piper-download-voices.sh.*--yes" "$TEST_PROJECT_DIR/.claude/hooks/piper-installer.sh"
+  [ "$status" -eq 0 ]
+}
+
+# Integration test - only runs if PIPER_INTEGRATION_TEST is set
+@test "Full Piper installation with voice downloads (integration)" {
+  if [ -z "$PIPER_INTEGRATION_TEST" ]; then
+    skip "Set PIPER_INTEGRATION_TEST=1 to run integration tests"
+  fi
+
+  # Run installer in non-interactive mode
+  run bash "$TEST_PROJECT_DIR/.claude/hooks/piper-installer.sh" --non-interactive
+  echo "Installer output: $output"
+  [ "$status" -eq 0 ]
+
+  # Verify Piper is installed
+  command -v piper || skip "Piper not in PATH after installation"
+
+  # Check voice storage directory
+  VOICE_DIR="$HOME/.claude/piper-voices"
+  [ -d "$VOICE_DIR" ]
+
+  # Verify at least some voices downloaded
+  voice_count=$(find "$VOICE_DIR" -name "*.onnx" | wc -l)
+  [ "$voice_count" -gt 0 ]
+
+  # Verify 16Speakers model specifically
+  [ -f "$VOICE_DIR/16Speakers.onnx" ]
+  [ -f "$VOICE_DIR/16Speakers.onnx.json" ]
+}
+
+@test "Voice download script handles failures gracefully" {
+  # Test that the script returns 0 even with failures
+  # This is a mock test - in real scenario we'd simulate network failures
+
+  run bash -c "source '$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh' 2>&1 | tail -1"
+  echo "Output: $output"
+
+  # Script should exit 0 (checked via exit code or explicit exit statement)
+  [ -f "$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh" ]
+  tail -5 "$TEST_PROJECT_DIR/.claude/hooks/piper-download-voices.sh" | grep -q "exit 0"
+}