Skip to content

Remove obsolete Beads integration - #14

Merged
pasunboneleve merged 1 commit into
mainfrom
codex/gv5z-remove-beads
Aug 26, 2026
Merged

Remove obsolete Beads integration#14
pasunboneleve merged 1 commit into
mainfrom
codex/gv5z-remove-beads

Conversation

@pasunboneleve

Copy link
Copy Markdown
Owner

Summary

  • remove the obsolete tracked .beads tree
  • replace Claude's bd prime hooks with Kata session attention hooks
  • retain the existing .githooks formatting hook and Kata project binding

Validation

  • jq empty .claude/settings.json
  • hidden-tree scan confirms no live Beads references remain
  • .kata.toml and .githooks/pre-commit remain present
  • git diff HEAD^ --check
  • Roborev job 217 finding fixed; verification job 218 found no issues

The Rust runtime is unchanged, so local Rust tests were not rerun. GitHub's required Linux and macOS PR checks provide the repository-wide gate.

No changelog or version change: this is internal task-tracking cleanup and does not trigger an artifact release.

Context:
Devloop uses Kata, but tracked Beads metadata and Claude hooks still invoked `bd prime`.

Decision:
Delete the tracked `.beads` tree and replace the Claude Beads hooks with Kata's supported session attention hooks.

Alternatives considered:
Keeping dormant Beads files would preserve unused current-tree state and allow hooks to recreate its database, so Git history remains the archive instead.

Tradeoffs:
Developers who intentionally relied on the old Beads database must recover it from repository history.

Architectural impact:
Kata is now the sole active task-tracking integration; the existing `.githooks` path continues to own Git commit formatting.
@pasunboneleve
pasunboneleve merged commit 058dd52 into main Aug 26, 2026
2 checks passed
@pasunboneleve
pasunboneleve deleted the codex/gv5z-remove-beads branch August 26, 2026 08:55
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