1 content migration and catalog refactors
forgejo-actions edited this page 2026-07-11 12:38:13 +00:00

Content Migration And Catalog Refactors

Purpose

Use this page when renaming ids, deleting catalog entries, normalizing schemas, migrating NPC data, or applying multi-asset text migrations that must be previewed, validated, and safely rolled back.

Steps

Start with a preview plan. Confirm impacted references through the authoring reference registry. Run before-validation. Apply through the authoring command bus or migration surface. Run after-validation and bake. Keep transaction metadata and reports attached to the change.

Expected Outputs

A migration should report changed files, skipped records, blockers, stale inputs, schema-normalization output, and rollback metadata where available. Successful refactors should leave no broken references in validation.

Common Mistakes

Do not apply a stale migration plan after assets changed. Do not rename an id without updating references. Do not bypass validation because the refactor is mechanical. Do not use global search/replace for structured assets when a parser-backed migration exists.

Recovery Paths

If a migration is wrong, use transaction history or rollback metadata first. Then rerun validation and inspect reference registry impacts. For partial writes, restore the affected asset files and rerun the migration from a fresh preview.