When using beads as the tracker, ralph-tui shows tasks in the wrong order. I have 18 tasks chained with dependencies (task 2 blocked by task 1, task 3 blocked by task 2, etc). Ralph shows them backwards - it wants to start with task 18 instead of task 1.

Dug into it a bit - looks like the beads plugin uses bd list --json which returns dependencies: null for every task. So ralph has no way to know which tasks are blocked. But bd ready --json correctly returns only the unblocked tasks (in my case, just task 1).

Would it make sense to switch to using bd ready instead of bd list for getting available tasks? That command already handles all the dependency filtering.