[Feature]: hermes agent support

[lee-b]

Problem

hermes agent can be more robust than the likes of opencode. Whilst a "claw" in one mode, hermes agent is also capable of being used as a regular TUI agentic dev agent. Using it this way, it can keep going, recovering from errors like tool call syntax failures, which would stop opencode, resulting in no progress until attended to by a human. So, especially for automated agents chomping through kanban tasks, this hermes agent support would be nice to have.

NOTE: hermes does have it's own kanban dashboard, but kandev is much nicer to use, and potentially more reliable for the kanban part.

Proposed solution

Add a new agent definition for hermes agent.

Affected area

agentctl

Who needs this?

Individual developer

Target workflow

• Alternate agent

Alternatives considered

• Alternate agentic dev tool
• Hermes Agent's Kanban board
• vibe-kanban

Acceptance criteria

• Hermes Agent is listed in the agents supported, can be selected/installed, works

Risks and constraints

No response

References

No response

Before submitting

• I checked existing issues and did not find this request already tracked.
• This request describes user value, not only an implementation detail.

[Snailflyer]

For Hermes support, I would make the adapter prove more than "Hermes is selectable".

Since the value here is Kanban reliability, the receipt should include:

• task id and project/cwd
• selected provider: Hermes
• live process/session id or generation
• first output cursor after dispatch
• last heartbeat while the task is running
• restart behavior: rebound_same_session, resumed_stored_session, fresh_session, or stale_task

That keeps kandev's board as the nicer project-management surface while still proving that the underlying Hermes session owns the task and can recover cleanly after errors or restarts.

Adjacent reference: I maintain Faryo, a smaller project/mobile workbench for same live tmux-backed coding sessions. The same boundary applies there: project state is useful only after the action routes into the original live session.
https://github.com/Snailflyer/faryo/releases/tag/v1.0.8