migrate

Migrate a repository to another lab's compute resources by discovering the current server, user, Slurm, and storage environment to generate a correction-focused migration plan. It requires explicit user permission before applying any edits.

Auditing repo assumptions safely involves performing a non-destructive discovery scan that identifies cluster-specific compute needs and risks without modifying files. Findings are summarized for explicit user validation before any edits are made.

Yes, you can migrate to different lab compute resources safely because the workflow focuses on non-destructive discovery and explicit user validation. It generates a guarded migration plan and requires permission before any file edits are applied.

Document cross-cluster migration risks by running the discovery workflow to generate reproducible documentation. It records findings, risks, and repository assumptions to guide cross-cluster migrations and compute resource audits.

The limitation of automated Slurm environment discovery for repo migrations is that it cannot apply changes autonomously. It generates a draft migration plan and requires explicit user permission and validation before editing any repository files.