fix(kanban): reject toolset names in task skills#22933
Conversation
|
Salvage merged via PR #23273 (rebase) — your commit shipped on The DB-layer validation approach you took was the right call — it catches the bug at every entry point (CLI, dashboard POST, kanban_create tool, future REST/MCP) instead of needing a per-tool guard. The One small follow-up improvement during salvage: the loop now aggregates ALL toolset names found into a single error rather than raising on the first. Agents that confuse skills with toolsets usually pass several at once ( Thanks @LeonSGP43! |
Summary
weborbrowserwhen creating kanban tasks with per-taskskillskanban_createerror instead of letting the worker crash later at dispatchTesting
git diff --checkuv sync --frozen --extra alluv run --frozen ruff check .env -ipytest--collect-onlysmokeruff/tylint-diff with 0 new diagnostics in touched filesCloses #22921