Context

Implement all REST API routes for core resources using Litestar class-based controllers. Each resource group gets its own controller with shared guards and configuration.

Controllers to implement (per §13.2):

• CompanyController — CRUD company config
• AgentController — List, hire, fire, modify agents
• DepartmentController — Department management
• ProjectController — Project CRUD
• TaskController — Task management (create, assign, status, list, detail)
• MessageController — Communication log queries
• MeetingController — Schedule, view meeting outputs
• ArtifactController — Browse produced artifacts
• BudgetController — Spending, limits, projections
• AnalyticsController — Performance metrics
• ProviderController — Model provider status, config

Acceptance Criteria

• Class-based controller for each resource group listed above
• Standard CRUD operations where applicable (list, get, create, update, delete)
• Consistent response envelope format across all endpoints
• Pagination support (offset/limit) on all list endpoints
• Filtering support where appropriate (e.g. tasks by status/assignee/project)
• Route guards for authorization on write operations
• Request/response DTOs using Pydantic v2 models (reuse existing domain models where possible)
• Integration with persistence repositories (TaskRepository, CostRecordRepository, MessageRepository)
• --json compatible output for all endpoints
• Unit tests for each controller

Dependencies

• Set up Litestar application with REST API skeleton #31 — Litestar skeleton must be set up

Design Spec Reference

• §13.2 — API endpoint definitions