ci: run tests and the frontend build on pull requests

.github/workflows/linters.yml

@@ -66,5 +66,22 @@ jobs:
       - name: Run mypy
         run: mypy "./backend/" --install-types --non-interactive --config-file pyproject.toml
 
-      - uses: pre-commit-ci/lite-action@v1.1.0
-        if: always()
+      # Some tests are genuine integration tests: they run real ffmpeg and
+      # ffprobe against tiny fixtures in tests/fixtures/ rather than mocking
+      # the subprocess. Without the binaries they fail with a bare ENOENT.
+      - name: Install FFmpeg
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y --no-install-recommends ffmpeg
+
+      # tests/test_workers.py is a manual script that takes a real media file
+      # argument, not a pytest suite -- it errors under plain collection.
+      - name: Run backend tests
+        run: pytest tests/ --ignore=tests/test_workers.py
+
+      # The frontend is built into the image at docker build time, so a broken
+      # frontend dependency used to surface only after merge, when the publish
+      # workflow ran. Building here moves that to the PR.
+      - name: Build frontend
+        working-directory: frontend
+        run: npm run build

.pre-commit-config.yaml

@@ -66,12 +66,3 @@ repos:
         language: system
         types_or: [ts, tsx, javascript, jsx, json, svelte]
         pass_filenames: false
-
-ci:
-  autofix_commit_msg: |
-    [pre-commit.ci] auto fixes from pre-commit hooks
-  autofix_prs: true
-  autoupdate_commit_msg: '[pre-commit.ci] pre-commit autoupdate'
-  autoupdate_schedule: weekly
-  skip: [svelte-check]
-  submodules: false

AGENTS.md

@@ -18,24 +18,37 @@ docker compose up -d --build
 
 # Tests (local venv)
 source .venv/bin/activate
-pytest tests/
+pytest tests/ --ignore=tests/test_workers.py
 
 # Lint — run what CI runs, NOT a --files subset
 pre-commit run --all-files
 ```
 
+### What CI actually runs
+
+The **Run Linters** workflow is the required check, and it is more than its
+name suggests — `pre-commit run --all-files`, then `mypy ./backend/`, then the
+test suite, then `npm run build`. A clean pre-commit alone does not mean CI is
+green.
+
+`docker-publish.yml` invokes that same workflow via `workflow_call` before it
+builds an image, so these four gate releases as well as pull requests.
+
 ### Linting rules that matter
 
 - **Always `pre-commit run --all-files` before committing.** `--files <subset>`
   is not a substitute: CI runs `--all-files`, and a subset run has already let a
   `ruff format` failure through to a red `main`.
 - A formatting hook that **modifies** a file fails the run *by design*, even
   though the fix itself succeeded. Re-stage and re-run; it is not a real error.
-- CI runs **`mypy ./backend/`** as a **separate step**, so a clean pre-commit
-  alone does not mean CI is green.
 - `tests/test_workers.py` is a manual script requiring a real media file
-  argument, not a pytest suite — it errors under plain collection. Run
-  `pytest tests/ --ignore=tests/test_workers.py`.
+  argument, not a pytest suite — it errors under plain collection. Always pass
+  `--ignore=tests/test_workers.py`, as CI does.
+- **The suite needs `ffmpeg` and `ffprobe` on `PATH`.** Some tests are real
+  integration tests that run the binaries against fixtures in
+  `tests/fixtures/` rather than mocking the subprocess; without them you get
+  two failures and a bare `No such file or directory: 'ffprobe'`. CI installs
+  FFmpeg for exactly this reason.
 
 ### Biome's version lives in exactly one place
 

pyproject.toml

@@ -39,6 +39,7 @@ dependencies = [
 [project.optional-dependencies]
 dev = [
     "pytest>=7.0",
+    "pytest-timeout",
     "mypy>=1.0",
     "pre-commit",
     "ruff>=0.8.0",

requirements-lint.txt

@@ -1,6 +1,8 @@
 -r requirements.txt
 mypy
 pre-commit
+pytest
+pytest-timeout
 ruff
 types-PyYAML
 types-requests