The marketing copy is bound to the capability flags now
Two sentences on countbean.com denied a feature customers could already use; the gate meant to prevent exactly that was never weak, it was just never pointed at the marketing tree.
The capability test ties each flag to a predicate over the live route table, and the caveats those flags gate render inside the app. The marketing site is a different tree with no import path to the flags and no test that read them.
The assertion is bidirectional, and that is the part that matters. When a flag is false the caveat must be present, so rewording or deleting it goes red — which is what stops a registry of phrases decaying into a check that cannot fail. When a flag is true the caveat must be absent, which is the repair-time defect: a denial that outlived the feature. Flipping any flag flips which branch bites.
Both directions have a live control in the same run today, and a test asserts that stays true rather than leaving half the file as untested machinery after some future flag flip. The corpus read refuses to return nothing, and refuses a corpus with no “Countbean” in it, for the same reason the route-table read does: an empty read grades every true flag green.