bd-to-br-migration

To migrate documentation from beads to beads_rust, you apply an automated transformation that updates bd commands and references to br equivalents across Markdown files like AGENTS.md, enforcing a fixed transform order for consistency.

The process updates bd references to br in AGENTS.md by applying a fixed transform order, removing deprecated daemon references, and requiring verification to ensure no remaining bd references exist in the Markdown file.

Yes, the beads to beads_rust migration automatically removes deprecated daemon references during the transformation process, ensuring outdated daemon configurations are cleaned up alongside updating bd commands to br equivalents.

You verify no remaining bd references exist by running the built-in verification step after migration, which checks the Markdown files to ensure all bd commands and beads references have been successfully updated to br equivalents.

Yes, you can use this migration for related Markdown files and migration scenarios beyond AGENTS.md, as long as they contain bd commands and beads references that need updating to br equivalents.

The automation enforces a fixed transform order and requires verification, meaning it follows a strict transformation sequence that may not accommodate custom or non-standard bd reference patterns outside typical Markdown migration scenarios.