migrate-managed-claude-md

Adding VE markers to CLAUDE.md safely requires detecting existing content boundaries and wrapping only the managed sections. The migration process preserves all user customizations outside the markers and generates a MIGRATION.md log to track the boundary detection results.

VE-managed boundaries are specific markers inserted into markdown files like CLAUDE.md to isolate managed content. They ensure future automated operations only modify the designated sections, preventing accidental edits to surrounding user content.

VE marker migration supports marker insertion without altering surrounding whitespace. It explicitly preserves content outside the managed boundaries to ensure a non-destructive migration of your existing markdown files.

When no existing VE-managed sections are detected in a CLAUDE.md file, the migration plan appends the VE markers at the end of the file. This establishes the managed boundary while keeping all current content intact.

Tracking boundary detection results during migration is handled by generating a MIGRATION.md file. This log records the boundary findings, decisions, and progress of the marker insertion process for review.

Yes, the migration validates and wraps content so that future ve init operations only modify the designated VE-managed section. This setup prevents accidental automated edits to your customized content.