bd-to-br-migration

To migrate documentation from bd to br, apply a strict, order-sensitive set of transforms across your files. The process converts section headers, command names, and workflow steps to match the new beads_rust toolchain.

Batch processing bd to br migration applies exact, ordered replacements across multiple files simultaneously. It ensures consistent headers and command names while automatically removing legacy bd daemon, auto-commit, and RPC references.

The br migration automatically converts bd commands to br equivalents and enforces required post-sync steps. It ensures you perform git add and commit operations after the transformation is applied.

Yes, you can verify no legacy bd references remain by running a dedicated verification script. This verifier checks that all bd-specific references are removed and all required br patterns are present in the output.

Order matters because the migration enforces exact, ordered replacements for headers, command names, and workflow steps. Applying transforms in sequence prevents partial matches and ensures all bd-specific references are properly converted.

The bd to br migration supports both single-file migrations and batch processing across multiple files. Both modes apply the same strict, order-sensitive transforms to ensure consistent results across your documentation.