runtime-api-verification

Curl the live endpoint to capture the real JSON response, then compare each top-level key against the frontend TypeScript type for name, casing, and nesting. Finally trace the data through the api client, adapter, hook, and component to confirm every layer passes real data.

Compilation only checks type shapes, not runtime wiring. Common causes are hooks returning mock data via setTimeout, adapters that just return raw responses, or components rendering inline MOCK_ constants instead of hook output.

Search the pages and hooks directories for identifiers starting with MOCK_ and the word mock using grep. Then confirm each hook actually calls the api client and each component consumes the hook result rather than a local constant.

Mismatches usually come from snake_case versus camelCase naming, different nesting depth, or optional fields missing in the backend response. Compare the curl output key by key against the type definition and add fallback handling for absent optional fields.

Run it after creating or modifying any frontend page, hook, or service layer that fetches backend data, and whenever users report symptoms like buttons doing nothing or empty screens. It is especially important as a QC step after subagents generate complete components.