Add OpenAPI endpoint reference docs

[anth-volk]

Fixes #18

Summary

• Add an API endpoint reference section to the country API docs pages.
• Add a selectable request sample panel mirroring the response sample component, with focused JSON snippets and explanatory notes for each allowed key.
• Document version as limited to current, frontier, or an exact numerical version string such as 1.691.1.
• Add a Spotify-style selectable Response sample panel for 200, 200 with deprecated-variable warning, 400 validation failures, 401, 403, 404, and 500 responses.
• Make request and response sample code blocks scroll horizontally instead of widening the page layout.
• Make the endpoint reference section use the same max-w-4xl gutter as the rest of the API guide.
• Make the docs app self-contained in local dev by clearing the zone asset prefix, while keeping /_zones/household-api-docs for production builds.

This keeps the production multi-zone asset shape, but avoids requiring app-v2 as the parent just to review local docs styling.

AI Explainer Note

This documentation exposes enable_ai_explainer and the AI explainer flow. No customer uses that endpoint today, and it is not fully implemented, so reviewers should explicitly decide whether exposing it in customer-facing docs is acceptable.

Validation

• bun install
• bun run build
• Verified the running local /us/api/ page includes the request sample selector, response sample selector, updated version allowed-value copy, and no Request keys or Response options sections.
• Verified local public chart assets serve at /python-guide/....
• Confirmed production app-v2 already proxies /_zones/household-api-docs/... assets for the deployed multi-zone route.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
household-api-docs	Ready	Preview, Comment	May 19, 2026 7:09pm

[anth-volk]