feat(kanban): expose per-task reasoning in tool and CLI

[alexferrari88]

Summary

PR #76417 added Kanban task-level reasoning_effort storage, Desktop/REST controls, and dispatcher propagation. The coordinator tool and human Kanban CLI could not set that existing field when creating a task.

This change completes that surface parity:

• adds optional reasoning_effort to kanban_create
• adds --reasoning LEVEL to hermes kanban create
• exposes the stored value in tool and CLI JSON/show output
• preserves omitted/empty as profile inheritance while keeping none as an explicit value
• documents coordinator and CLI usage

The implementation reuses the existing database normalization and dispatcher path from #76417. It does not change the database, dispatcher, REST API, Desktop UI, or conversation loop.

Prior art: #47476 proposed the tool and CLI surfaces before #76417 established the final reasoning_effort schema.

Verification

• PYTHONDONTWRITEBYTECODE=1 scripts/run_tests.sh tests/tools/test_kanban_tools.py tests/hermes_cli/test_kanban_cli.py tests/plugins/test_kanban_model_override.py -q
  • 59 passed
• PYTHONDONTWRITEBYTECODE=1 scripts/run_tests.sh tests/hermes_cli/test_kanban_db.py tests/hermes_cli/test_kanban_core_functionality.py tests/hermes_cli/test_kanban_cli_dispatch_passthrough.py -q
  • 56 passed
• python -m ruff check tools/kanban_tools.py hermes_cli/kanban.py tests/tools/test_kanban_tools.py tests/hermes_cli/test_kanban_cli.py
  • passed
• git diff --check origin/main...HEAD
  • passed

Independent acceptance also exercised explicit effort, none, omitted/empty inheritance, invalid-value rejection without creating a task, model/provider coexistence, and list/show/JSON visibility.