hermes - 💡(How to fix) Fix feat(kanban): simplify todo/ready/scheduled queue states

Problem

The Kanban status model currently exposes several queue-ish states (todo, ready, and scheduled) that feel redundant from an operator/user perspective. This makes the board harder to reason about: users mostly need to know whether a card is intake/triage, ready to delegate, running, blocked, review/done, or archived.

There is also an existing related issue, #28502, noting that scheduled is not fully integrated with the dashboard/web UI.

Current semantics observed

• triage: raw/intake card that needs spec/decomposition.
• todo: dependency-waiting or not-ready queue.
• ready: dispatchable queue.
• scheduled: paused/deferred by reason, but not shown in the current dashboard column order.
• running, blocked, done, archived: operational states.

Proposal

Simplify the user-facing model by collapsing todo, ready, and scheduled into a single ready-ish queue or hiding the distinction behind metadata/UI filters.

Preferred direction to evaluate:

• Keep a simple visible lane: Ready.
• Preserve dependency safety internally: cards with unfinished parents must not be dispatchable.
• Represent manual deferral/scheduling as metadata/hold reason rather than a full visible lane, unless a separate Paused lane is clearly needed.
• Make dashboard/CLI wording consistent so users do not have to understand todo vs ready before delegating.

Acceptance criteria

• Operators see fewer redundant columns/choices in the dashboard.
• Moving a card to Ready is the normal path for delegation.
• Dependency-blocked cards cannot be dispatched even if displayed in the simplified ready/backlog area.
• Any remaining scheduled/deferred concept is visible and actionable, not hidden in the API only.
• Existing boards migrate safely without losing status information.
• Tests cover state migration, dispatcher claim safety, and dashboard/API transitions.