Skip to content

fix: use explicit priority for task provider registration#14

Merged
kostyay merged 1 commit intomainfrom
fix/task-provider-priority-ordering
Jan 13, 2026
Merged

fix: use explicit priority for task provider registration#14
kostyay merged 1 commit intomainfrom
fix/task-provider-priority-ordering

Conversation

@kostyay
Copy link
Owner

@kostyay kostyay commented Jan 13, 2026

Summary

  • Fix kt tasks not showing when running with -test flag in directories with .ktickets
  • Go's gofmt sorts imports alphabetically, causing beads to register before kt
  • Changed to explicit RegisterWithPriority() with priority constants (kt=10, tk=20, beads=30)

Test plan

  • Run claude-status -test in a directory with .ktickets - now shows kt tasks
  • All existing tests pass
  • Added registry priority tests

🤖 Generated with Claude Code

Go's gofmt sorts imports alphabetically, causing beads to register
before kt regardless of comment-based ordering intent. This meant
beads was checked first and would win when both providers were
available in a directory.

Changed from order-dependent Register() to RegisterWithPriority()
with explicit priority constants (kt=10, tk=20, beads=30). The
registry now sorts by priority, ensuring kt is always checked first.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@kostyay kostyay merged commit 2bc47c2 into main Jan 13, 2026
2 checks passed
@kostyay kostyay deleted the fix/task-provider-priority-ordering branch January 13, 2026 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant