migratelisted

# migrate - bring an existing repo into `.credo/` A generic, reusable procedure to migrate ANY existing repo into the credo target form. It tells you HOW to reach that end state safely. Everywhere below, `<repo>` is the target repo and "the user" is its owner. This skill contains no personal, project-specific, or absolute-path data. ## Target form: what "conformant" means here (authority) The binding target form is defined INSIDE this plugin, not by any external design document. At the end of a migration, everything under `.credo/` must match: - **The scaffolded tree** produced by `"${CLAUDE_PLUGIN_ROOT}/scripts/credo-init.sh"` - folder layout and the files it creates (see step 1). That tree is the layout authority. - **The `items` skill** - the work-item model: folder = status, the lean frontmatter, the body sections, the Definition of Done, and id issuance. - **The `safety` skill** - the highest-priority filesystem-protection and no-autonomous-installs rules; they bind this whole procedure. - **The `requirements-verbatim` skill** - the append-only, never-censored requirements log and the strict separation of user-verbatim text from any assistant proposal. - **The `verify` skill** - what a real (visual, per-viewport) verification is, which governs whether a criterion counts as `exercised`. - **The `budget` skill** - budget caps and the commit-identity gate, when a migration run is autonomous and commits anything. Reference these by name. If any instruction p