Skip to content

fix(docs): correct beads-rust reference + stale "SQLite data model" claim#16

Merged
mabry1985 merged 1 commit into
mainfrom
fix/beads-rust-and-projection-docs
Jun 13, 2026
Merged

fix(docs): correct beads-rust reference + stale "SQLite data model" claim#16
mabry1985 merged 1 commit into
mainfrom
fix/beads-rust-and-projection-docs

Conversation

@mabry1985

Copy link
Copy Markdown
Member

Two accuracy fixes (no behaviour change), both spotted in review:

  1. "Projection over beads" is true — but one docstring lied. store.py has no separate store (every op shells br; beads owns .beads/*.db + JSONL), yet __init__.py still called the board "a SQLite data model" (pre-beads-migration leftover, contradicting store.py). Fixed.
  2. It's beads-rust (br), not the homebrew bd. The code was already correct (BR defaults to br), but the README linked the wrong repo (steveyegge/beads). Now points at Dicklesworthstone/beads_rust + cargo install beads_rust, warns off the stale write-broken bd, and the store's not-on-PATH error says the same.

Docs + one error message only. 116 tests green, ruff clean.

…model" claim

Two accuracy fixes (no behaviour change):

- The board IS a projection over beads (store.py only shells `br` — no separate
  store; beads owns the .beads/*.db + JSONL), but __init__.py's module docstring
  still called it "a SQLite data model" — a leftover from before the beads migration
  (D8) that directly contradicted store.py. Fixed to say projection-over-beads.
- The dependency is **beads-rust** (`br`, crate `beads_rust`), NOT the stale
  write-broken homebrew `bd`. The README linked the wrong repo (steveyegge/beads);
  point it at Dicklesworthstone/beads_rust + `cargo install beads_rust`, warn off
  `bd`, and make the store's not-on-PATH error say the same.

The code was already correct (BR defaults to `br`, BR_BIN override); this only fixes
docs + one error message.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@protoquinn

protoquinn Bot commented Jun 13, 2026

Copy link
Copy Markdown

👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow.

@protoquinn protoquinn Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA Audit — PR #16 | fix(docs): correct beads-rust reference + stale "SQLite data model" claim

VERDICT: PASS (pending CI) — non-blocking comment; CI still queued.


CI Status

  • test: queued

Diff Review

  • README: steveyegge/beadsDicklesworthstone/beads_rust with install command + bd warning. Correct — the code defaults BR to br (beads-rust), not the stale homebrew bd.
  • __init__.py: "SQLite data model" → "projection over beads (br)". Accurate — store.py shells br; beads owns .beads/*.db + JSONL.
  • store.py: error message now says "beads-rust" and warns off bd. Consistent with README.

Observations

  • LOW: CI still queued at review time; re-dispatch will submit the formal APPROVED once terminal-green.
  • All changes are docs + error-string only; zero behavioral risk. 3 files, ~25 net lines, no security paths.

— Quinn, QA Engineer

@mabry1985
mabry1985 merged commit abe1ddb into main Jun 13, 2026
1 check passed
@protoquinn

protoquinn Bot commented Jun 13, 2026

Copy link
Copy Markdown

Submitted COMMENT review on protoLabsAI/projectBoard-plugin#16.

@mabry1985
mabry1985 deleted the fix/beads-rust-and-projection-docs branch June 13, 2026 06:54
@mabry1985 mabry1985 mentioned this pull request Jun 13, 2026
protoquinn Bot pushed a commit that referenced this pull request Jun 13, 2026
Docs/accuracy patch over v0.4.0 (#16): correct the board's projection-over-beads
docstring (was a stale "SQLite data model" claim) and the beads-rust reference
(real repo Dicklesworthstone/beads_rust + `cargo install beads_rust`; warn off the
homebrew `bd`). No behaviour change.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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