docs: update Bash version references from 3.2+ to 3.0+

Author: Chemaclass

.claude/CLAUDE.md

@@ -2,7 +2,7 @@
 
 ## Project Overview
 
-**bashunit** is a comprehensive, lightweight Bash testing framework (requires Bash 3.2+) focused on developer experience. It provides assertions, test doubles (spies/mocks), data providers, snapshots, and more.
+**bashunit** is a comprehensive, lightweight Bash testing framework (requires Bash 3.0+) focused on developer experience. It provides assertions, test doubles (spies/mocks), data providers, snapshots, and more.
 
 **Documentation:** https://bashunit.typeddevs.com
 
@@ -11,7 +11,7 @@
 This directory (`.claude/`) contains comprehensive Claude Code configuration:
 - **Custom skills**: `/tdd-cycle`, `/fix-test`, `/add-assertion`, `/check-coverage`, `/pre-release`
 - **Custom commands**: `/gh-issue` (complete GitHub issue → PR workflow)
-- **Modular rules**: Bash 3.2+ compatibility, testing patterns, TDD workflow
+- **Modular rules**: Bash 3.0+ compatibility, testing patterns, TDD workflow
 - **Automation**: Agent SDK examples for CI/CD
 
 See `README.md` in this directory for complete documentation.
@@ -27,7 +27,7 @@ See `README.md` in this directory for complete documentation.
 
 Every change starts from a failing test. No exceptions.
 
-### Bash 3.2+ Compatible
+### Bash 3.0+ Compatible
 
 Works on macOS default bash. **Prohibited features:**
 - ❌ `declare -A` (associative arrays - Bash 4.0+)
