/* Integration safety gate — merge-level repair, NOT an agent file.
   Problem: design-system.css (agent 01) defines an UNGATED
   `.reveal { opacity: 0 }` hidden state, on the assumption (stated in its
   own comment) that "pages must not carry .reveal in static HTML".
   In fact 19 merged pages DO carry .reveal in static markup (agents 06,
   08, 09, 10, 11, 13, 14, 15, 16, 17), each relying on its own JS-added
   gate class. With JavaScript disabled, design-system.css alone would
   leave that content invisible, breaking the contract rule "never
   require JS for content to be readable" (acceptance B5).
   Fix (no agent file touched, no copy changed): this rule forces
   .reveal fully visible whenever NO reveal script has run — i.e. none
   of the gate classes (html.js, html.js-motion, html.js-reveal,
   html.demo-motion) is present. Once any reveal script runs and adds
   its gate class, this rule stops applying and the normal reveal
   systems take over. It never hides anything. Loaded LAST on every
   page so it wins the cascade; !important so it beats every
   hidden-state rule regardless of specificity. */
html:not(.js):not(.js-motion):not(.js-reveal):not(.demo-motion) .reveal {
  opacity: 1 !important;
  transform: none !important;
}