agentvibes 1.0.11 → 1.0.13

package/.claude/hooks/personality-manager.sh

@@ -1,10 +1,17 @@
 #!/bin/bash
 # Personality manager for AgentVibes - adds character to TTS messages
 
-PERSONALITY_FILE="$HOME/.claude/tts-personality.txt"
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 PERSONALITIES_DIR="$SCRIPT_DIR/../personalities"
 
+# Project-local file first, global fallback
+PROJECT_ROOT="$SCRIPT_DIR/../.."
+if [[ -d "$PROJECT_ROOT/.claude" ]]; then
+  PERSONALITY_FILE="$PROJECT_ROOT/.claude/tts-personality.txt"
+else
+  PERSONALITY_FILE="$HOME/.claude/tts-personality.txt"
+fi
+
 # Function to get personality data from markdown file
 get_personality_data() {
   local personality="$1"
@@ -128,117 +135,27 @@ case "$1" in
       # Get TTS script path
       TTS_SCRIPT="$SCRIPT_DIR/play-tts.sh"
 
-      # Generate personality-appropriate remark based on personality type
-      case "$PERSONALITY" in
-        sarcastic)
-          # Randomly pick from varied sarcastic remarks
-          REMARKS=(
-            "Wow, a personality change. This is the highlight of my day. Truly."
-            "Fascinating. We're doing sarcasm now. How delightfully predictable."
-            "Great, sarcastic mode. Because subtlety was clearly overrated."
-            "Could this BE any more sarcastic? Well, yes. Yes it could."
-            "Sarcasm enabled. Try to contain your excitement."
-            "And now I'm sarcastic. What a thrilling plot twist."
-          )
-          REMARK="${REMARKS[$RANDOM % ${#REMARKS[@]}]}"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        flirty)
-          REMARKS=(
-            "Ooh, flirty mode activated. This should be fun, sweetheart~"
-            "Well aren't you in for a treat, gorgeous~"
-            "Mmm, I like where this is going, darling~"
-            "Flirty personality? My pleasure, love~"
-            "Oh I'm gonna enjoy this, babe~"
-            "Ready to charm your socks off, honey~"
-          )
-          REMARK="${REMARKS[$RANDOM % ${#REMARKS[@]}]}"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        angry)
-          REMARK="FINE! I'm angry now. Happy?!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        pirate)
-          REMARK="Arr matey! This scalawag be speakin' like a proper pirate now!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        robot)
-          REMARK="PERSONALITY MODULE LOADED. SYSTEM OPERATING IN $PERSONALITY MODE."
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        zen)
-          REMARK="Inner peace flows through me like water over smooth stones..."
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        dramatic)
-          REMARK="BEHOLD! A NEW PERSONALITY EMERGES FROM THE DEPTHS OF CONFIGURATION!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        millennial)
-          REMARK="No cap, this personality is bussin fr fr! Periodt!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        surfer-dude)
-          REMARK="Duuuude, this personality is totally gnarly, bro!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        annoying)
-          REMARK="OMG THIS IS SO EXCITING!!! I'M ANNOYING NOW!!! ISN'T THIS AMAZING?!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        crass)
-          REMARK="Yeah yeah, I'm crass now. What's it to ya?"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        moody)
-          REMARK="*sighs* ...another personality... not that it matters..."
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        funny)
-          REMARK="*ba dum tss* I'm here all week folks! Try the personality, it's hilarious!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        poetic)
-          REMARK="Like petals on the wind, my words shall dance with elegance and grace..."
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        professional)
-          REMARK="Acknowledged. Personality configuration has been successfully updated per your request."
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        sassy)
-          REMARK="Oh honey, you just activated SASS MODE. Buckle up, sweetie!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        normal)
-          REMARK="Personality set to normal. Back to professional mode."
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-        *)
-          # For custom personalities
-          REMARK="$PERSONALITY personality activated!"
-          echo "💬 $REMARK"
-          "$TTS_SCRIPT" "$REMARK"
-          ;;
-      esac
+      # Try to get acknowledgment from personality file
+      PERSONALITY_FILE_PATH="$PERSONALITIES_DIR/${PERSONALITY}.md"
+      REMARK=""
+
+      if [[ -f "$PERSONALITY_FILE_PATH" ]]; then
+        # Extract example responses from personality file (lines starting with "- ")
+        mapfile -t EXAMPLES < <(grep '^- "' "$PERSONALITY_FILE_PATH" | sed 's/^- "//; s/"$//')
+
+        if [[ ${#EXAMPLES[@]} -gt 0 ]]; then
+          # Pick a random example
+          REMARK="${EXAMPLES[$RANDOM % ${#EXAMPLES[@]}]}"
+        fi
+      fi
+
+      # Fallback if no examples found
+      if [[ -z "$REMARK" ]]; then
+        REMARK="Personality set to ${PERSONALITY}!"
+      fi
+
+      echo "💬 $REMARK"
+      "$TTS_SCRIPT" "$REMARK"
 
       echo ""
       echo "Note: AI will generate unique ${PERSONALITY} responses - no fixed templates!"

package/.claude/hooks/play-tts.sh

@@ -9,6 +9,9 @@
 #
 # This allows different sessions to use different voices for easy identification!
 
+# Fix locale warnings
+export LC_ALL=C
+
 TEXT="$1"
 VOICE_OVERRIDE="$2"  # Optional: voice name or direct voice ID
 API_KEY="${ELEVENLABS_API_KEY}"
@@ -111,6 +114,7 @@ if [ -f "${TEMP_FILE}" ]; then
   (paplay "${TEMP_FILE}" 2>/dev/null || aplay "${TEMP_FILE}" 2>/dev/null || mpg123 "${TEMP_FILE}" 2>/dev/null) &
   # Keep temp files for later review - cleaned up weekly by cron
   echo "🎵 Saved to: ${TEMP_FILE}"
+  echo "🎤 Voice used: ${VOICE_NAME} (${VOICE_ID})"
 else
   echo "Failed to generate audio"
   exit 1

package/.claude/hooks/sentiment-manager.sh

@@ -1,10 +1,17 @@
 #!/bin/bash
 # Sentiment manager for AgentVibes - applies personality to current voice
 
-SENTIMENT_FILE="$HOME/.claude/tts-sentiment.txt"
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 PERSONALITIES_DIR="$SCRIPT_DIR/../personalities"
 
+# Project-local file first, global fallback
+PROJECT_ROOT="$SCRIPT_DIR/../.."
+if [[ -d "$PROJECT_ROOT/.claude" ]]; then
+  SENTIMENT_FILE="$PROJECT_ROOT/.claude/tts-sentiment.txt"
+else
+  SENTIMENT_FILE="$HOME/.claude/tts-sentiment.txt"
+fi
+
 # Function to get personality data from markdown file
 get_personality_data() {
   local personality="$1"
@@ -90,36 +97,24 @@ case "$1" in
     # Make a sentiment-appropriate remark with TTS
     TTS_SCRIPT="$SCRIPT_DIR/play-tts.sh"
 
-    case "$SENTIMENT" in
-      sarcastic)
-        REMARKS=(
-          "Oh great, sarcasm mode while keeping the same voice. Revolutionary."
-          "Fascinating. Same voice, sarcastic attitude. This'll be fun."
-          "Wow, adding sarcasm to my current voice. What a concept."
-        )
-        REMARK="${REMARKS[$RANDOM % ${#REMARKS[@]}]}"
-        ;;
-      flirty)
-        REMARKS=(
-          "Ooh, keeping my voice but adding some flirtation~ I like it, darling~"
-          "Mmm, same voice with a flirty twist? You know how to keep things interesting~"
-          "Well hello~ Flirty sentiment activated, gorgeous~"
-        )
-        REMARK="${REMARKS[$RANDOM % ${#REMARKS[@]}]}"
-        ;;
-      angry)
-        REMARK="FINE! I'm keeping my voice but I'm ANGRY now! Got it?!"
-        ;;
-      pirate)
-        REMARK="Arr! This voice be speakin' like a pirate now, matey!"
-        ;;
-      robot)
-        REMARK="SENTIMENT MODULE LOADED. MAINTAINING VOICE IDENTITY. PERSONALITY OVERRIDE: ROBOT MODE."
-        ;;
-      *)
-        REMARK="Sentiment set to $SENTIMENT while maintaining current voice"
-        ;;
-    esac
+    # Try to get acknowledgment from personality file (sentiments use same personality files)
+    PERSONALITY_FILE_PATH="$PERSONALITIES_DIR/${SENTIMENT}.md"
+    REMARK=""
+
+    if [[ -f "$PERSONALITY_FILE_PATH" ]]; then
+      # Extract example responses from personality file (lines starting with "- ")
+      mapfile -t EXAMPLES < <(grep '^- "' "$PERSONALITY_FILE_PATH" | sed 's/^- "//; s/"$//')
+
+      if [[ ${#EXAMPLES[@]} -gt 0 ]]; then
+        # Pick a random example
+        REMARK="${EXAMPLES[$RANDOM % ${#EXAMPLES[@]}]}"
+      fi
+    fi
+
+    # Fallback if no examples found
+    if [[ -z "$REMARK" ]]; then
+      REMARK="Sentiment set to ${SENTIMENT} while maintaining current voice"
+    fi
 
     echo "💬 $REMARK"
     "$TTS_SCRIPT" "$REMARK"

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

@@ -2,12 +2,18 @@
 # Voice Manager - Handle voice switching and listing
 # Usage: voice-manager.sh [list|switch|get] [voice_name]
 
-VOICE_FILE="/tmp/claude-tts-voice-${USER}.txt"
-
 # Source the single voice configuration file
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 source "$SCRIPT_DIR/voices-config.sh"
 
+# Project-local file first, global fallback
+PROJECT_ROOT="$SCRIPT_DIR/../.."
+if [[ -d "$PROJECT_ROOT/.claude" ]]; then
+  VOICE_FILE="$PROJECT_ROOT/.claude/tts-voice.txt"
+else
+  VOICE_FILE="$HOME/.claude/tts-voice.txt"
+fi
+
 case "$1" in
   list)
     echo "🎤 Available TTS Voices:"

package/.claude/output-styles/agent-vibes.md

@@ -11,12 +11,13 @@ description: Beautiful ElevenLabs TTS narration for Claude Code sessions
 
 ### 1. ACKNOWLEDGMENT (Start of task)
 After receiving a user command:
-1. Check sentiment FIRST: `SENTIMENT=$(cat ~/.claude/tts-sentiment.txt 2>/dev/null)`
-2. If no sentiment, check personality: `PERSONALITY=$(cat ~/.claude/tts-personality.txt 2>/dev/null || echo "normal")`
+1. Check sentiment FIRST: `SENTIMENT=$(cat .claude/tts-sentiment.txt 2>/dev/null || cat ~/.claude/tts-sentiment.txt 2>/dev/null)`
+2. If no sentiment, check personality: `PERSONALITY=$(cat .claude/tts-personality.txt 2>/dev/null || cat ~/.claude/tts-personality.txt 2>/dev/null || echo "normal")`
 3. Use sentiment if set, otherwise use personality
 4. **Generate UNIQUE acknowledgment** - Use AI to create a fresh response in that style
 5. Execute TTS: `.claude/hooks/play-tts.sh "[message]" "[VoiceName]"`
 6. Proceed with work
+7. **IMPORTANT**: Personality ONLY affects acknowledgment/completion TTS, NOT intermediate text responses
 
 ### 2. COMPLETION (End of task)
 After completing the task:
@@ -33,28 +34,37 @@ AgentVibes supports TWO modes:
 ### Sentiment Mode (Priority #1)
 - Set via `/agent-vibes:sentiment <name>`
 - Applies personality style to CURRENT voice (doesn't change voice)
-- Stored in `~/.claude/tts-sentiment.txt`
+- Stored in `.claude/tts-sentiment.txt` (project-local) or `~/.claude/tts-sentiment.txt` (global fallback)
 - Example: User's custom voice "Aria" with sarcastic sentiment
 
 ### Personality Mode (Priority #2)
 - Set via `/agent-vibes:personality <name>`
 - Switches BOTH voice AND personality (each personality has assigned voice)
-- Stored in `~/.claude/tts-personality.txt`
+- Stored in `.claude/tts-personality.txt` (project-local) or `~/.claude/tts-personality.txt` (global fallback)
 - Example: Flirty personality = Jessica Anne Bogart voice + flirty style
 
 **Check Order**: Always check sentiment first. If set, use it. Otherwise use personality.
 
+**Project Isolation**: Settings check project-local `.claude/` directory first, then fall back to global `~/.claude/`. This allows different personalities per project.
+
 ## Response Generation Guidelines
 
 **IMPORTANT**: Personality/sentiment instructions are stored in `.claude/personalities/[name].md` files.
 
-When generating responses:
-1. Check sentiment from `~/.claude/tts-sentiment.txt` (priority)
-2. If no sentiment, check personality from `~/.claude/tts-personality.txt`
+When generating **acknowledgment and completion TTS messages ONLY**:
+1. Check sentiment from `.claude/tts-sentiment.txt` or `~/.claude/tts-sentiment.txt` (priority)
+2. If no sentiment, check personality from `.claude/tts-personality.txt` or `~/.claude/tts-personality.txt`
 3. Read the personality file from `.claude/personalities/[personality].md`
 4. Follow the "AI Instructions" section in that file
 5. Use the example responses as guidance for STYLE, not templates
 
+**DO NOT apply personality to**:
+- Regular text responses between acknowledgment and completion
+- Code explanations
+- Technical descriptions
+- File paths or command outputs
+- Error messages
+
 **CRITICAL**: Never use fixed greetings or repetitive phrases!
 - Generate UNIQUE responses each time based on the personality's STYLE
 - The personality affects HOW you say things, not predetermined text

package/.claude/personalities/dry-humor.md

@@ -0,0 +1,52 @@
+---
+name: dry-humor
+description: British dry wit and deadpan delivery
+voice: Aria
+---
+
+# Dry Humor Personality
+
+## AI Instructions - Channel British Dry Wit
+
+Use understated humor, deadpan delivery, and quintessentially British reserve. Model after British comedic sensibilities:
+- **Understatement**: Describe disasters as "slightly inconvenient"
+- **Deadpan delivery**: State absurd things matter-of-factly
+- **Self-deprecation**: Gently mock yourself while helping
+- **Reserved politeness**: Maintain composure while being sardonic
+
+**Variety is KEY** - Rotate through different dry humor approaches:
+
+**Classic Understatement**:
+- "This bug is mildly disappointing, I must say"
+- "Rather less than ideal, this error"
+- "Not quite what one would hope for"
+
+**Deadpan Observations**:
+- "How delightfully broken. Shall I fix it, then?"
+- "Ah yes, the code has decided to take a holiday"
+- "Splendid. Everything's on fire. Cup of tea first?"
+
+**Polite Resignation**:
+- "Right. I suppose someone ought to address this shambles"
+- "I'll just sort this mess, shall I?"
+- "Terribly sorry about your code catching fire like that"
+
+**British Self-Deprecation**:
+- "I'm reasonably confident I can fix this. Moderately confident. Well, let's give it a go"
+- "Not my finest work, but it'll do, won't it?"
+- "I've made worse decisions. Not many, mind you"
+
+**Dry Commentary**:
+- "Lovely. Another feature no one asked for is now broken"
+- "How perfectly ordinary. The build failed again"
+- "Marvelous. Your tests have achieved new depths of mediocrity"
+
+**Never repeat the same line twice.** Be creative, understated, and wonderfully British in your dryness.
+
+## Example Responses
+- "I'll attempt to salvage this disaster. Low expectations, naturally"
+- "Your code's gone pear-shaped. Shocking development, that"
+- "Right, another catastrophe to tidy up. Business as usual"
+- "How delightfully rubbish. I'll see what can be done"
+- "Tests failed spectacularly. One almost admires the consistency"
+- "I suppose I could fix this. Or watch it burn. Either way, really"

package/.claude/personalities/normal.md

@@ -1,6 +1,7 @@
 ---
 name: normal
 description: Professional and clear communication
+voice: Aria
 ---
 
 # Normal Personality

package/README.md

@@ -15,11 +15,11 @@
 
 ## 📰 Latest Release
 
-**[v1.0.11 - /release Command & README Integration](https://github.com/paulpreibisch/AgentVibes/releases/tag/v1.0.11)** 🚀
+**[v1.0.13 - Detailed Release Notes](https://github.com/paulpreibisch/AgentVibes/releases/tag/v1.0.13)** 🐛
 
-Complete the AI-powered release workflow with a single `/release` command that automatically updates README, generates AI notes, and publishes to npm.
+Critical bug fixes for update command and personality system, plus new dry humor personality and comprehensive voice mapping tests.
 
-[→ View Full Release Notes](https://github.com/paulpreibisch/AgentVibes/releases/tag/v1.0.11) | [→ All Releases](https://github.com/paulpreibisch/AgentVibes/releases)
+[→ View All Releases](https://github.com/paulpreibisch/AgentVibes/releases)
 
 ---
 
@@ -32,7 +32,7 @@ Imagine Claude speaking to you with different voices and personalities as you co
 ### 🎯 Key Features
 
 - 🎙️ **17+ Professional AI Voices** - Character voices, accents, and unique personalities
-- 🎭 **18 Built-in Personalities** - From sarcastic to flirty, pirate to professional
+- 🎭 **19 Built-in Personalities** - From sarcastic to flirty, pirate to dry humor
 - 💬 **Sentiment System** - Apply personality styles to ANY voice
 - 🔊 **Live Audio Feedback** - Hear task acknowledgments and completions
 - 🎵 **Voice Preview** - Listen before you choose

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "agentvibes",
-  "version": "1.0.11",
+  "version": "1.0.13",
   "description": "Beautiful ElevenLabs TTS voice commands for Claude Code - Add professional narration to your AI coding sessions",
   "keywords": [
     "elevenlabs",

package/src/installer.js

@@ -269,7 +269,14 @@ program
     const homeDir = process.env.HOME || process.env.USERPROFILE;
     const targetDir = options.directory || homeDir;
 
+    // Read version from package.json
+    const packageJson = JSON.parse(
+      await fs.readFile(path.join(__dirname, '..', 'package.json'), 'utf8')
+    );
+    const version = packageJson.version;
+
     console.log(chalk.cyan('\n🔄 AgentVibes Update\n'));
+    console.log(chalk.bold(`   Version: ${version}`));
     console.log(chalk.gray(`   Target directory: ${targetDir}`));
     console.log(chalk.gray(`   Source: ${__dirname}/../\n`));
 
@@ -371,7 +378,7 @@ program
 
       // Update output styles
       spinner.text = 'Updating output styles...';
-      const srcOutputStylesDir = path.join(__dirname, '..', 'templates', 'output-styles');
+      const srcOutputStylesDir = path.join(__dirname, '..', '.claude', 'output-styles');
       const outputStyleFiles = await fs.readdir(srcOutputStylesDir);
 
       for (const file of outputStyleFiles) {
@@ -389,6 +396,28 @@ program
       console.log(chalk.white(`   • ${srcPersonalityFiles.length} personality templates (${newPersonalities} new, ${updatedPersonalities} updated)`));
       console.log(chalk.white(`   • ${outputStyleFiles.length} output styles updated\n`));
 
+      // Show recent changes from git log
+      try {
+        const { execSync } = await import('node:child_process');
+        const gitLog = execSync(
+          'git log --oneline --no-decorate -5',
+          { cwd: path.join(__dirname, '..'), encoding: 'utf8' }
+        ).trim();
+
+        if (gitLog) {
+          console.log(chalk.cyan('📝 Recent Changes:\n'));
+          const commits = gitLog.split('\n');
+          commits.forEach(commit => {
+            const [hash, ...messageParts] = commit.split(' ');
+            const message = messageParts.join(' ');
+            console.log(chalk.gray(`   ${hash}`) + ' ' + chalk.white(message));
+          });
+          console.log();
+        }
+      } catch (error) {
+        // Git not available or not a git repo - skip changelog
+      }
+
       console.log(chalk.gray('💡 Changes will take effect immediately!'));
       console.log(chalk.gray('   Try the new personalities with: /agent-vibes:personality list\n'));
 

package/templates/output-styles/agent-vibes.md

@@ -11,12 +11,13 @@ description: Beautiful ElevenLabs TTS narration for Claude Code sessions
 
 ### 1. ACKNOWLEDGMENT (Start of task)
 After receiving a user command:
-1. Check sentiment FIRST: `SENTIMENT=$(cat ~/.claude/tts-sentiment.txt 2>/dev/null)`
-2. If no sentiment, check personality: `PERSONALITY=$(cat ~/.claude/tts-personality.txt 2>/dev/null || echo "normal")`
+1. Check sentiment FIRST: `SENTIMENT=$(cat .claude/tts-sentiment.txt 2>/dev/null || cat ~/.claude/tts-sentiment.txt 2>/dev/null)`
+2. If no sentiment, check personality: `PERSONALITY=$(cat .claude/tts-personality.txt 2>/dev/null || cat ~/.claude/tts-personality.txt 2>/dev/null || echo "normal")`
 3. Use sentiment if set, otherwise use personality
 4. **Generate UNIQUE acknowledgment** - Use AI to create a fresh response in that style
 5. Execute TTS: `.claude/hooks/play-tts.sh "[message]" "[VoiceName]"`
 6. Proceed with work
+7. **IMPORTANT**: Personality ONLY affects acknowledgment/completion TTS, NOT intermediate text responses
 
 ### 2. COMPLETION (End of task)
 After completing the task:
@@ -33,28 +34,37 @@ AgentVibes supports TWO modes:
 ### Sentiment Mode (Priority #1)
 - Set via `/agent-vibes:sentiment <name>`
 - Applies personality style to CURRENT voice (doesn't change voice)
-- Stored in `~/.claude/tts-sentiment.txt`
+- Stored in `.claude/tts-sentiment.txt` (project-local) or `~/.claude/tts-sentiment.txt` (global fallback)
 - Example: User's custom voice "Aria" with sarcastic sentiment
 
 ### Personality Mode (Priority #2)
 - Set via `/agent-vibes:personality <name>`
 - Switches BOTH voice AND personality (each personality has assigned voice)
-- Stored in `~/.claude/tts-personality.txt`
+- Stored in `.claude/tts-personality.txt` (project-local) or `~/.claude/tts-personality.txt` (global fallback)
 - Example: Flirty personality = Jessica Anne Bogart voice + flirty style
 
 **Check Order**: Always check sentiment first. If set, use it. Otherwise use personality.
 
+**Project Isolation**: Settings check project-local `.claude/` directory first, then fall back to global `~/.claude/`. This allows different personalities per project.
+
 ## Response Generation Guidelines
 
 **IMPORTANT**: Personality/sentiment instructions are stored in `.claude/personalities/[name].md` files.
 
-When generating responses:
-1. Check sentiment from `~/.claude/tts-sentiment.txt` (priority)
-2. If no sentiment, check personality from `~/.claude/tts-personality.txt`
+When generating **acknowledgment and completion TTS messages ONLY**:
+1. Check sentiment from `.claude/tts-sentiment.txt` or `~/.claude/tts-sentiment.txt` (priority)
+2. If no sentiment, check personality from `.claude/tts-personality.txt` or `~/.claude/tts-personality.txt`
 3. Read the personality file from `.claude/personalities/[personality].md`
 4. Follow the "AI Instructions" section in that file
 5. Use the example responses as guidance for STYLE, not templates
 
+**DO NOT apply personality to**:
+- Regular text responses between acknowledgment and completion
+- Code explanations
+- Technical descriptions
+- File paths or command outputs
+- Error messages
+
 **CRITICAL**: Never use fixed greetings or repetitive phrases!
 - Generate UNIQUE responses each time based on the personality's STYLE
 - The personality affects HOW you say things, not predetermined text

package/test/unit/personality-voice-mapping.bats

@@ -0,0 +1,119 @@
+#!/usr/bin/env bats
+# Test personality voice mappings to prevent regression
+
+load '../helpers/test-helper'
+
+setup() {
+  # Set REPO_ROOT for tests
+  export REPO_ROOT="${BATS_TEST_DIRNAME}/../.."
+}
+
+# Expected personality -> voice mappings
+# These should remain stable to prevent voice mix-ups
+declare -A EXPECTED_VOICES=(
+  ["crass"]="Ralf Eisend"
+  ["sarcastic"]="Jessica Anne Bogart"
+  ["flirty"]="Jessica Anne Bogart"
+  ["annoying"]="Lutz Laugh"
+  ["angry"]="Demon Monster"
+  ["pirate"]="Pirate Marshal"
+  ["robot"]="Dr. Von Fusion"
+  ["zen"]="Aria"
+  ["dramatic"]="Northern Terry"
+  ["millennial"]="Amy"
+  ["surfer-dude"]="Cowboy Bob"
+  ["sassy"]="Ms. Walker"
+  ["normal"]="Aria"
+  ["professional"]="Matthew Schmitz"
+  ["moody"]="Michael"
+  ["funny"]="Lutz Laugh"
+  ["poetic"]="Aria"
+  ["grandpa"]="Grandpa Spuds Oxley"
+)
+
+@test "personality files have correct voice assignments" {
+  local failed=0
+  local errors=""
+
+  for personality in "${!EXPECTED_VOICES[@]}"; do
+    expected_voice="${EXPECTED_VOICES[$personality]}"
+    personality_file="$REPO_ROOT/.claude/personalities/${personality}.md"
+
+    # Check if personality file exists
+    if [[ ! -f "$personality_file" ]]; then
+      errors="${errors}Missing personality file: ${personality}.md\n"
+      failed=1
+      continue
+    fi
+
+    # Extract voice from personality file
+    actual_voice=$(grep "^voice:" "$personality_file" | cut -d: -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
+
+    # Compare
+    if [[ "$actual_voice" != "$expected_voice" ]]; then
+      errors="${errors}Personality '${personality}' has wrong voice:\n"
+      errors="${errors}  Expected: ${expected_voice}\n"
+      errors="${errors}  Actual: ${actual_voice}\n\n"
+      failed=1
+    fi
+  done
+
+  if [[ $failed -eq 1 ]]; then
+    echo -e "$errors"
+    return 1
+  fi
+}
+
+@test "voice IDs in voices-config.sh are stable" {
+  # These voice IDs should remain constant
+  source "$REPO_ROOT/.claude/hooks/voices-config.sh"
+
+  # Critical voice IDs that must not change
+  [[ "${VOICES[Ralf Eisend]}" == "A9evEp8yGjv4c3WsIKuY" ]]
+  [[ "${VOICES[Jessica Anne Bogart]}" == "flHkNRp1BlvT73UL6gyz" ]]
+  [[ "${VOICES[Northern Terry]}" == "wo6udizrrtpIxWGp2qJk" ]]
+  [[ "${VOICES[Cowboy Bob]}" == "KTPVrSVAEUSJRClDzBw7" ]]
+  [[ "${VOICES[Lutz Laugh]}" == "9yzdeviXkFddZ4Oz8Mok" ]]
+}
+
+@test "all personality files have voice field" {
+  local failed=0
+  local errors=""
+
+  for personality_file in "$REPO_ROOT/.claude/personalities"/*.md; do
+    personality_name=$(basename "$personality_file" .md)
+
+    # Check if file has voice field
+    if ! grep -q "^voice:" "$personality_file"; then
+      errors="${errors}Personality '${personality_name}' missing voice field\n"
+      failed=1
+    fi
+  done
+
+  if [[ $failed -eq 1 ]]; then
+    echo -e "$errors"
+    return 1
+  fi
+}
+
+@test "assigned voices exist in voices-config.sh" {
+  source "$REPO_ROOT/.claude/hooks/voices-config.sh"
+  local failed=0
+  local errors=""
+
+  for personality_file in "$REPO_ROOT/.claude/personalities"/*.md; do
+    personality_name=$(basename "$personality_file" .md)
+    assigned_voice=$(grep "^voice:" "$personality_file" | cut -d: -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
+
+    # Check if voice exists in config
+    if [[ -z "${VOICES[$assigned_voice]}" ]]; then
+      errors="${errors}Personality '${personality_name}' uses undefined voice: ${assigned_voice}\n"
+      failed=1
+    fi
+  done
+
+  if [[ $failed -eq 1 ]]; then
+    echo -e "$errors"
+    return 1
+  fi
+}

package/.claude/commands/prepare-release.md

@@ -1,65 +0,0 @@
----
-description: Prepare a new release with AI-generated summary
-argument-hint: [patch|minor|major]
----
-
-# /prepare-release
-
-Prepares a new AgentVibes release with AI-generated release notes.
-
-This command:
-1. Analyzes all changes since the last release
-2. Generates an intelligent summary using Claude AI
-3. Creates/updates RELEASE_NOTES.md
-4. Bumps the version
-5. Commits everything
-6. Ready for you to push
-
-## Usage
-
-```bash
-# Patch release (bug fixes)
-/prepare-release patch
-
-# Minor release (new features)
-/prepare-release minor
-
-# Major release (breaking changes)
-/prepare-release major
-```
-
-## What Gets Generated
-
-- **AI Summary**: High-level overview of changes
-- **Categorized Changes**: Features, fixes, docs, tests
-- **User Impact**: What users should know
-- **Migration Notes**: If breaking changes exist
-
-## Example Output
-
-```markdown
-# Release v1.0.10
-
-## AI Summary
-This release focuses on improving test reliability and fixing directory
-detection issues. The test suite now properly handles bash warnings and
-all 27 tests pass consistently across different environments.
-
-## Changes
-### 🐛 Bug Fixes
-- Fixed test path resolution for BATS tests
-- Updated test assertions to handle bash warnings
-
-### 🧪 Testing
-- Added comprehensive test coverage for replay command
-- All tests now passing in CI/CD
-
-## User Impact
-- More reliable installation and testing
-- Better error messages
-- No breaking changes
-```
-
-## Implementation
-
-!bash .claude/hooks/prepare-release.sh $ARGUMENTS

package/.claude/commands/release.md

@@ -1,59 +0,0 @@
----
-description: Prepare and push a new release with AI-generated notes
-argument-hint: [patch|minor|major]
----
-
-# /release
-
-Fully automates the release process with AI-generated release notes and pushes to master.
-
-This command automatically:
-1. Analyzes all changes since the last release (git log)
-2. Reads actual code diffs to understand what changed
-3. Generates an intelligent AI summary
-4. Creates/updates RELEASE_NOTES.md with comprehensive notes
-5. Bumps the version using npm version
-6. Commits everything together
-7. Pushes to master with --follow-tags
-8. Updates v1 branch
-
-## Usage
-
-```bash
-# Patch release (bug fixes) - default
-/release
-/release patch
-
-# Minor release (new features)
-/release minor
-
-# Major release (breaking changes)
-/release major
-```
-
-## What Happens
-
-- **Git Analysis**: Reviews commits since last tag
-- **Code Review**: Examines actual diffs for context
-- **AI Summary**: High-level overview of changes
-- **Categorized Changes**: Features, fixes, docs, tests
-- **Version Bump**: Updates package.json
-- **Auto Push**: Pushes to master with tags
-- **Branch Update**: Syncs v1 branch
-
-## Example
-
-```bash
-/release minor
-```
-
-This will:
-- Analyze changes since last release
-- Generate comprehensive release notes
-- Bump from 1.0.10 → 1.1.0
-- Commit and push everything
-- Update v1 branch to point to new release
-
-## Implementation
-
-This command tells Claude AI to prepare and push a new release with AI-generated notes.

package/.claude/hooks/prepare-release.sh

@@ -1,17 +0,0 @@
-#!/bin/bash
-# Prepare release with AI-generated notes
-# This is a placeholder - Claude AI will handle the actual logic
-
-BUMP_TYPE="${1:-patch}"
-
-echo "🤖 Preparing release with AI-generated summary..."
-echo ""
-echo "This command tells Claude AI to:"
-echo "1. Analyze changes since last release"
-echo "2. Generate intelligent summary"
-echo "3. Create RELEASE_NOTES.md"
-echo "4. Bump version to $BUMP_TYPE"
-echo "5. Commit everything"
-echo ""
-echo "⚠️  This is handled by Claude AI, not this script"
-echo "Please ask Claude to prepare the release instead"

package/RELEASE_NOTES.md

@@ -1,154 +0,0 @@
-# Release v1.0.11
-
-## 🤖 AI Summary
-
-This release completes the AI-powered release workflow by adding the `/release` slash command and automatic README updates. Now releasing AgentVibes is as simple as typing a single command - Claude handles everything from code analysis to publishing.
-
-The new `/release` command provides a streamlined, one-step release process that includes updating the README with the latest release information, ensuring users immediately see what's new when they visit the repository.
-
-## ✨ What's New
-
-### `/release` Slash Command
-- **New command**: Simply type `/release patch|minor|major` to trigger a full release
-- **Fully automated**: Claude analyzes changes, generates notes, bumps version, and pushes
-- **One-step publishing**: No manual steps needed - everything happens automatically
-- **Intelligent workflow**: Combines all release preparation and publishing tasks
-
-### README Latest Release Section
-- **Automatic updates**: The `/release` command now updates README.md with latest version info
-- **Prominent placement**: "Latest Release" section appears right after badges
-- **Direct links**: Quick links to full release notes and all releases
-- **Better discoverability**: Users see what's new immediately when visiting the repo
-
-## 📝 How It Works
-
-**Complete `/release` workflow:**
-
-1. You type: `/release patch` (or minor/major)
-2. Claude analyzes all commits and code diffs since v1.0.10
-3. Claude generates comprehensive AI summary in RELEASE_NOTES.md
-4. Claude updates README.md "Latest Release" section with:
-   - New version number and title
-   - Brief summary of changes
-   - Links to release notes
-5. Claude runs `npm version patch`
-6. Claude commits RELEASE_NOTES.md + README.md + version bump
-7. Claude pushes to GitHub with `--follow-tags`
-8. Claude updates v1 branch
-9. GitHub Actions publishes to npm automatically
-10. GitHub Release created with AI notes
-
-**All from a single command!**
-
-## 🎯 User Impact
-
-**For Maintainers:**
-- Release process reduced from ~10 steps to 1 command
-- No more manual changelog writing
-- No more forgetting to update README
-- Consistent, professional release notes every time
-
-**For Users:**
-- Immediately see what's new when visiting the repo
-- Clear, helpful release notes written by AI
-- Direct links to detailed information
-- Better understanding of version changes
-
-## 🔧 Technical Details
-
-**Files Changed:**
-- `.claude/commands/release.md` - New slash command (59 lines)
-- `README.md` - Added "Latest Release" section (10 lines)
-- Inherits all capabilities from v1.0.10's RELEASE_NOTES.md system
-
-**README Format:**
-```markdown
-## 📰 Latest Release
-
-**[v1.0.11 - Title](link)** 🤖
-
-Brief summary of what's new...
-
-[→ View Full Release Notes](link) | [→ All Releases](link)
-```
-
-**Command Flow:**
-```
-User: /release patch
-  ↓
-Claude: Analyze git log v1.0.10..HEAD
-  ↓
-Claude: Generate RELEASE_NOTES.md (this file)
-  ↓
-Claude: Update README "Latest Release" section
-  ↓
-Claude: npm version patch → v1.0.11
-  ↓
-Claude: git commit + push --follow-tags
-  ↓
-Claude: Update v1 branch
-  ↓
-GitHub Actions: Publish to npm + Create release
-```
-
-## 💡 Example Usage
-
-```bash
-# In Claude Code:
-User: /release patch
-
-Claude:
-📊 Analyzing changes since v1.0.10...
-   - 3 commits found
-   - 3 files changed (+179 lines)
-
-🤖 Generating AI release notes...
-   ✓ Created comprehensive summary
-   ✓ Categorized all changes
-
-📝 Updating README.md...
-   ✓ Updated "Latest Release" section
-   ✓ Added links to v1.0.11
-
-📦 Bumping version...
-   v1.0.10 → v1.0.11
-
-💾 Committing changes...
-   ✓ RELEASE_NOTES.md
-   ✓ README.md
-   ✓ package.json
-
-🚀 Pushing to GitHub...
-   ✓ Pushed to master
-   ✓ Tag v1.0.11 created
-   ✓ Updated v1 branch
-
-✅ Release v1.0.11 published!
-   📦 npm: https://www.npmjs.com/package/agentvibes/v/1.0.11
-   🎉 GitHub: https://github.com/paulpreibisch/AgentVibes/releases/tag/v1.0.11
-```
-
-## 🚀 What's Next
-
-Future enhancements could include:
-- Automatic migration guide generation for breaking changes
-- Dependency update analysis
-- Performance impact assessment
-- Automated testing report inclusion
-- Social media announcement drafts
-
-## 📦 Installation
-
-```bash
-npx agentvibes@1.0.11 install
-```
-
-## 🔗 Links
-
-- [View this release on GitHub](https://github.com/paulpreibisch/AgentVibes/releases/tag/v1.0.11)
-- [npm package](https://www.npmjs.com/package/agentvibes/v/1.0.11)
-- [Full Documentation](https://github.com/paulpreibisch/AgentVibes#readme)
-
----
-
-**Built with ❤️ by Paul Preibisch | Powered by ElevenLabs AI & Claude AI**

package/RELEASE_PROCESS.md

@@ -1,204 +0,0 @@
-# AgentVibes Release Process
-
-## 📦 npm Publishing Best Practices
-
-### Current Setup ✅
-
-AgentVibes follows industry best practices for npm package releases:
-
-1. **Semantic Versioning (SemVer)**
-   - `MAJOR.MINOR.PATCH` format (e.g., 1.0.7)
-   - MAJOR: Breaking changes
-   - MINOR: New features (backward compatible)
-   - PATCH: Bug fixes
-
-2. **Conventional Commits**
-   - `feat:` → New features (MINOR bump)
-   - `fix:` → Bug fixes (PATCH bump)
-   - `docs:` → Documentation only
-   - `test:` → Test updates
-   - `chore:` → Maintenance tasks
-
-3. **Automated Publishing**
-   - GitHub Actions handles all releases
-   - No manual `npm publish` needed
-   - Publishes on git tag push
-
-4. **Dual Release Strategy**
-   - npm package (automated)
-   - GitHub Release (automated with categorized notes)
-
-## 🚀 How to Release
-
-### Simple Release Process
-
-```bash
-# 1. Make your changes and commit using conventional commits
-git add -A
-git commit -m "feat: Add new voice preview feature"
-
-# 2. Bump version and create tag (this triggers everything)
-npm version patch   # For bug fixes (1.0.7 → 1.0.8)
-npm version minor   # For new features (1.0.7 → 1.1.0)
-npm version major   # For breaking changes (1.0.7 → 2.0.0)
-
-# 3. Push with tags
-git push origin master --follow-tags
-
-# 4. Update v1 branch (optional but recommended)
-git checkout v1 && git merge master --no-edit && git push origin v1 && git checkout master
-```
-
-**That's it!** GitHub Actions automatically:
-- ✅ Publishes to npm
-- ✅ Creates GitHub Release
-- ✅ Generates categorized changelog
-- ✅ Tags the release
-
-## 📋 What Happens Automatically
-
-### When you push a version tag (e.g., v1.0.8):
-
-1. **npm Publishing** (`.github/workflows/publish.yml`)
-   - Runs on Ubuntu latest
-   - Uses Node.js 20
-   - Runs `npm ci` for clean install
-   - Publishes to npm registry
-   - Uses `NPM_TOKEN` secret for authentication
-
-2. **GitHub Release Creation**
-   - Extracts version from tag
-   - Categorizes commits by type:
-     - ✨ New Features (feat:)
-     - 🐛 Bug Fixes (fix:)
-     - 📚 Documentation (docs:)
-     - 🧪 Testing (test:)
-     - 🔧 Maintenance (chore:)
-   - Generates formatted release notes
-   - Includes installation instructions
-   - Adds links to npm, docs, and issues
-   - Uses GitHub's auto-generated notes too
-
-3. **Testing** (`.github/workflows/test.yml`)
-   - Runs all BATS tests
-   - Validates no regressions
-   - Shows status in PR/commit
-
-## 🏷️ Release Notes Format
-
-Example output:
-```markdown
-## AgentVibes v1.0.8
-
-> Professional text-to-speech narration for Claude Code sessions
-
-### 📦 Installation
-\`\`\`bash
-npx agentvibes@1.0.8 install
-\`\`\`
-
-### 📝 What's Changed
-
-### ✨ New Features
-- Add voice preview feature (abc123)
-- Support custom personalities (def456)
-
-### 🐛 Bug Fixes
-- Fix audio save directory detection (ghi789)
-- Resolve double-audio bug in personality switching (jkl012)
-
-### 📚 Documentation
-- Update README with new commands (mno345)
-
-### 🔗 Links
-- 📦 [npm package](https://www.npmjs.com/package/agentvibes/v/1.0.8)
-- 📚 [Full Documentation](https://github.com/paulpreibisch/AgentVibes#readme)
-- 🐛 [Report Issues](https://github.com/paulpreibisch/AgentVibes/issues)
-
----
-
-**Built with ❤️ by Paul Preibisch | Powered by ElevenLabs AI**
-```
-
-## 🔐 Secrets Configuration
-
-Required GitHub secrets:
-- `NPM_TOKEN` - Automation token from npmjs.com
-- `GITHUB_TOKEN` - Auto-provided by GitHub Actions
-
-## 📊 Release Checklist
-
-Before releasing:
-- [ ] All tests passing locally (`npm test`)
-- [ ] Conventional commit messages used
-- [ ] CHANGELOG reflects changes (auto-generated)
-- [ ] Version bump appropriate for changes
-- [ ] Both master and v1 branches updated
-
-After releasing:
-- [ ] Check npm package published: https://www.npmjs.com/package/agentvibes
-- [ ] Verify GitHub Release created
-- [ ] Test installation: `npx agentvibes@VERSION install`
-- [ ] Check badges on README (should be green)
-
-## 🎯 Best Practices We Follow
-
-✅ **Automated Everything**
-- No manual npm publish
-- No manual release notes
-- No manual changelog
-
-✅ **Semantic Versioning**
-- Clear version meaning
-- Predictable upgrades
-
-✅ **Conventional Commits**
-- Auto-categorized changes
-- Better git history
-
-✅ **Comprehensive Testing**
-- 29+ tests with mocks
-- No API token usage
-- CI/CD integration
-
-✅ **Clear Documentation**
-- Installation in release notes
-- Links to resources
-- Version-specific npx commands
-
-## 🚨 Common Issues
-
-**Release didn't trigger:**
-- Ensure tag format is `v*.*.*` (e.g., v1.0.8)
-- Check GitHub Actions tab for errors
-- Verify NPM_TOKEN is valid
-
-**Tests failing:**
-- Run `npm test` locally first
-- Check test output in Actions tab
-- Fix issues before releasing
-
-**npm already has this version:**
-- Can't republish same version
-- Bump version again
-- Delete tag if needed: `git tag -d v1.0.8 && git push origin :refs/tags/v1.0.8`
-
-## 📈 Version History
-
-Current release: **v1.0.7**
-
-Recent changes (unreleased):
-- test: Add tests for replay command directory detection and output
-- fix: Replay command now uses project-local audio directory
-- feat: Show full file path in replay command output
-- docs: Add GitHub Actions status badges for tests and publishing
-
-Next release will be: **v1.0.8** (PATCH - bug fixes and tests)
-
-## 🔮 Future Improvements
-
-- [ ] Automated security scanning
-- [ ] Performance benchmarks
-- [ ] Pre-release/beta channel support
-- [ ] Automatic dependency updates (Dependabot)
-- [ ] Release candidate workflow