Colspan tables shredded my HTML-to-Markdown output — Markdown can't express merged cells

A user fed a cloud vendor's pricing page through my HTML-to-Markdown endpoint and got back a table where every plan's price sat in the wrong column. The page's comparison table used colspan for a tier header spanning three cells and rowspan for a plan name covering two rows. My converter processed each row independently — row count became pipe count. Rows under a colspan came out shorter, and whichever Markdown parser consumed the file aligned what came next with whatever column was open. A RAG pipeline downstream then quoted the wrong plan for a feature, which is how I found out: the answer l