feat(kanban): triage layer Phase 1 — labels column + LLM-emitted assignee + routing engine

[jjaavvin-web]

Summary

Phase 1 of the triage routing layer that fills the "auto-assignee" gap in Kanban dispatch:

• hermes_cli/kanban_db.py — adds labels JSON column to tasks + migration for legacy DBs + set_task_labels/get_task_labels helpers
• hermes_cli/kanban_specify.py — specifier LLM now emits {title, body, assignee_suggestion, labels} instead of just title/body; suggestion fills empty assignee, labels written via schema column with metadata fallback
• hermes_cli/triage_routing.py (new) — route(labels, llm_suggested_assignee, routing_rules) with first-match-wins subset semantics; reads triage.routing_rules from ~/.hermes/config.yaml
• Specifier now calls route() after parsing LLM output → final assignee flows to specify_triage_task

Routing rules block (drop into config.yaml when ready):

triage:
  routing_rules:
    - labels: [audit-only]
      assignee: h2reviewer
    - labels: [long-running, autopilot]
      assignee: ruflo-swarm

Test plan

• 84/84 new tests in tests/hermes_cli/test_kanban_labels.py, test_kanban_specify.py, test_kanban_specify_db.py, test_triage_routing.py
• Full hermes_cli suite: 4378/4378 green — no regressions

🤖 Generated with Claude Code

[teknium1]

Thanks @jjaavvin-web — closing this one. The Phase 1 triage layer (labels column + LLM-emitted assignee + routing engine, 1360 LOC + 84 tests) overlaps with the existing orchestrator-driven decompose path that landed in #27572. Decompose already takes an LLM call to route tasks to specialist assignees by description; adding a parallel labels+routing engine would create two paths to the same outcome. If there's a concrete gap decompose doesn't fill, please open an issue and we can fold it into the orchestrator surface.