2.7 KiB
2.7 KiB
id, title, status, wave, depends_on, plan, spec
| id | title | status | wave | depends_on | plan | spec |
|---|---|---|---|---|---|---|
| 01-backend-mcp-contract | Backend and MCP title contract | done | 1 | plan.md | ../../specs/tasks/requirements/title-length-limit.md |
Task 01: Backend and MCP title contract
Acceptance
- Task creation and title-bearing updates accept 60-character titles and reject longer titles before persistence, while unrelated updates preserve legacy overlong titles.
- HTTP, WebSocket, and MCP callers receive their existing validation response for an overlong title.
create_task_kandev.titleadvertisesmaxLength: 60and recommends a concise, few-word title.
Verification
(
cd apps/backend
go test ./internal/task/service -run 'Test(CreateTaskAcceptsTitleAtLimit|CreateTaskRejectsTitleLongerThanLimit|UpdateTaskRejectsTitleLongerThanLimit|UpdateTaskWithoutTitlePreservesLegacyOverlongTitle)'
go test ./internal/task/handlers -run 'Test(HTTP|WS).*(Create|Update).*Title'
go test ./internal/mcp/server -run 'Test(CreateTask|UpdateTask)_ToolSchema'
go test ./internal/mcp/handlers -run 'Test(ClassifyCreateTaskErrorMapsOverlongTitleToValidation|HandleCreateTask_RejectsOverlongTitle|HandleUpdateTask_TitleTooLongReturnsValidation)'
)
Files likely touched
apps/backend/internal/task/service/task_title.goapps/backend/internal/task/service/task_title_test.goapps/backend/internal/task/service/service_tasks.goapps/backend/internal/task/handlers/errors.goapps/backend/internal/task/handlers/task_ws_handlers.goapps/backend/internal/task/handlers/task_http_handlers_test.goapps/backend/internal/task/handlers/task_update_repositories_test.goapps/backend/internal/mcp/server/server.goapps/backend/internal/mcp/server/handlers_test.goapps/backend/internal/mcp/handlers/handlers.goapps/backend/internal/mcp/handlers/handlers_test.goapps/backend/config/prompts/kandev-context.md
Dependencies
None.
Parallelism
Parallel-safe with Task 02 because backend/MCP files and frontend files are disjoint. Execute sequentially unless the user explicitly authorizes subagents.
Inputs
- Spec sections: What, API surface, Failure modes, and the API/MCP scenarios.
- Plan sections: Backend, MCP contract, and Tests.
- Existing patterns:
Service.validateCreateTaskRequest,handlers.isValidationError,classifyCreateTaskError, andmcp.MaxLengthin mcp-go.
Risks
- Do not validate unchanged legacy titles during non-title updates.
- Return the typed validation error before task writes, events, or auto-start metadata can cause side effects.
Output contract
Report the changed files, exact test commands/results, blockers and remaining risks, then mark this task done and update its checkbox in plan.md.