Expose capability-driven UI API with Pydantic/OpenAPI

[quinCode]

Expose capability-driven UI API with Pydantic/OpenAPI

Parent

#2

What to build

Expose UI backend routes and schemas for capability discovery using Pydantic as the source of truth and FastAPI OpenAPI as the frontend contract. The route should return normalized UI application model data, not raw core CLI contract output.

This slice proves the pattern for backend capability modules and gives the future React frontend a typed API contract to consume.

Acceptance criteria

• A backend capability module exposes UI capabilities through a FastAPI route.
• Pydantic schemas define the response shape for capabilities.
• OpenAPI includes the capability route and schemas.
• Backend API tests cover successful capability responses and degraded or unsupported core capability states.
• The route uses application services and CoreGateway rather than direct subprocess calls.
• The response shape is stable for frontend feature modules and does not leak raw core stdout, YAML, or result files.

Blocked by

• Create the UI backend source boundary and CoreGateway skeleton #4