chore: untrack generated base.css, build it in test/CI paths

base.css is a Tailwind build artifact already listed in .gitignore, but it
had been tracked since it was first committed (gitignore can't untrack an
already-tracked file), so it kept getting re-committed against intent. Untrack
it to match js/dist (the TS artifact, also gitignored + untracked).

Because nothing in the test path rebuilt it, e2e/static serving relied on the
committed copy. Add 'css' (and 'ts') as prerequisites of the test/test-e2e
make targets and a Build CSS step in CI so the stylesheet is generated before
tests run.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.github/workflows/build-docker.yml

@@ -30,6 +30,9 @@ jobs:
       - name: Build TypeScript
         run: make ts
 
+      - name: Build CSS
+        run: make css
+
       - name: Install Playwright browsers
         run: uv run playwright install --with-deps chromium
 

Makefile

@@ -81,10 +81,12 @@ collectstatic:
 uv.lock: pyproject.toml
 	uv sync
 
-test: uv.lock
+# base.css (Tailwind) and js/dist (TS) are build artifacts, gitignored and not
+# tracked — build both before tests so e2e/static serving has fresh assets.
+test: uv.lock css ts
 	uv run --with pytest-django pytest
 
-test-e2e: uv.lock
+test-e2e: uv.lock css ts
 	uv run pytest e2e/
 
 lint: