Contract Source
The API explorer reads docs/public/openapi.json. That file is generated from the TypeSpec contract in api/, then copied into the backend so non-production runtime docs can serve the same schema.
pnpm generate:openapiUse The Explorer
Open /openapi/ from the docs nav. The public page renders the generated contract with Scalar and groups operations by the tags defined in TypeSpec.
Use it to verify request bodies, response schemas, and route paths before writing additional guides.
Backend non-production environments also expose runtime Scalar API docs at /api/v1/docs. That page loads /api/v1/openapi.json from the same controller process. Production does not register either backend runtime docs route.
Authenticated Routes
Authenticated routes still need a valid session cookie when the backend enforces one. The explorer can describe the shape of the request, but it does not bypass application auth.
Documentation Updates
When a route changes, update the guide or reference page that explains the user-facing behavior. Keep implementation details in backend code and use docs for intent, workflow, and examples.