Kanban Workflow (core)

Goal

Provide a reusable core for a project-management “co-worker” that:

• Uses the existing stage:* lifecycle as the canonical state machine.
• Integrates with PM platforms via adapter-managed auth (external CLIs/scripts; may require env vars like API keys). Kanban Workflow does not run interactive OAuth flows or persist secrets.
• Centralizes workflow/rules/runbooks so GitHub/Planka/Plane/Linear implementations share logic.

Queue semantics (requirements):

• next / autopilot-tick operate on assigned-to-me only items (across all configured scopes) for every adapter.
• Multi-scope monitoring is allowed, but it must enforce consistent stage/list/status names across all monitored scopes so a single stageMap is valid everywhere.

Canonical stage model

Treat these labels/states as canonical (and the only stages the agent should consider):