bd-to-br-migration

Migrating beads documentation to beads_rust requires updating command syntax, converting issue IDs from bd-### to br-###, and revising sync behavior descriptions to reflect beads_rust's non-invasive nature.

Converting bd commands to br equivalents involves renaming commands, transforming sync behavior, and enforcing manual Git commit requirements. The br system operates non-invasively, requiring users to handle version control steps manually.

Updating issue IDs from bd-### to br-### requires scanning documentation files like AGENTS.md and systematically replacing all references. This ensures issue tracking remains consistent across the migrated beads_rust system.

Yes, beads_rust operates non-invasively, meaning it does not automatically perform Git commits. After running br commands, you must manually execute Git commits to track changes.

Yes, you can automate AGENTS.md file updates for beads_rust migration by using scripting tools that handle command transformation and issue ID renaming. This ensures all bd references are correctly updated to br syntax.

Migrating bd docs to br syntax requires careful handling of behavioral changes, as br's non-invasive nature and manual Git requirements must be clearly documented. Automated transformation may not capture all nuanced behavioral context without review.