lumi-migrate-legacy

To backfill missing provenance and confidence fields in legacy wiki entries, run a migration that reads CHANGELOG specs and lint findings to infer missing schema metadata conservatively, then applies idempotent frontmatter updates. This ensures your source and concept pages meet current schema requirements.

Wiki pages show lint errors after a schema upgrade because legacy entries are missing newly introduced frontmatter fields like provenance and confidence. You can resolve these L01/L11 lint findings by running a targeted backfill process that updates the frontmatter and clears the legacy migration flag.

The best way to update frontmatter on legacy pages without overwriting existing data is to use an idempotent atomic update process like set-meta. This method backfills only the missing provenance and confidence fields, and can optionally populate external_ids from canonical urls without touching existing values.

You can infer provenance for old documents by cross-referencing the manifest, lint results, ingest checkpoints, and raw file discovery. This evidence-based approach conservatively estimates the missing metadata required by the new schema rather than relying on manual entry.

Yes, the schema backfill process automatically verifies that lint errors are eliminated by re-running lint checks after applying the frontmatter updates. It continues this verification loop until all errors are resolved and clears the legacyMigrationNeeded flag in the manifest.

Yes, you can populate external_ids from canonical urls during the legacy wiki migration by using the --backfill-ids option. This enriches the schema without overwriting any existing external_id values already present in the frontmatter.