"=cargo install beads=" is wrong. The =bd= binary installed on this machine (v1.1.2, build 20e493e5) is a stripped Go executable --- `file` reports "ELF 64-bit ... Go BuildID=..."; its dependencies include golang.org/x/sys and google.golang.org/grpc --- not a Rust crate, and there is no cargo package to install. Corrected to the methods the binary's own error output recommends when embedded-Dolt support is missing: =brew install beads=, =npm install -g @beads/bd=, or the installer script. Separately, github.com/aygp-dr/beads (linked below) resolves (HTTP 200) but GitHub's API reports it as a fork (=fork: true=, =parent: gastownhall/beads=); steveyegge/beads, the name used in the install script's own URL and in this install's bundled =.beads/README.md=, now 301-redirects to gastownhall/beads. The link is the user's own fork and still works, so left as-is; noted here for anyone trying to find the canonical upstream.

Checked every command below against the installed =bd= v1.1.2 (this repo's own tracker). Three have drifted; left unedited in the code block per this pass's scope but flagged here. (1) =bd create -t "Fix login bug" -y bug= does not run: =-y= is not a registered flag on =bd create= (not in its =--help= output), and executing it directly returns "Error: unknown shorthand flag: 'y' in -y". The example also misuses =-t= (type) to hold the title. A working form is =bd create "Fix login bug" -t bug=. (2) =bd ready <issue-id> # Mark issue ready for work= --- =bd ready --help= describes it as "Show ready work (open issues with no active blockers)" and takes no issue-id positional at all; there is no "mark ready" action in this version. (3) =bd sync # Sync issues (pull from remote)= --- running it returns "Error: unknown command \"sync\" for \"bd\""; no =sync= subcommand exists in v1.1.2's full command list. =bd list=, =bd close=, and =bd show= are all still correct as written.

"Issues are stored in =.beads/issues.jsonl=" describes bd's original design, not this repo's actual current backend. =bd context= here reports =Backend: type dolt, mode embedded= --- an embedded SQL database (Dolt) is the live store, with =.beads/issues.jsonl= kept as a git-synced export rather than the source of truth; =bd doctor= confirms this repo's JSONL holds 306 issues with no local database present, flagging it a "Fresh Clone" that needs =bd bootstrap= to rebuild the database from the JSONL. The record schema has drifted too: older entries in this repo's own =issues.jsonl= use the =type=/=created=/=updated= field names shown below, but newer ones (=www.wal.sh-*= prefix) use =issue_type=/=created_at=/=updated_at= and omit =type= when it's the default; priority is stored as a plain integer (0-4) in every live record sampled, never a word like "medium". Left the example JSON and surrounding prose unedited (schema-literal rewrite is outside this pass's scope); flagging the drift here.