Grace Migrate

<skill>

<migration_safety>

Migration is copy-and-validate, not destructive conversion. Before writing .grace, inventory every legacy source, record a restorable backup path outside the proposed cleanup set, present the migration report, and wait for explicit write approval. Never create retroactive C-* bundles.

</migration_safety>

<workflow>

• Detect legacy docs and current .grace state. If .grace already exists, stop and ask whether migration should merge, replace, or abort.
• Inventory legacy source paths and create or verify a restorable backup. Record source coverage and backup evidence in the report.
• Map legacy requirements, technology, graph, verification, and operational content into the GRACE 4 layout. List ambiguities and unsupported structures rather than guessing.
• Produce references/migration-report-template.xml, review references/migration-checklist.md, and ask for explicit approval before writing .grace.
• Write .grace, then run grace lint --path <project-root> --assertions current and grace status --path <project-root> --json. Require status projectKind grace4 with no integrity errors, and record commands, exit states, and findings.
• If validation is not successful or generated coverage is incomplete, retain all legacy sources and stop.
• Detect git availability and worktree membership. If git is available for the project, record git status --porcelain --untracked-files=all before cleanup.
• Present an exact cleanup proposal containing only inventoried legacy paths. Ask for a separate explicit cleanup approval. For a dirty worktree or non-git project, require another explicit acknowledgement naming that risk.
• Archive or delete only the approved paths, record each result, and leave the backup intact. Do not use broad globs, hidden shell cleanup, or unreviewed recursive deletion.

</workflow>

<cleanup_preconditions>

Cleanup requires all of: complete inventory, restorable backup, explicit write approval, successful current lint, fresh status proving GRACE 4 with no integrity errors, verified generated coverage, git availability/worktree inspection, recorded porcelain output when applicable, exact proposed paths, separate explicit cleanup approval, and separate dirty or non-git risk acknowledgement when applicable. A missing gate means no cleanup.

</cleanup_preconditions>

<cleanup_failure_rule>

If validation, git inspection, move, archive, or delete fails, stop immediately and state: "Legacy GRACE 3 artifacts remain untouched unless the failure output explicitly lists a completed move." Never retry destructive cleanup automatically.

</cleanup_failure_rule>

</skill>