feat: add WebSocket call script for assistants and squads

[vapi-tasker]

Summary

• Adds a CLI script to initiate WebSocket voice calls directly from the gitops repo
• Supports both assistants and squads via explicit -a and -s flags
• Works with nested resource paths (e.g., company-1/inbound-support)
• Checks microphone permissions at startup (prompts on macOS, checks ALSA on Linux)
• Real-time audio I/O via microphone and speakers (with optional dependencies)
• Displays live transcripts in the terminal
• Graceful shutdown with Ctrl+C

Usage

# Call an assistant in dev
bun run call:dev -a my-assistant

# Call a nested assistant
bun run call:dev -a company-1/inbound-support

# Call a squad
bun run call:dev -s my-squad

# Call in production
bun run call:prod -a my-assistant

CLI Options

Flag	Description
-a <name>	Call an assistant by name
-s <name>	Call a squad by name

New Files

• src/call.ts - Main entry point with WebSocket connection, audio handling, permission checks, and CLI parsing

Modified Files

• package.json - Added call:dev and call:prod scripts, optional mic and speaker dependencies
• README.md - Added comprehensive documentation for the WebSocket call feature

Permission Check Flow

On startup, the script checks microphone permissions:

• macOS: Attempts to trigger the system permission prompt using sox/rec
• Linux: Checks for ALSA recording devices
• Windows: Informs user they may be prompted

If permission cannot be verified, the user is asked whether to continue.

Audio Dependencies

The audio dependencies (mic, speaker) are marked as optional. The script works without them but will only show transcripts (no audio I/O). Users can install them with:

npm install mic speaker

# macOS may require:
brew install sox

Test plan

• Run npm install to install dependencies
• Run bun run call:dev -a <assistant-name> and verify:
  • Permission check runs on first invocation
  • Call is created successfully
  • WebSocket connects
  • Transcripts appear in terminal
  • Ctrl+C gracefully ends the call
• Test with nested assistant path (e.g., company-1/inbound-support)
• Test squad call: bun run call:dev -s <squad-name>
• Test error cases:
  • Invalid assistant name shows helpful error with available assistants
  • Missing state file shows helpful error
  • Using both -a and -s shows error

Closes VAP-11241

🤖 Generated with Claude Code