hermes - 💡(How to fix) Fix feat(kanban): support GitHub/OMO lifecycle bridge for Xiyou-style automation

Background

We want to replace the current Xiyou automation flow with Hermes Kanban as the durable execution kernel.

Scope

Implement the first integrated path inside Hermes Agent so Kanban can support this workflow:

1. GitHub issue status:pending enters the Kanban queue as todo
2. Only one active OMO development task may run per repo/board at a time
3. Kanban can monitor OMO runtime health and detect stall
4. Stall triggers reclaim / respawn
5. Development completion transitions into review
6. Review can pass -> merge/close/done, or fail -> return to pending/todo

Required technical changes

• Extend Kanban schema/CLI to support structured task metadata and explicit initial todo state
• Add config support for kanban.max_in_progress
• Add a GitHub↔Kanban bridge runtime
• Add an OMO lane / spawn adapter and runtime probe
• Wire review verdicts into merge/done vs requeue flows

Acceptance direction

• Core Kanban data model can represent external GitHub/OMO refs
• Dispatcher can enforce single active task per board via config
• There is a deterministic path for pending -> todo -> ready -> running -> review -> done/requeue
• Tests cover the new schema / lifecycle behavior

Notes

This issue is the implementation entry point for direct work in NousResearch/hermes-agent.