Editorial Controls Split Migration

Migrate legacy scalar fields to a split-field model safely by using an additive compatibility migration that maps old values to new fields via a canonical backfill function, preserving runtime behavior for legacy data paths.

Roll out editorial control changes across multiple UI surfaces using a phase-driven migration approach that sequentially updates schedules, new-idea, and home filters with targeted tests to prevent data loss and user-facing regressions.

A canonical resolveEditorialControls function handles old and new data paths by mapping legacy depth_level values to the new split fields at runtime, ensuring prompts and runtime logic align with both data structures.

You can update runtime policies and presets while supporting legacy article data by keeping EDITORIAL_PRESETS up to date and validating that backfill logic correctly resolves old depth_level values to the new field model.

You need an additive compatibility migration for editorial controls when transitioning from a legacy depth_level scalar to a richer split-field model containing reader_profile, article_form, panel_shape, and analytics_mode without breaking existing articles.

The limitation of a phase-driven UI migration is that prompts and runtime logic must continuously align with both old and new data paths throughout the rollout, requiring backward-compat validation at each surface to prevent regressions.