project-setup

To migrate a repository safely, you need a consent-gated migration plan that uses worktree isolation and moves files instead of deleting them to preserve history. This approach prevents unsafe migrations and accidental overwrites during workspace restructuring.

Repository topology detection analyzes project layouts, stacks, and workspace structures by reading repository signals before making changes. You need it when onboarding existing repositories into a vwf workflow to understand the current state and prevent undocumented changes.

Upgrading blueprint formats requires blueprint version tracking to migrate outdated structures to the latest vwf blueprint format. This process keeps CLAUDE.md workflow guidance synchronized with the current vwf process during repository onboarding.

Yes, consent-gated migration planning allows you to create dry-run migration plans before applying any changes. This validates the repository state and ensures workspace restructuring happens safely through worktree isolation without unexpected overwrites.

Worktree isolation requires valid repository state validation before it can safely apply changes. Limitations include the need for consent-gated execution and the constraint that all file modifications must move rather than delete to preserve history during topology detection and migration.