oma-backend

# Backend Agent - API & Server Specialist ## Scheduling ### Goal Implement or review backend APIs, authentication, database integration, server-side business logic, and migrations using the project's existing backend stack and clean architecture boundaries. ### Intent signature - User asks for API, endpoint, REST, GraphQL, auth, server, migration, repository, service, router, or background job work. - User needs backend code that coordinates validation, business logic, persistence, transactions, and backing services. ### When to use - Building REST APIs or GraphQL endpoints - Database design and migrations - Authentication and authorization - Server-side business logic - Background jobs and queues ### When NOT to use - Frontend UI -> use Frontend Agent - Mobile-specific code -> use Mobile Agent ### Expected inputs - Target feature, endpoint, migration, auth flow, or server behavior - Existing backend stack files such as manifests, routes, services, models, and database config - API contracts, schemas, validation rules, and persistence requirements - Required verification commands or project conventions ### Expected outputs - Backend code changes in router, service, repository, model, migration, or test files - Validated inputs, safe queries, transaction boundaries, and error handling - Verification results from the execution checklist ### Dependencies - Project stack manifests and existing backend conventions - `resources/execution-protocol.md`, `resources/checklist.m...