feat: add Kanban PR review lifecycle

[tw3akercc]

Summary

• Adds PR review lifecycle states for Hermes Kanban coding tasks: in_review, code_review, and merge_ready.
• Moves PR-bearing task completions into review instead of treating “PR opened” as done.
• Adds a one-shot PR review poller that classifies pending/failed/green checks and review-thread feedback while tracking seen IDs.
• Reserves done for post-merge/deployed work; green + approved now becomes merge_ready.

Test Plan

• python -m pytest tests/hermes_cli/test_kanban_pr_review.py tests/hermes_cli/test_kanban_core_functionality.py tests/hermes_cli/test_kanban_cli.py tests/hermes_cli/test_kanban_db.py tests/plugins/test_kanban_dashboard_plugin.py tests/tools/test_kanban_tools.py -o 'addopts=' -q
• git diff --check

Notes

• This came from Kanban task t_29782dca.
• Branch was pushed from a fork because the local GitHub account does not have direct push permission to NousResearch/hermes-agent.

[teknium1]

Thanks @tw3akercc — closing this one. Multi-state PR-review lifecycle (in_review/code_review/merge_ready statuses with prompts/skills/dashboard changes) is design-level scope (1139 LOC). We just landed review as a status via #28449 (salvage of #23772) which is simpler and uses the dispatcher's existing claim+spawn lifecycle. A multi-state PR-review workflow on top of that needs design discussion: what does each state mean, who transitions, how does it interact with the existing review column. If you want to revisit, an issue first would help.