kanban-worker

Prevent cross-tenant context leakage in multi-agent kanban workflows by enforcing tenant-prefixed memory entries. This ensures worker runtimes maintain strict isolation and prevents data spillover between different tenants during task handoffs.

The correct metadata shape for reliable kanban task handoffs uses validated kanban_complete(summary, metadata) semantics. You must claim created_cards based strictly on captured kanban_create return values to avoid phantom task claims.

Handle workspace persistence correctly by adapting behavior for scratch spaces, shared persistent directories, and git worktrees. Kanban workers must manage these differently to avoid broken handoffs and mis-handled workspaces during multi-agent collaboration.

Kanban worker retries often fail due to unclear block reasons and poor heartbeat quality. Improve retry diagnostics by applying operational guardrails and using strict KANBAN_GUIDANCE lifecycle semantics to capture accurate failure states.

No, you cannot claim kanban tasks not captured by your own kanban_create results. Claiming created_cards must be based strictly on captured kanban_create return values to prevent phantom task claims and automation failures.