luyao618 6b3efcee49 fix(kanban): reject direct status transition to 'running' via dashboard API ...

The PATCH /tasks/:id endpoint allows setting status='running' via
_set_status_direct(), bypassing the dispatcher/claim path that creates
run rows, claim locks, expiry, and worker process metadata. This can
leave tasks stuck in 'running' with no active worker.

Fix: reject status='running' with HTTP 400, requiring all transitions
to 'running' to go through the canonical claim_task() path.

Closes #19535

2026-05-04 04:46:47 -07:00

..

dashboard

fix(kanban): reject direct status transition to 'running' via dashboard API

2026-05-04 04:46:47 -07:00

systemd

feat(kanban): durable multi-profile collaboration board (#17805)

2026-04-30 13:36:47 -07:00