hermes - 💡(How to fix) Fix External worker-lane plugin API for AgentPlane-style supervisors

Summary

There is now a public AgentPlane Hermes plugin that implements an external worker-lane integration for Hermes Kanban:

https://github.com/basilisk-labs/agentplane-hermes-plugin

The plugin is intentionally conservative: it can run doctor/registry checks today and registers native worker lanes only when Hermes exposes a public worker-lane API. It does not write directly to kanban.db.

Use case

Kanban cards with assignees like agentplane-* should be spawnable without creating fake Hermes profiles. Instead, Hermes should delegate those cards to an external supervisor command such as:

agentplane hermes supervise <task-id> --root <repo> --json

This lets Hermes keep ownership of Kanban lifecycle state while AgentPlane handles its own terminal gate, evidence, and agent workflow controls.

Requested public surface

A small plugin-facing API would be enough:

register_worker_lane(match, spawn_fn, profile_exists=True)

and dispatch integration in:

• gateway dispatcher
• hermes kanban dispatch
• dashboard dispatch endpoint

Useful lifecycle context for spawn_fn:

• task id
• board
• run id
• workspace/repo root
• claim lock
• structured card metadata

Useful lifecycle helpers for plugins or external supervisors:

• comment
• block
• complete
• heartbeat
• current-run / stale-run guard

Why this should be plugin API rather than a fork

Without a worker-lane registry, external lanes have to monkeypatch dispatch internals or pretend to be Hermes profiles. Both are brittle. A public registry keeps Hermes in control of task/run ownership and makes integrations like AgentPlane first-class without requiring Hermes core to vendor every external supervisor.

Existing implementation

The current plugin is here:

https://github.com/basilisk-labs/agentplane-hermes-plugin

It ships:

• plugin.yaml
• lane registry example
• hermes agentplane doctor --json path when CLI registration is available
• native register_worker_lane path when Hermes exposes it
• explicit no-direct-kanban.db boundary

This issue is meant to track the minimal upstream hook that would make that plugin fully native.