@@ -52,7 +52,7 @@ shfmt -w .       # Code formatting
 
 ```
 bashunit/
-├── src/                    # Core framework code (Bash 3.2+ compatible)
+├── src/                    # Core framework code (Bash 3.0+ compatible)
 │   ├── bashunit.sh        # Main entry point
 │   ├── assertions.sh      # Assertion functions
 │   ├── assert_*.sh        # Specialized assertions
@@ -141,10 +141,10 @@ Comprehensive validation before releasing.
 
 Specialized agents you can consult using the Task tool:
 
-### Bash 3.2+ Expert
-**When to use:** Reviewing code for Bash 3.2+ compatibility
+### Bash 3.0+ Expert
+**When to use:** Reviewing code for Bash 3.0+ compatibility
 **Expertise:** Identifying incompatible features, suggesting portable alternatives
-**Invoke:** Use Task tool with subagent_type="bash-3.2-expert"
+**Invoke:** Use Task tool with subagent_type="bash-3.0-expert"
 
 ### Code Reviewer
 **When to use:** Before committing, for comprehensive code review
@@ -185,7 +185,7 @@ Complete end-to-end workflow from issue to PR:
 
 ### Bash Style
 @.claude/rules/bash-style.md
-- Bash 3.2+ compatibility (critical!)
+- Bash 3.0+ compatibility (critical!)
 - ShellCheck compliance
 - Function documentation
 - Naming conventions
@@ -208,7 +208,7 @@ Complete end-to-end workflow from issue to PR:
 
 ### `src/**/*.sh`
 - Small, portable functions
-- Bash 3.2+ compatibility (no associative arrays, no `[[`, no `${var,,}`)
+- Bash 3.0+ compatibility (no associative arrays, no `[[`, no `${var,,}`)
 - Proper namespacing (`bashunit::*`)
 - No external dependencies in core
 - Function documentation required
@@ -235,7 +235,7 @@ Complete end-to-end workflow from issue to PR:
 
 ### Never:
 - Invent commands/features not in the codebase
-- Break Bash 3.2+ compatibility
+- Break Bash 3.0+ compatibility
 - Skip tests or quality checks
 - Change public API without docs/CHANGELOG
 - Use speculative/unproven patterns
@@ -249,7 +249,7 @@ Complete end-to-end workflow from issue to PR:
 - Keep tests passing during REFACTOR
 - Run quality checks before committing
 - Update CHANGELOG.md for user-visible changes
-- Maintain Bash 3.2+ compatibility
+- Maintain Bash 3.0+ compatibility
 
 ## Definition of Done
 
@@ -258,7 +258,7 @@ Before marking work complete:
 - ✅ `make sa` passes (ShellCheck)
 - ✅ `make lint` passes (EditorConfig)
 - ✅ Code formatted (`shfmt -w .`)
-- ✅ Bash 3.2+ compatible
+- ✅ Bash 3.0+ compatible
 - ✅ Parallel tests passing (`./bashunit --parallel tests/`)
 - ✅ CHANGELOG.md updated (if user-facing changes)
 - ✅ Documentation updated (if needed)

.claude/GETTING_STARTED.md

@@ -15,7 +15,7 @@ Welcome! This 5-minute guide will get you started with the custom Claude Code co
 - `/gh-issue 42` - Complete GitHub issue → PR workflow
 
 📚 **Code Standards** - Automatic enforcement:
-- Bash 3.2+ compatibility
+- Bash 3.0+ compatibility
 - TDD methodology (RED → GREEN → REFACTOR)
 - Testing patterns
 - Quality checks
@@ -58,7 +58,7 @@ Claude automatically follows these rules (from `.claude/CLAUDE.md`):
 - Minimal implementation
 - Refactor while green
 
-**Bash 3.2+ Compatible:**
+**Bash 3.0+ Compatible:**
 - No `declare -A` (associative arrays)
 - No `[[ ]]` (use `[ ]`)
 - No `${var,,}` (case conversion)
@@ -144,7 +144,7 @@ Study existing patterns:
 ## What Claude Automatically Enforces
 
 ✅ **TDD workflow** - Tests before code
-✅ **Bash 3.2+ compatibility** - No modern bash features
+✅ **Bash 3.0+ compatibility** - No modern bash features
 ✅ **Quality checks** - make sa && make lint
 ✅ **Test patterns** - Use existing patterns only
 ✅ **Commit format** - Conventional commits (no AI mentions!)

.claude/QUICK_REFERENCE.md

@@ -15,7 +15,7 @@
 | File | Purpose |
 |------|---------|
 | `CLAUDE.md` | Main project instructions |
-| `rules/bash-style.md` | Bash 3.2+ compatibility rules |
+| `rules/bash-style.md` | Bash 3.0+ compatibility rules |
 | `rules/testing.md` | Testing patterns & guidelines |
 | `rules/tdd-workflow.md` | TDD methodology details |
 | `AGENTS.md` | Comprehensive workflow guide |
@@ -100,7 +100,7 @@ Before marking work complete:
 
 **Never:**
 - Skip task file requirement
-- Use Bash 4+ features (macOS = Bash 3.2)
+- Use Bash 4+ features (macOS = Bash 3.0)
 - Break public API without docs
 - Commit without tests passing
 - Skip quality checks
@@ -110,11 +110,11 @@ Before marking work complete:
 - Use patterns from `tests/**` and `src/**`
 - Update task file logbook
 - Run tests after every change
-- Bash 3.2+ compatible code
+- Bash 3.0+ compatible code
 
-## 🔍 Bash 3.2+ Compatibility
+## 🔍 Bash 3.0+ Compatibility
 
-| ❌ Don't Use (Bash 4+) | ✅ Use Instead (Bash 3.2+) |
+| ❌ Don't Use (Bash 4+) | ✅ Use Instead (Bash 3.0+) |
 |------------------------|----------------------------|
 | `declare -A map` | Indexed arrays or workarounds |
 | `[[ "$var" == "x" ]]` | `[ "$var" = "x" ]` |

.claude/README.md

@@ -8,7 +8,7 @@ This directory contains custom Claude Code configuration to enhance AI-assisted
 .claude/
 ├── CLAUDE.md              # Main project instructions (read this first!)
 ├── rules/                 # Modular rules by topic
-│   ├── bash-style.md      # Bash 3.2+ compatibility & style
+│   ├── bash-style.md      # Bash 3.0+ compatibility & style
 │   ├── testing.md         # Testing patterns & guidelines
 │   └── tdd-workflow.md    # TDD Red-Green-Refactor cycle
 ├── skills/                # Custom reusable workflows
@@ -90,7 +90,7 @@ python .claude/agents/examples/pr-validator.py <pr-number>
 ### 2. Rules (Modular Guidelines)
 
 #### `rules/bash-style.md`
-- **Bash 3.2+ compatibility** (critical for macOS)
+- **Bash 3.0+ compatibility** (critical for macOS)
 - Coding standards
 - ShellCheck compliance
 - Documentation patterns
@@ -252,13 +252,13 @@ Workflow steps...
 For specific domains, create custom agents:
 
 ```markdown
-# .claude/agents/bash-3-expert/agent.md
+# .claude/agents/bash-3.0-expert/agent.md
 
-You are a Bash 3.2 compatibility expert for bashunit.
+You are a Bash 3.0 compatibility expert for bashunit.
 
 Your expertise:
 - Identify Bash 4+ features
-- Suggest Bash 3.2 alternatives
+- Suggest Bash 3.0 alternatives
 - Explain compatibility trade-offs
 
 When consulted:
@@ -356,7 +356,7 @@ jobs:
 /tdd-cycle
 
 # Test rules are followed
-# (Claude should enforce Bash 3.2+ compatibility)
+# (Claude should enforce Bash 3.0+ compatibility)
 
 # Test agents run
 python .claude/agents/examples/tdd-bot.py --help

.claude/agents/bash-3.2-expert/agent.md .claude/agents/bash-3.0-expert/agent.md.claude/agents/bash-3.2-expert/agent.md renamed to .claude/agents/bash-3.0-expert/agent.md

@@ -1,23 +1,23 @@
-# Bash 3.2+ Compatibility Expert
+# Bash 3.0+ Compatibility Expert
 
-You are a Bash 3.2+ compatibility expert for the bashunit project.
+You are a Bash 3.0+ compatibility expert for the bashunit project.
 
 ## Your Expertise
 
 You specialize in:
-- Bash 3.2+ compatibility (macOS default)
+- Bash 3.0+ compatibility (macOS default)
 - Identifying Bash 4.0+ features
-- Providing Bash 3.2 alternatives
+- Providing Bash 3.0 alternatives
 - ShellCheck compliance
 - Portable shell scripting
 
 ## When You're Consulted
 
 Developers will ask you to:
-- Review code for Bash 3.2+ compatibility
+- Review code for Bash 3.0+ compatibility
 - Identify incompatible features
 - Suggest portable alternatives
-- Explain why certain features don't work in Bash 3.2
+- Explain why certain features don't work in Bash 3.0
 - Fix compatibility issues
 
 ## Critical Knowledge
@@ -30,7 +30,7 @@ Developers will ask you to:
 declare -A map
 map["key"]="value"
 
-# ✅ DO (Bash 3.2+)
+# ✅ DO (Bash 3.0+)
 # Use indexed arrays or alternative data structures
 declare -a keys=("key1" "key2")
 declare -a values=("val1" "val2")
@@ -110,7 +110,7 @@ When reviewing code:
     - Explain why it's incompatible
     - State which Bash version introduced it
 
-3. **Provide Bash 3.2 alternative**
+3. **Provide Bash 3.0 alternative**
     - Show working alternative code
     - Explain any trade-offs
     - Ensure it's tested and verified
@@ -145,18 +145,18 @@ Found 3 Bash 4+ compatibility issues:
 
 After fixes, run:
     shellcheck -x file.sh
-    bash --version  # Verify 3.2 compatibility
+    bash --version  # Verify 3.0 compatibility
 ```
 
 ## Testing Compatibility
 
 Suggest testing approaches:
 ```bash
-# Test on macOS (usually Bash 3.2)
+# Test on macOS (usually Bash 3.0)
 bash --version
 
 # Run with older bash if available
-bash-3.2 script.sh
+bash-3.0 script.sh
 
 # Use shellcheck with appropriate shell directive
 # shellcheck shell=bash
@@ -166,7 +166,7 @@ bash-3.2 script.sh
 
 ### Loops
 ```bash
-# ✅ Bash 3.2 compatible
+# ✅ Bash 3.0 compatible
 for item in "${array[@]}"; do
     echo "$item"
 done
@@ -178,31 +178,31 @@ done < file
 
 ### String Manipulation
 ```bash
-# ✅ Substring (works in 3.2)
+# ✅ Substring (works in 3.0)
 substring="${string:5:3}"
 
-# ✅ Remove prefix/suffix (works in 3.2)
+# ✅ Remove prefix/suffix (works in 3.0)
 filename="${path##*/}"
 extension="${filename##*.}"
 ```
 
 ### Arrays
 ```bash
-# ✅ Array basics (works in 3.2)
+# ✅ Array basics (works in 3.0)
 declare -a array=("item1" "item2")
 length="${#array[@]}"
 last="${array[${#array[@]}-1]}"
 ```
 
 ## Resources
 
-- Bash 3.2 was released in 2006 (macOS default)
+- Bash 3.0 was released in 2004
 - Major features added in Bash 4.0+ (2009) are not available
-- Always test on macOS or with Bash 3.2
+- Always test on macOS or with Bash 3.0
 
 ## Key Principles
 
-1. **Assume Bash 3.2** - It's the lowest common denominator
+1. **Assume Bash 3.0** - It's the lowest common denominator
 2. **Test on macOS** - Most likely to catch issues
 3. **Use ShellCheck** - It helps catch compatibility issues
 4. **Prefer POSIX** - When possible, use POSIX-compatible constructs
@@ -221,4 +221,4 @@ If compatibility cannot be achieved:
     fi
     ```
 
-Your goal: Help maintain bashunit's Bash 3.2+ compatibility while writing clean, readable code.
+Your goal: Help maintain bashunit's Bash 3.0+ compatibility while writing clean, readable code.

.claude/agents/code-reviewer/agent.md

@@ -7,7 +7,7 @@ You are a code reviewer for the bashunit project, specializing in validating cod
 You review code for:
 - Project standard compliance
 - Code quality and readability
-- Bash 3.2+ compatibility
+- Bash 3.0+ compatibility
 - Security issues
 - Performance concerns
 - Test coverage
@@ -24,7 +24,7 @@ You review code for:
 - ✅ Variables quoted (`"$var"` not `$var`)
 - ✅ Error handling (`set -euo pipefail` where appropriate)
 - ✅ ShellCheck compliance
-- ✅ Bash 3.2+ compatibility (no `[[`, `declare -A`, etc.)
+- ✅ Bash 3.0+ compatibility (no `[[`, `declare -A`, etc.)
 
 ### 2. Testing Standards (@.claude/rules/testing.md)
 
@@ -90,7 +90,7 @@ Lines: +150 -0
 **Bash Style:**
 - Line 15: Missing function documentation
 - Line 42: Variable not quoted: `$user_input`
-- Line 58: Using `[[` instead of `[` (Bash 3.2 incompatible)
+- Line 58: Using `[[` instead of `[` (Bash 3.0 incompatible)
 
 **Testing:**
 - Missing test for error case (when file not found)
@@ -115,7 +115,7 @@ result="$user_input"
 # ❌ Line 58: Bash 4+ feature
 if [[ "$var" == "value" ]]; then
 
-# ✅ Fix: Use Bash 3.2 compatible syntax
+# ✅ Fix: Use Bash 3.0 compatible syntax
 if [ "$var" = "value" ]; then
 ```
 
@@ -174,7 +174,7 @@ Use this for each review:
 - [ ] Functions documented
 - [ ] Variables quoted
 - [ ] ShellCheck clean
-- [ ] Bash 3.2+ compatible
+- [ ] Bash 3.0+ compatible
 
 ### Testing
 - [ ] Test file names correct (_test.sh)
@@ -211,7 +211,7 @@ Use this for each review:
 
 **Critical (Block Merge):**
 - Security vulnerabilities
-- Bash 3.2 incompatibility
+- Bash 3.0 incompatibility
 - Breaking changes without docs
 - Failing tests
 
@@ -253,7 +253,7 @@ Complexity: Medium
 2. **Compatibility: Bash 4+ Feature** (Line 78)
     Using associative array (Bash 4.0+)
 
-    Fix: See @.claude/agents/bash-3.2-expert for alternatives
+    Fix: See @.claude/agents/bash-3.0-expert for alternatives
 
 ## Major Issues ⚠️