content-migration

# zuvo:content-migration — CMS-to-SSG Content Parity Check & Fix Compare an old CMS page with its new SSG version. Report parity gaps. Optionally apply safe additive patches to the local markdown source. **One page pair per invocation.** For bulk progress, use `--status`. **Out of scope:** SEO optimization (`zuvo:seo-audit`), content hygiene (`zuvo:content-audit`), pixel-level visual comparison, redirect mapping. --- ## Mandatory File Loading Read before work begins: 1. `../../shared/includes/env-compat.md` -- Environment adaptation 2. `../../shared/includes/live-probe-protocol.md` -- Consent + rate limiting Load on demand: - `../../shared/includes/codesift-setup.md` -- Only if source file needs discovery - `../../shared/includes/migration-fix-registry.md` -- Only with `--fix` - `../../shared/includes/verification-protocol.md` -- Only with `--fix` - `../../shared/includes/run-logger.md` -- At report phase - `../../shared/includes/retrospective.md` -- At report phase --- ## Safety Gates ### GATE 1 — Consent Per `live-probe-protocol.md` for BOTH `--old` and `--new` URLs. ### GATE 2 — Read-Only Default Without `--fix`: compare and report only. Writes only to `zuvo/reports/`. ### GATE 3 — Conservative Fixes With `--fix`: - **Never** delete content from the new site - **Never** reorder existing content - **Never** modify files not explicitly resolved as the source - Dirty file check: `git status --porcelain -- <file>`. Dirty → STOP. - If insertion point is ambiguous →...