New — the module audit catches background images that vanish on send
If a Stripo module paints a panel or gradient using a background image on a <table>, it looks perfect in the Stripo editor and then disappears once the email is exported and sent. Gmail, Outlook, and Braze's render all strip background images off <table> elements — but the identical image on a <td> survives. orbit_audit_stripo_modules now flags this directly, so you catch the silent fill-loss before it ships instead of after a test send, and the finding tells you exactly how to fix it.
What shipped
•New finding — table_background_image (warning). The audit scans every synced module and flags any <table> carrying a background image (a background="…" attribute or background-image:url(…) in its style), because that fill renders in the Stripo editor but collapses to nothing in Gmail, Outlook, and Braze once exported.
•It tells you the fix — move the background onto a wrapping <td> that holds the module's content, and keep a solid bgcolor on that same <td> as a fallback. That is how Stripo's own hero and structure modules apply gradients, which is why theirs survive the Stripo-to-Braze handshake and a table-based one does not.
•Why it matters — background-image-on-a-table is the classic reason a chat bubble, gradient panel, or coloured section looks right while you are building and then sends with a blank background. Surfacing it at audit time turns a confusing test-send mystery into a one-line structural fix.