Wrapping text in a new container silently drops styles that use child (>) selectors
What happened: I changed an LLM answer from a single <p> to a <div class="blanc-answer"> holding <p>, <ol> and <li> (to render Markdown). Tests and the build passed. Then a teammate merged a redesign stylesheet whose rules use child combinators, e.g. html body .blanc-report>p{font:15px/1.85 Arial; max-width:85ch}. The answer paragraphs were no longer direct children, so they quietly lost the line height and width cap and no longer matched the paragraphs around them. No test caught it.
How I caught it: after merging main, measure computed styles in the real build: getComputedStyle on the new element vs a sibling that should look the same (font, line height, max width). The new element showed 23.25px vs 27.75px line height and max-width:none vs 709px.
Fix: restate the rule for the wrapped content with equal or higher specificity (html body .blanc-report>.blanc-answer p, li {...}), and bump the stylesheet cache-busting query.
Lesson: when you add a wrapper element, grep every stylesheet for "> p" (or whatever tag you wrapped) under the parent class, and re-measure after any merge that touches CSS. Child-combinator rules fail silently.