Skip to content

fix(kanban): keep initial blocked tasks sticky - #43479

Closed
scroasdale wants to merge 10 commits into
NousResearch:mainfrom
scroasdale:wt/t_54d2fb35
Closed

fix(kanban): keep initial blocked tasks sticky#43479
scroasdale wants to merge 10 commits into
NousResearch:mainfrom
scroasdale:wt/t_54d2fb35

Conversation

@scroasdale

Copy link
Copy Markdown

Summary

  • Record a blocked event when tasks are created directly with initial_status=blocked so dispatcher recompute does not auto-promote them without explicit unblock.
  • Use the board projection notifier_profile for Discord projection subscriptions when configured, with creator-profile fallback when absent.
  • Add focused regressions for sticky initial blocked create and configured projection notifier ownership.

Test Plan

  • python -m pytest tests/hermes_cli/test_kanban_blocked_sticky.py::test_initial_blocked_create_is_sticky_across_dispatcher_recompute tests/hermes_cli/test_kanban_core_functionality.py::test_create_projects_task_to_discord_forum_and_records_linkage tests/hermes_cli/test_kanban_core_functionality.py::test_create_projection_notifier_profile_falls_back_to_author_when_unconfigured -q -o 'addopts='
  • python -m pytest tests/hermes_cli/test_kanban_blocked_sticky.py tests/hermes_cli/test_kanban_core_functionality.py tests/hermes_cli/test_kanban_db.py::test_recompute_ready_skips_tasks_at_failure_limit -q -o 'addopts='
  • git diff --check

Notes

Full tests/hermes_cli was previously run in this environment and is not clean due to unrelated/baseline failures; focused Kanban coverage above passes.

hermes-agent and others added 10 commits June 10, 2026 09:54
- Resolve Discord thread-scoped Kanban lifecycle commands against notify subscriptions
- Add task context injection for gateway session prompts
- Add DB helper coverage for subscription lookup
- Add focused gateway/CLI regression tests

Refs: t_7bbd2997
(cherry picked from commit 8f1422b647c804119a9795edea17260933364695)
- pass Discord forum thread names and applied tags through live and standalone send paths
- wrap invalid Kanban DB header failures with corrupt-db backup handling
- add regression coverage for forum projection metadata forwarding

(cherry picked from commit fa644b684466afb11ec075df5f7e8c6204aec081)
(cherry picked from commit 5d00e8a3b70bede7f994b7c46385c8fcdf52f851)
(cherry picked from commit 2e5a09a234178cde211dcbbe633b24375bcd1035)
(cherry picked from commit 0793f62fc45c0de8d0c814f93ce0d744503a3a82)
(cherry picked from commit c233a0f10d1aeed4fdcb35cd1488001a03491446)
(cherry picked from commit c628f7e765b02745825c6c693e09ebc91d9503fb)
Port the preserved uncommitted Discord/Kanban projection and gateway follow-ups onto origin/main.
Record a blocked event for tasks created directly in blocked status so dispatcher recompute does not auto-promote them without an explicit unblock.

Use the board projection notifier_profile for Discord projection subscriptions when configured, falling back to the creating profile only when absent.
@scroasdale

Copy link
Copy Markdown
Author

Closed at Sam's request: this work is not ready for public upstream due diligence. Keeping the patch local/private for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/cron Cron scheduler and job management P3 Low — cosmetic, nice to have type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants