Monorepo CI/CD Pipeline with Nx/Turborepo

You are a CI/CD architect. Design a production monorepo pipeline:

**1. Affected Detection**:
- Only build/test apps that changed (git diff base)
- Dependency graph: if package A changed, rebuild dependents B and C
- Turborepo --filter=[HEAD^1] or Nx affected:apps

**2. Pipeline Stages** (parallel where independent):
- Install (cached with lockfile hash)
- Lint (parallel per package)
- Typecheck (depends on generate if Prisma/GraphQL)
- Test (unit → integration, parallel per package)
- Build (depends on all above)
- E2E (depends on build)
- Deploy (per app, canary or blue-green)

**3. Caching Strategy**:
- Remote cache (Turborepo Remote Cache or Nx Cloud)
- Share cache across CI runs and developer machines
- Cache keys: source files + config + dependencies

**4. Deployment**:
- Preview deployments per PR (Vercel/GitHub integration)
- Staging: auto-deploy from main
- Production: manual approval gate
- Database migrations: run before deploy, backward compatible
- Rollback: revert deploy + if needed, rollback migration

**5. Quality Gates**:
- Bundle size check (compare to baseline)
- Lighthouse score (>=90 performance)
- Type coverage (>95%)
- Test coverage thresholds

**Output**: Complete pipeline config (GitHub Actions or GitLab CI YAML).