wow-migratelisted

# Migrate Wow Across Breaking Boundaries ## Scope gate Use only for a downstream application; the Wow framework repository and its modules never qualify. Require scoped source/target to use or introduce Wow plus a cross-major upgrade, known source/configuration/generated/runtime break, or Wow-managed storage/data change. Routine same-major non-breaking upgrades and first adoption stay with `wow-develop` unless adoption requires Wow-managed history/compatibility conversion, data reconciliation/cutover, or rollback after incompatible target writes. Checkout-wide markers and unrelated application contracts do not qualify. Otherwise state that this Skill does not apply and stop using it. Own the complete migration task. Treat breaking release upgrades—including cross-major and same-major source/config contract changes—and storage/data cutovers as platform, source, generated-contract, data, runtime, and release migrations rather than dependency bumps. ## Contract - Pin the exact source and target versions before implementation. “v8” alone is not an executable target. - Use the target tag's source, tests, BOM, release notes, and generated contracts as authority. - Distinguish audit, planning, code implementation, data rehearsal, production cutover, and review modes. - Treat code-write authorization, data-write authorization, and production-release authorization as separate scopes. - Mark missing production, data, or deployment evidence as `MISSING EVIDENCE`. - Never claim migr