elevenlabs-ci-integration

# ElevenLabs CI Integration ## Overview Set up CI/CD pipelines that test ElevenLabs integrations without burning character quota on every PR. Uses a two-tier strategy: mocked unit tests on every push, gated integration tests on demand. ## Prerequisites - GitHub repository with Actions enabled - ElevenLabs API key for integration tests - npm/pnpm project with vitest configured ## Instructions ### Step 1: GitHub Actions Workflow ```yaml # .github/workflows/elevenlabs-tests.yml name: ElevenLabs Tests on: push: branches: [main] pull_request: branches: [main] jobs: # Tier 1: Always runs — no API key needed, no quota cost unit-tests: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: "20" cache: "npm" - run: npm ci - run: npm test -- --coverage env: # Mock mode — no real API calls ELEVENLABS_API_KEY: "sk_test_mock_key_for_ci" # Tier 2: Only on main or manual trigger — uses real API integration-tests: runs-on: ubuntu-latest if: github.ref == 'refs/heads/main' || github.event_name == 'workflow_dispatch' needs: unit-tests steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: "20" cache: "npm" - run: npm ci # Check quota before running integration tests - name: Check ElevenLabs quota env: ELE...