bd-to-br-migration

To migrate documentation from beads to beads_rust, you apply deterministic transforms that update AGENTS.md references, remove bd-specific content, and map commands like bd ready/list/show to br equivalents.

Deterministic transforms for bd to br migration are ordered rules that enforce section header changes, cross-link updates, and command mappings, ensuring workflows align with the new beads_rust toolchain predictably.

Yes, you can batch migrate multiple files from bd to br. The migration process supports both single-file and batch migrations while keeping references in place across the documentation.

You verify no beads references remain after migration by executing the provided verification scripts. These scripts apply strict validation to prevent any lingering bd references in the migrated files.

Yes, the bd to br migration updates AGENTS.md workflow steps. It inserts guidance notes after beads headers and updates workflows with br sync --flush-only plus git steps, article links, and IDs.

A key limitation of automated bd to br migration is that it enforces strict validation using provided scripts, meaning any deviations from expected reference patterns or unmapped bd content may halt the process.