Legacy Editorial Control Sync

To align legacy editorial fields during a repository migration, apply patches that map legacy inputs like depth_level and content_profile to their preset-era equivalents. This process keeps derived fields in sync across forms and routes.

Migrating legacy editorial controls causes drift in derived columns because patches modifying legacy data can bypass preset-era synchronization rules. Without explicit alignment, canonical fields fail to recompute properly when legacy inputs change.

Yes, you can preserve advanced overrides like panel_shape and panel_constraints_json when migrating legacy editorial fields. The sync process ensures these explicit configurations are retained without unintended resets during the transition.

Derived defaults recompute only when explicit legacy inputs change during the editorial control sync. This targeted patch-resolution approach prevents unintended resets of canonical fields if no actual legacy data modifications occurred.

The best way to resolve legacy inputs to updated editorial controls is running a dedicated sync process during repository migration. This safely patches legacy fields across forms and routes while preserving advanced overrides.

If you patch legacy data without an editorial control sync, preset-era fields face compatibility issues and derived column drift. Canonical fields remain out of sync because the system cannot automatically align the legacy modifications.