flyio-ci-integration

# Fly.io CI Integration ## Overview Set up CI/CD for Fly.io edge deployments: run unit tests on every PR, deploy to staging on pull requests, and promote to production on merge to main. Fly.io uses Machines API for app management and deploy tokens for scoped CI authentication. CI pipelines build Docker images, deploy via `flyctl`, and run post-deploy health checks against the edge endpoints. ## GitHub Actions Workflow ```yaml # .github/workflows/fly-ci.yml name: Fly.io CI on: pull_request: branches: [main] push: branches: [main] jobs: unit-tests: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: { node-version: '20' } - run: npm ci - run: npm test -- --reporter=verbose deploy: if: github.ref == 'refs/heads/main' needs: unit-tests runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: superfly/flyctl-actions/setup-flyctl@master - run: fly deploy --ha=false env: FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }} - name: Health check run: | sleep 10 curl -sf https://my-app.fly.dev/health || exit 1 ``` ## Mock-Based Unit Tests ```typescript // tests/fly-service.test.ts import { describe, it, expect, vi } from 'vitest'; import { scaleApp } from '../src/fly-service'; vi.mock('../src/fly-client', () => ({ FlyClient: vi.fn().mockImplementation(() => ({ listMachines: vi.fn().mockReso...