LATTICE FastAPI Endpoint Authoring

To prevent FastAPI endpoint contract drift, implement new routes under pixeltable/service/routes and register routers in pixeltable/service/main.py. You must synchronize the exact endpoint count with meta/API.md and meta/ARCHITECTURE.md in the same commit to avoid breaking dependent systems.

To enforce JSON-only responses in FastAPI routes, ban HTML, file, and redirect response patterns in your route implementations. This guarantees routes return strict JSON, preventing unexpected content types from breaking dependent systems or causing runtime failures.

A FastAPI sidecar endpoint count mismatch occurs when routes are added without updating canonical metadata. You must synchronize the active route registrations in pixeltable/service/main.py with the declared endpoint tables in meta/API.md and meta/ARCHITECTURE.md prior to commit.

To validate FastAPI sidecar health and Unix socket connectivity, run the operational scoring script to check for drift and worker health. This confirms the sidecar is operational and verifies production Unix socket connectivity prior to committing route changes.

No, FastAPI routes in pixeltable require JSON-only responses. HTML, file, and redirect response patterns are explicitly banned to maintain the LATTICE API contract, ensuring consistent JSON data exchange and preventing hard-to-debug runtime failures across dependent systems.

The correct workflow for FastAPI route registration involves adding routes under pixeltable/service/routes, registering routers in main.py, and running docs-sync checks. You must update meta/API.md and meta/ARCHITECTURE.md in the same commit to maintain the 33-endpoint contract.