hermes - 💡(How to fix) Fix feat(kanban): sync GitHub issues into Kanban triage without auto-dispatch

Problem

We want GitHub issues to be usable as the intake source for Hermes Kanban work. When a new GitHub issue is created, it should be easy to mirror it into the Kanban triage lane so a human can delete/refine/decompose the plan and delegate from the dashboard.

Desired workflow

• GitHub issue is the durable external request / backlog item.
• Hermes Kanban receives a matching triage card, not an immediately-running task.
• The triage card includes:
  • GitHub issue number and URL
  • title/body snapshot
  • labels/priority hints when available
  • clear instruction: human must review/decompose before delegation
• Duplicate syncs must be idempotent by issue URL/number.
• Closing/archiving should not accidentally delete GitHub issues.

Safety / product constraints

• Do not auto-start workers from GitHub issues.
• Keep this manual-delegation only: mirrored cards land in triage and require human action before they can run.
• Avoid recursive sync loops between GitHub and Kanban.

Implementation sketch

• Add a command like hermes kanban sync-github --repo OWNER/REPO [--since ...] [--label ...].
• Use gh issue list/view or GitHub REST/GraphQL.
• Create Kanban tasks with triage=True and an idempotency key such as github-issue:OWNER/REPO#123.
• Optionally support a webhook/cron wrapper later, but default behavior should remain explicit/manual.

Acceptance criteria

• Running sync twice does not create duplicate Kanban tasks.
• New GitHub issues appear as Kanban triage cards with source links.
• No mirrored card is dispatched automatically.
• Dashboard makes the source issue visible/clickable.
• Tests cover idempotency and the triage-only behavior.