feat: add agent branch support to CLI (#66)

* feat: add agent branch support to CLI (#56)

Add support for working with agent branches, allowing users to list
branches, and pull/push from specific branches instead of only main.

New commands:
- `elevenlabs agents branches list --agent <id>` with --include-archived
- `elevenlabs agents pull --agent <id> --branch <name_or_id>`
- `elevenlabs agents push --agent <id> --branch <name_or_id>`

Branch identification accepts both human-readable names and IDs
(auto-detected by agtbrch_ prefix). --branch requires --agent since
branch names are per-agent.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* feat: add persistent branch config storage for CI/CD workflows

Branch configs are now stored as separate files in agent_configs/ and
tracked in agents.json under a `branches` map per agent, enabling
git-based version control and CI/CD pipelines.

New features:
- `pull --all-branches`: fetch all branches as separate config files
- `pull --branch <name>`: now persistently stores branch config
- `push`: auto-pushes all registered branch configs alongside main
- `init`: updated next-steps with branch workflow guidance

Schema: agents.json entries now support an optional `branches` map:
  { "staging": { "config": "agent_configs/Agent.staging.json",
    "branch_id": "agtbrch_xxx", "version_id": "ver_xxx" } }

Fully backward compatible - agents without branches work unchanged.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix: address code review findings

- Fix variable shadowing: rename inner agentId to currentAgentId in
  push-impl.ts loop body to avoid confusion with the parameter
- Fix dry-run: restructure push-impl.ts so --dry-run previews branch
  pushes instead of skipping them (previously dead code)
- Fix React key: use branch.id instead of array index in BranchesListView

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* docs: add branch support documentation to README

- Add branch support to features list
- Show branch config files in directory structure
- Document branch commands (branches list, --branch, --all-branches)
- Add Branch Workflows section with CI/CD pipeline example
- Document agents.json branches schema

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix: address bugs in agent branch support

- Fall back to non-UI codepath for --all-branches (UI view doesn't
  support it, was silently ignored)
- Auto-push registered branch configs in PushView UI mode (previously
  only worked with --no-ui)
- Fix main branch duplication in pullAllBranches when branch_id is
  unset on the agent entry (fall back to name="main" check)
- Move dry-run check before client init and branch resolution in
  push-impl so --dry-run doesn't make network calls
- Remove redundant resolveBranchId call in PullView (resolve once in
  initial effect, pass through to processNextAgent)
- Include archived branches when resolving branch names so resolution
  doesn't silently fail for archived branches

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Boris Starkov <boris.starkow@gmail.com>

Author: 3 people

README.md

@@ -15,6 +15,7 @@ Manage ElevenLabs with local configuration files. This tool is an experimental e
 - **Smart Updates**: Hash-based change detection
 - **Import/Export**: Fetch existing agents and tools from workspace
 - **Tool Management**: Import and manage tools from ElevenLabs workspace
+- **Branch Support**: Pull/push specific agent branches, CI/CD-friendly multi-branch workflows
 - **Widget Generation**: HTML widget snippets
 - **Secure Storage**: OS keychain integration with secure file fallback
 
@@ -102,10 +103,12 @@ elevenlabs agents push
 
 ```
 your_project/
-├── agents.json              # Central configuration
+├── agents.json              # Central configuration (includes branch mappings)
 ├── tools.json               # Tool configurations
 ├── tests.json               # Test configurations
 ├── agent_configs/           # Agent configuration files
+│   ├── My-Agent.json        # Main branch config
+│   └── My-Agent.staging.json # Branch config (auto-created by --all-branches)
 ├── tool_configs/            # Tool configurations
 └── test_configs/            # Test configurations
 ```
@@ -158,8 +161,14 @@ elevenlabs tools add-webhook "Tool Name" [--config-path path]
 # Create client tool
 elevenlabs tools add-client "Tool Name" [--config-path path]
 
-# Push changes
-elevenlabs agents push [--agent "Agent Name"] [--dry-run]
+# Push changes (main + all registered branches)
+elevenlabs agents push [--agent <agent_id>] [--dry-run]
+
+# Push to a specific branch
+elevenlabs agents push --agent <agent_id> --branch <branch_name_or_id>
+
+# List branches for an agent
+elevenlabs agents branches list --agent <agent_id> [--include-archived]
 
 # Sync tools
 elevenlabs tools push [--tool "Tool Name"] [--dry-run]
@@ -173,6 +182,12 @@ elevenlabs agents status [--agent "Agent Name"]
 # Pull agents from ElevenLabs
 elevenlabs agents pull [--search "term"] [--update] [--dry-run]
 
+# Pull from a specific branch
+elevenlabs agents pull --agent <agent_id> --branch <branch_name_or_id>
+
+# Pull all branches for each agent (stores as separate config files)
+elevenlabs agents pull --all --all-branches
+
 # Pull tools from ElevenLabs
 elevenlabs tools pull [--search "term"] [--tool "tool-name"] [--dry-run] [--output-dir tool_configs]
 
@@ -339,13 +354,59 @@ elevenlabs agents list
 elevenlabs agents delete agent_123456789
 ```
 
+## Branch Workflows
+
+Agent branches let you manage different configurations (e.g., staging vs production) alongside the main agent. Branch configs are stored as separate files in `agent_configs/` and tracked in `agents.json`, making them git-friendly and CI/CD-ready.
+
+**Work with branches locally:**
+
+```bash
+# List branches for an agent
+elevenlabs agents branches list --agent <agent_id>
+
+# Pull a specific branch config
+elevenlabs agents pull --agent <agent_id> --branch staging
+
+# Push to a specific branch
+elevenlabs agents push --agent <agent_id> --branch staging
+```
+
+**CI/CD pipeline (sync all branches):**
+
+```bash
+elevenlabs agents pull --all --all-branches --update --no-ui
+# Make config changes...
+elevenlabs agents push --no-ui
+# Push auto-pushes main + all registered branch configs
+```
+
+Branch configs in `agents.json`:
+
+```json
+{
+  "agents": [{
+    "config": "agent_configs/My-Agent.json",
+    "id": "agent_123",
+    "branches": {
+      "staging": {
+        "config": "agent_configs/My-Agent.staging.json",
+        "branch_id": "agtbrch_xxx",
+        "version_id": "ver_xxx"
+      }
+    }
+  }]
+}
+```
+
+The `--branch` flag accepts both human-readable names (`staging`) and branch IDs (`agtbrch_xxx`).
+
 ## Workflow Examples
 
 ```bash
 # List all agents
 elevenlabs agents list
 
-# Push all agents
+# Push all agents (main + branches)
 elevenlabs agents push
 
 # Pull agents (skips existing local agents)