Job and step timeouts to prevent runaway CI bills

Hung processes (waiting for user input, deadlocked test, infinite loop in a script) cause CI jobs to run for the full 6-hour default timeout, consuming all runner minutes and blocking the queue.

Set timeout-minutes on both jobs and individual steps:

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15  # entire job
    steps:
      - name: Install dependencies
        run: npm ci
        timeout-minutes: 5  # this step only

      - name: Run tests
        run: npm test
        timeout-minutes: 10

For long-running processes, add explicit timeouts inside the command:

timeout 300 ./run-integration-tests.sh

A 15-minute timeout on a job that normally takes 5 minutes gives headroom for slow days while preventing the 6-hour worst case. Step-level timeouts pinpoint which step is hanging.