fix: correct dependency field names in beads tracker

[roberto-mello]

Summary

• Fixed BeadJson interface field names to match actual bd list --json output
• Fixed beadToTask function to use correct field names for dependency parsing

Problem

The BeadJson interface had incorrect field names for dependencies that didn't match the actual bd output:

• dependencies[].id should be dependencies[].depends_on_id
• dependencies[].dependency_type should be dependencies[].type

This caused dependsOn to never be populated, making all tasks appear as "actionable" instead of properly detecting blocked tasks. The TUI would show blocked tasks as ready to work on.

Tests ran

• bun run typecheck passes
• bun run build passes
• Run ralph-tui run --epic <epic-id> with tasks that have blocking dependencies
• Verify blocked tasks show red "blocked" indicator instead of green "actionable"
• Verify task list sorts correctly (actionable tasks before blocked tasks)

Summary by CodeRabbit

• Refactor
  • Updated internal dependency tracking data structure for improved system efficiency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

@roberto-mello is attempting to deploy a commit to the plgeek Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The Beads tracker plugin's dependency object structure is refactored, renaming fields (id → issue_id, dependency_type → type), removing title and status, and introducing an optional created_at field. Function references are updated accordingly.

Changes

Cohort / File(s)	Summary
Beads Tracker Dependency Schema src/plugins/trackers/builtin/beads/index.ts	BeadJson dependency item interface restructured: id renamed to issue_id, dependency_type renamed to type, title and status fields removed, created_at field added as optional. Updated beadToTask function to reference dep.type and dep.depends_on_id.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A hop through the schema, fields dance and reorganise,
Dependencies reshape in logical disguise,
From id to issue_id we swiftly transform,
New fields arrive whilst old ones reform—
A tidy tracker, clean and wise! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarises the main change: correcting dependency field names in the beads tracker component to match the actual API output.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/plugins/trackers/builtin/beads/index.ts (1)

48-53: Both dependencies and dependents should be simple string arrays of issue IDs, not objects.

According to bd CLI documentation, both dependencies and dependents fields should contain arrays of issue ID strings (e.g., ["bd-xxxx", "bd-yyyy"]), not arrays of objects with id, title, status, and dependency_type fields. Update the type definitions for both fields to match the actual bd CLI output structure: dependencies?: string[] and dependents?: string[].

[subsy]

@roberto-mello

This PR changes the field names to match the raw storage format in issues.jsonl, but the code actually parses bd show --json output, which returns a different (expanded) format:

• Raw storage: depends_on_id, type
• bd show --json: id, dependency_type

The current code on main is correct I think. Merging this would break dependency parsing since dep.depends_on_id and dep.type would be undefined in the actual CLI output.Let me know if you think I'm missing something here.