chore: track uv lockfile and ignore coverage artifacts

.github/workflows/tests.yml

@@ -44,6 +44,21 @@ jobs:
       - name: Run platform and Python runtime suite
         run: ./tests/full_validate.sh --gate runtime
 
+  uv-lock:
+    name: Validate uv lockfile
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 1
+      - name: Set up uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          version: "0.12.8"
+      - name: Check uv lockfile
+        run: uv lock --check
+
   quality:
     name: Quality and security gates
     runs-on: ubuntu-latest

.gitignore

@@ -6,4 +6,7 @@ __pycache__/
 dist/
 build/
 *.egg-info/
+# pytest-cov writes the primary database and per-process databases here.
+.coverage
+.coverage.*
 coverage.json

docs/testing.md

@@ -7,6 +7,13 @@ documentation/schema/contract validation, benchmark budgets, and security.
 Bandit and pip-audit are required; a missing tool is an error rather than a
 skipped check.
 
+The repository is managed locally through uv, so `uv.lock` is checked into the
+repository. Validate that it still matches `pyproject.toml` with:
+
+```bash
+uv lock --check
+```
+
 Run it from a clean checkout after installing the development, quality, and
 benchmark extras (the latter installs every declared framework comparator):
 

tests/validate.sh

@@ -12,6 +12,7 @@ required_files=(
   LICENSE
   mkdocs.yml
   base_manifest.yaml
+  uv.lock
   .github/workflows/issue-branch-policy.yml
   .github/workflows/project-intake.yml
   .github/workflows/tests.yml