LATTICE TanStack Start Frontend

Route loader coverage validation checks every route under src/routes to ensure required loader functions are present, avoiding blank screens. It confirms the operator UI matches the expected 11-route set and verifies no routes are missing loaders.

Client-purity enforcement detects forbidden imports like Anthropic SDK or @itwin/core/backend inside src/ to keep server responsibilities separated. Scanning src/ ensures the client bundle stays pure and prevents backend dependencies from leaking into client code.

Server function contract checks validate runtime functions under src/server/runtime to ensure they follow TanStack Start patterns and return JSON only. This auditing confirms server-side functions maintain proper contracts and avoid non-JSON responses.

Route inventory and drift detection confirms the operator UI under src/routes matches the expected 11-route set. By applying deterministic auditing steps, it identifies missing or unexpected routes when adding new operator UI screens.

Bundle-health build analysis using Bun validates the LATTICE TanStack Start frontend build status. It executes deterministic build checks to resolve runtime issues caused by missing loaders or forbidden imports within the project.

Yes, Bun is required to execute the bundle-health build analysis that resolves build or runtime issues. This analysis identifies problems caused by missing route loaders or forbidden client imports to keep the UI pure and routes correct.