name: CI

# Branch pushes only — a release TAG deliberately does not re-run CI: the
# tagged commit's CI already ran on its branch push, and the runner is
# sequential, so tag-triggered matrix jobs (~22 min) would queue AHEAD of the
# tag's publish-source run and starve every release (observed on 8.10.3 and
# 9.0.0: the publish sat behind the tag's own redundant CI).
on:
  push:
    branches: ['**']
  pull_request:

jobs:
  node:
    name: Node ${{ matrix.node-version }}
    runs-on: ubuntu-latest
    strategy:
      fail-fast: false
      matrix:
        node-version: ['22', '24']
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: ${{ matrix.node-version }}
          cache: npm
      - run: npm ci
      - run: npm run test:unit

  # The correctness plant's full gate: integration + conformance run here on
  # dedicated iron, on every push, so a release never depends on any other
  # machine being up. Verdicts live in this run's log (never inferred).
  integration:
    name: Integration + conformance (Node 22)
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '22'
          cache: npm
      - run: npm ci
      - run: npm run test:ci-integration
      - run: npx vitest run tests/conformance

  bun:
    name: Bun (latest)
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '22'
          cache: npm
      - uses: oven-sh/setup-bun@v2
        with:
          bun-version: latest
      - run: npm ci
      # test:bun imports the built dist/, so build first.
      - run: npm run build
      # Bun as a runtime is the supported Bun story (`bun add` / `bun run`).
      - run: npm run test:bun