🧒 Kid Mode — Health & Fix

A handful of recently-generated pages shipped a Kid mode button wired to onclick="toggleKid()" — but the toggleKid function itself was never put on the page. So clicking the button threw toggleKid is not defined and nothing happened.

The button looked perfect in the HTML. It just had nothing behind it.

The page generators emit the button + its CSS, and relied on a separate injector to add the script. But the idempotency check — has_button() in kid_mode_inject.py and ensure_button() in ship.py — treated "a button tag is present" as "kid mode is satisfied." It never checked that the toggleKid function existed. A button with no function sailed through every gate, including the closeout that is supposed to prove it works.

Both gates now require the function, not just the button. A page is "working" only when it has a button and a real toggleKid (or a bespoke kid-class toggle). The precise rule: a page is DEAD only if it references toggleKid() but never defines it.

• kid_mode_inject.py — repairs a dead button by injecting only the script (no duplicate button), leaves bespoke pages untouched.
• ship.py — ensure_button() repairs before deploy; the live check now confirms kid_works=true, not just a button tag.

Result: 0 dead buttons remain, and the closeout gate can no longer ship one.

Measured live at build time. OK = real toggleKid present · OK·bespoke = page has its own working kid toggle (e.g. straykids) · DEAD = button with no function.

Vercel serves with stale-while-revalidate=86400, so the CDN can hand you a cached copy from up to a day ago while it refreshes in the background. If you saw a dead button before the fix deployed, your browser/edge may still be holding that old copy. This deploy purges the edge; a hard refresh (Cmd + Shift + R) clears the rest.