fix(kanban): preserve orchestrator lifecycle

[voidfreud]

Summary

• separate task-lifecycle Kanban access from explicit board-routing capability, including for dispatcher-spawned orchestrator profiles
• make kanban_create reject unknown profile assignees before creating stranded cards
• keep orchestrator roots alive through dependency blocking and resumption, with implementation → reviewer dependencies instead of review-required deadlocks
• inject full worker guidance only in dispatcher-scoped sessions and update the Kanban docs to match

Verification

• uv run --extra dev pytest tests/tools/test_kanban_tools.py tests/agent/test_prompt_builder.py -q — 90 passed, 1 skipped
• uv run --extra dev pytest tests/agent/test_system_prompt.py tests/test_model_tools.py tests/hermes_cli/test_kanban_worker_spawn_toolsets.py -q — 33 passed
• uv run --extra dev pytest tests/hermes_cli/test_kanban_notify.py tests/gateway/test_kanban_notifier.py tests/tui_gateway/test_kanban_notify_poller.py -q — 21 passed
• uv run --extra dev ruff check ... — clean
• live smoke test with the branch gateway: Default created one Orchestrator root; Orchestrator created Researcher → Reviewer dependencies, dependency-blocked its own root, resumed in a second run after both parents completed, inspected both handoffs, and completed with the verified result

[teknium1]

Thanks for tracing the dispatcher lifecycle end-to-end. The premise is real: current main tells dispatcher-scoped orchestrators to fan out in agent/prompt_builder.py:254-266, but excludes those same workers from the routing gate in tools/kanban_tools.py:111-124; kanban_create and kanban_link use that gate at tools/kanban_tools.py:2210-2234.

Problems

• tools/kanban_tools.py:60 changes the established toolsets: [kanban] contract to an exclusive platform_toolsets.cli lookup. The original two-tier routing commit, 2704e7b67e, explicitly established toolsets: [kanban] for orchestrators. Please retain compatibility or provide a migration plus coverage.
• The changed default_assignee documentation is inaccurate. hermes_cli/kanban_decompose.py:201-214 falls back to the active profile or default, and lines 252-268 rewrite invalid/absent decomposition assignees to that fallback.

Suggested changes

• Keep the legacy configuration path working while recognizing the platform-scoped form, and test a real dispatcher-spawned routing profile.
• Restore the documented fallback behavior for kanban.default_assignee.

Automated hermes-sweeper review.

[alt-glitch]

This was generated by AI during triage.

Related: #64186 and #68608 both change Kanban guidance dispatch. This PR adopts a broader lifecycle and routing contract, including dispatcher-spawned orchestrators and dependency resumption; maintainers should choose the intended contract rather than treating these as duplicates.