Repository navigation
chore: stop tracking beads SQLite sidecar files - #71
Conversation
They change on every beads write, so the board's base checkout always looked dirty and could not fast-forward. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
QA panel review — PASS
code-review · head 91fc98c0bf6f · formal
Clean pass — all four finders and the structural engine returned no defects, and the verifier confirmed there was nothing to verify. No disagreements, no refutations, no uncertain items to carry forward. If this PR touches production code, the silence is a genuine clean rather than a coverage gap; no heavily-changed file went unexamined.
No findings — the review came back clean.
findings JSON (machine-readable)
[]Runner context: observed. Native parent-conversation exclusion and separate history exclusion are checked per execution. Intended prior findings may remain in the rendered prompt. Instruction-source observations describe the assembled system prompt; mandatory repository guidance remains applicable. External instruction sources and runtime additions remain unknown. Tool observations describe bound tools, inherited fence and enforcement; external policy remains unknown. Construction evidence does not establish semantic review coverage.
Raw finding accounting: unsupported
{"supported": false, "complete": null, "gaps": [], "status": "unsupported"}
.beads/beads.db-shmand.beads/beads.db-wal(SQLite WAL sidecars) were committed. They change on every beads write, so protoEngineer's board saw the base checkout as dirty and couldn't fast-forward it (stale_base_checkouts: release-tools: uncommitted changes to .beads/beads.db-shm, .beads/beads.db-wal). This untracks them and adds them, plus.beads/.write.lock, to .gitignore. The files on disk are unchanged.🤖 Generated with Claude Code