style-migrate-enhance

To migrate CSL 1.0 styles without losing rendering fidelity, run batch conversion waves that generate before/after/rerun metrics and enforce hard fidelity gates using oracle verification. This ensures only changes that do not reduce fidelity are accepted.

Oracle verification for citation rendering style migration is an apples-to-apples comparison mechanism that measures before/after rendering fidelity. It runs node scripts to ensure CSL 1.0 to Citum YAML conversions do not introduce rendering differences.

Automate batch conversion of legacy CSL 1.0 parent styles by executing migration waves with provided legacy and target style path inputs. The workflow tracks evidence consistently and generates wave-level summaries across multiple styles.

When style migration introduces rendering differences in Citum, the workflow generates an engine-gap recommendations table. This structured code opportunities output provides targeted follow-ups for converter and preset improvements to resolve the gaps.

Yes, you need to provide legacy and target style path inputs to execute batch style migration waves. These paths are required to run the shared workflow decision and evidence order docs and verify results via oracle.js node scripts.

CSL 1.0 style migration breaks downstream citation workflows because legacy styles often migrate imperfectly into Citum. These rendering differences erode trust in style results and disrupt dependent processes without repeatable evidence and metrics.