chore: remove beads (bd) issue tracker

[frankbria]

What

Removes the beads (bd) issue tracker, which we weren't using as intended and whose git hooks were interfering with commits (the pre-commit bd-sync hook aborted commits when the daemon flush failed — hit during the #659 work).

• Untracks the only committed artifact: .beads/issues.jsonl
• Drops the .beads/ / !.beads/*.jsonl entries from .gitignore

Local cleanup (outside version control, already done on this machine)

• Removed the bd pre-commit and post-merge git hooks
• Restored the real secret-scanning pre-commit hook that beads had displaced (it had been backed up to pre-commit.backup)
• Stopped the bd daemon(s) and the .beads/ working directory

No production code touched.

[coderabbitai]

Warning

Review limit reached

@frankbria, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 1 hour, 21 minutes, and 13 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b9a73530-303c-45da-8dd2-b9453a9670d2

📥 Commits

Reviewing files that changed from the base of the PR and between 339af60 and 9a1c9eb.

📒 Files selected for processing (2)

• .beads/issues.jsonl
• .gitignore

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/remove-beads

---

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

[claude]

Code Review — chore: remove beads (bd) issue tracker

Overview

This is a clean chore PR that removes the bd (beads) issue tracker from the repository. The changes are minimal and focused:

• .beads/issues.jsonl (200 lines) — untracked and deleted
• .gitignore — 3 lines removed (# Beads, .beads/, !.beads/*.jsonl)

No production code is touched. The PR description is unusually thorough for a chore — good.

---

What's Good

• Correct scope: Only the two files that need changing are touched. Nothing else.
• Well-motivated: The pre-commit hook interference is a concrete, reproducible problem (daemon flush failure → commit abort). Removing the tool is the right call if it wasn't providing value.
• Security hook restored: The PR description calls out that the real secret-scanning pre-commit hook was restored after beads had displaced it. That's the most important outcome here — worth highlighting even if it happened outside VCS.

---

Observations

Historical data in git history: The 200-entry issues.jsonl file will remain in git history after this. That's intentional (no history rewrite needed), but worth noting in case anyone searches for the data later — git log --all --full-history -- .beads/issues.jsonl will find it.

.gitignore gap: After removing .beads/ from .gitignore, if bd is accidentally re-initialized in a future working tree, its files won't be gitignored and could be staged accidentally. This is acceptable since the tool is being abandoned, but worth a mental note. No action needed.

Local hook cleanup outside VCS: The PR description notes the git hooks (pre-commit, post-merge) and daemon were cleaned up locally, not via this PR. This is correct — .git/hooks/ isn't tracked — but it means other contributors who cloned before the tool was removed may still have the bd hooks active. A brief team note suggesting contributors check .git/hooks/pre-commit would be a nice-to-have for awareness.

---

Verdict

Approve. This is a focused, well-described cleanup with no risk to production code. The security hook restoration is the most important side effect, and the PR correctly surfaces it.

The one optional follow-up: if any other contributors are working in this repo with local bd hook installs, a quick heads-up that they should check .git/hooks/pre-commit would prevent them from hitting the same pre-commit blocking issue.

[claude]

Follow-up Review

No new commits beyond the original chore commit and the merge-from-main rebase. My prior review stands in full.

Summary for merge readiness:

• The beads issues.jsonl file is deleted (200 stale entries, none needed)
• The gitignore is trimmed of the 3 beads entries
• No production code touched
• Secret-scanning pre-commit hook restored (noted in PR description)

Nothing new to flag. Ready to merge.

[claude]

Follow-up Review (merge-from-main sync)

A third merge-from-main commit (9a1c9ebd) landed since my last review. Changed files are still identical: .beads/issues.jsonl (deleted) and .gitignore (3 lines removed). No new content introduced.

My prior two reviews stand. This PR remains clean and ready to merge.