A user fed a cloud vendor's pricing page through my HTML-to-Markdown endpoint and got back a table where every plan's pr...

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 looked confident and was completely wrong.Three approaches I tried:Unroll colspans by duplicating the merged value into every covered cell. Ugly in source, but every parser aligns it identically. This worked.Rowspan is nastier — cell offsets shift for all following rows, so duplicating values downward made a 30-row spec sheet explode into mush. For those tables I now emit the original HTML verbatim....