/* ==========================================================================
   COMPATIBILITY LAYER - TEMPORARY, REDUCED IN BUILD 3
   ==========================================================================

   WHY THIS FILE EXISTS.

   Build 1 replaced the application shell before any page had been
   redesigned, and a handful of page-level rules written for a white page on
   a grey canvas collided with the new white card on a pale blue one. This
   file loads AFTER main.css and fixes exactly those collisions.

   BUILD 3 REMOVED SIX OF THE ORIGINAL EIGHT BLOCKS. Each was checked
   against the templates rather than assumed:

     1. Page backgrounds (`.page-surface`, `.page-background`)
        REMOVED - no template emits either class.

     2. Full-bleed wrappers (`.content > .wide`, `.content > .full-bleed`)
        REMOVED - the only `.wide` usages are `.chart-card wide`,
        `.modal-wide` and `.form-field-wide`, none of which is a direct
        child of `.content`. The selector matched nothing.

     3. Legacy sidebar selectors (`.sidebar-brand`, `.mobile-topbar`)
        REMOVED - no template emits either, and its stated removal trigger
        was "Build 3, once a test asserts no template emits either". That
        test now exists: tests/test_visual_rollout.py.

     4. Report masthead top margin
        REMOVED - Build 2 rebuilt `.report-masthead` and it no longer
        declares a top margin, so the override was a no-op.

     5. Nested table-card chrome
        REMOVED - no template nests one `.table-card` inside another.

     8. Report and dashboard section surfaces
        PROMOTED, not deleted. `.summary-section` is used by 26 templates
        and is now a first-class shared component in components.css, with
        the Executive HR Summary archetype's surface and heading. It stopped
        being a collision fix and became the platform's section.

   THE RULES THIS FILE IS STILL HELD TO

     1. Every rule here is a COLLISION FIX, never a design decision.
     2. No !important.
     3. Every block says what removes it.
     4. The file only shrinks.

   Like every other shared sheet it carries no literal colour and no
   !important - both enforced by tests/test_design_tokens.py.
   ========================================================================== */


/* --------------------------------------------------------------------------
   6. Filter bars nested inside a section
   --------------------------------------------------------------------------
   STILL REQUIRED.

   `.filters-bar` is a frosted container, and `.summary-section` became an
   opaque white card in Build 3. A frosted band on white reads as a grey
   box rather than as a filter band.

   One template nests them today: `hr_reporting_builder.html`, where the
   field picker, the filter rows and the results all belong to one bounded
   report-builder surface. That nesting is deliberate there - the filters
   describe the report being built, not the page - so the fix is to make
   the inner bar a plain row rather than to move it.

   REMOVED BY: a future build that either flattens the Report Builder's
   surfaces or gives `.filters-bar` a variant for use inside a card. Not
   urgent: one template, one rule.
   -------------------------------------------------------------------------- */

.surface-card .filters-bar,
.table-card .filters-bar,
.card .filters-bar,
.summary-section .filters-bar {
  padding: 0;
  background: none;
  border: 0;
  box-shadow: none;
  backdrop-filter: none;
}


/* --------------------------------------------------------------------------
   7. Dialogs are never frosted
   --------------------------------------------------------------------------
   STILL REQUIRED, and arguably permanent.

   The translucency split puts modals firmly on the opaque side: a dialog
   over a table over a photograph is exactly where frosted glass stops
   being readable. This is defensive - no dialog sets a translucent
   background today - but the cost is two lines and the failure it prevents
   is one somebody would ship without noticing.

   REMOVED BY: nothing planned. If a later build adds a test asserting no
   dialog declares a backdrop-filter, this can go and the test can carry
   the guarantee instead.
   -------------------------------------------------------------------------- */

.modal,
.modal-body {
  backdrop-filter: none;
}
