fix(tools/kanban): sync kanban_unblock response status with DB state

[Dusk1e]

Summary

• return the actual task status from kanban_unblock instead of always reporting ready
• add a regression test covering blocked child tasks with unfinished parents

Why

kanban_unblock could report ready even when the DB correctly re-gated the task to todo, which made the tool response inconsistent with actual board state.

Testing

• scripts/run_tests.sh tests/tools/test_kanban_tools.py -k unblock

  
============================== 5 passed in 3.41s ==============================

[teknium1]

Thanks for the focused regression fix. The premise is confirmed on current main: tools/kanban_tools.py:1074-1077 calls unblock_task() but always returns status="ready", while hermes_cli/kanban_db.py:5079-5107 deliberately persists todo for tasks with unfinished parents. The added tool-level test covers the missing response contract above the existing DB-layer state-transition test at tests/hermes_cli/test_kanban_db.py:1425-1449.

Problems

• The change leaves model-facing schema text stale: tools/kanban_tools.py:1562-1572 still tells agents that unblocking returns a task to ready.
• User/reference docs have the same stale guarantee at website/docs/reference/tools-reference.md:133 and website/docs/user-guide/features/kanban.md:276. The event reference already states the correct ready or todo outcome at website/docs/user-guide/features/kanban.md:905.

Suggested changes

• Update the handler docstring/schema and the two documentation entries to describe the parent-gated ready/todo result.

Automated hermes-sweeper review.

[teknium1]

Superseded and merged via #66571 — your response-status fix (return the persisted status instead of hardcoding ready) is preserved in history via rebase. Thanks @Dusk1e.