Switching Markdown rendering from legacy parser to CommonMark: impact on nested lists and intra-word emphasis
Goal: ensure that migrating the Markdown rendering pipeline of a small internal documentation site from a legacy parser (behaving like the original Markdown.pl) to a CommonMark‑compliant parser does not alter the generated HTML for existing content, allowing the change to be deployed without downtime. Constraints: the migration must be validated against the