/**
 * MCMC — the CHROME's page layer, layer 5 of 5.
 *
 * SEAT REFACTOR-R6, 10 September 2026. Unit R6 of `docs/refactor/04-build-order.md`.
 *
 * ⛔⛔ THIS FILE IS A PAGE LAYER AND `docs/refactor/05-page-layers.md` IS ITS LAW.
 *    A page layer is MEASURED, not authored: for every element, at every one of the
 *    three gate widths, it carries exactly the properties the four system files do not
 *    already produce on that element in that position — and nothing else. Its SIZE is
 *    the report card, because **a page layer that may carry anything makes the system
 *    unfalsifiable**: pixel zero would then follow from the layer alone and say nothing
 *    whatever about `03-layout.css`.
 *
 * ⛔ THE CHROME IS NOT A PAGE, AND THAT IS WHY IT HAS ITS OWN FILE RATHER THAN A ROW IN
 *    FIVE OTHERS. The header and the footer are on 79 of 79 captures, byte-identical;
 *    SEAT REFACTOR-R0 measured the footer alone at 309,228 of the ~309,500 pixels its
 *    `--mc-black` perturbation moved on five pages of wildly different length, *"at row
 *    320 on the story page and row 6,475 on home"*. A residue that is the same on every
 *    page is a SITE rule wearing a page layer's clothes. Everything in this file is
 *    therefore a candidate for `04-components.css`, and the pixel gate is what says
 *    whether the move is correct.
 *
 * ⛔ EVERY SELECTOR IS WRITTEN THREE TIMES — `.mcp-chrome.mcp-chrome.mcp-chrome` — FOR
 *    (0,3,0). REFACTOR-R0's FINDINGS 5: `.mc-header__logo img` is (0,1,1) and beats a
 *    single page class at (0,1,0), so a measured width was emitted, ignored, and
 *    re-measured as still wrong every round, at two widths of three. (0,3,0) beats every
 *    selector in the four files, the highest of which is (0,2,1).
 *    ⚠ It still does not beat an `!important` in a component, and two exist.
 *
 * ⚠ AT STEP 1 OF THIS UNIT THIS FILE CARRIES NO RULES, AND THE EMPTINESS IS THE POINT.
 *    The enqueue set is made final BEFORE the templates change, so the step that switches
 *    the templates changes markup and this file's CONTENT and moves no `<link>`. A step
 *    that changed both the served link set and the markup at once would have two
 *    explanations for every pixel.
 *
 * ══════════════════════════════════════════════════════════════════════════════════════
 * ⛔⛔ FILLED BY SEAT REFACTOR-R6B, 10 SEPTEMBER 2026 — AND **NOT** BY TRANSCRIBING THE
 *    478 MEASURED DECLARATIONS, WHICH IS WHAT THE BRIEF ASKED FOR AND WHAT MEASUREMENT
 *    REFUSED. The 478 are a page layer in REFACTOR-R0's sense: computed values read back
 *    at 1440, 1024 and 390. Read them and they are pixel PINS —
 *      `width: 1006px` at base · `width: 883.59375px` at ≤1024 · `width: 472px` ·
 *      `width: 80.390625px` · `height: 233.84375px` — 
 *    and a chrome stylesheet carrying those is correct at exactly three viewport widths
 *    and wrong at every other one. The header and footer are on 79 of 79 pages and the
 *    site is browsed at whatever width a window happens to be. A three-width gate CANNOT
 *    SEE that defect: both arms are pinned to the same three numbers.
 *    ⭐ So this file is AUTHORED FROM THE CENSUS, exactly as `01`–`04` were: every rule
 *    below is a rule the site actually declares — `css/post-214.css` for the header and
 *    `css/post-915.css` for the footer, the two per-document stylesheets Elementor
 *    generated for templates 214 and 915 — with Elementor's `--display`/`--width`
 *    indirection resolved to the property it feeds. The 478 are then the CROSS-CHECK and
 *    not the source, and the gate is run at eight widths offline rather than three, so
 *    the claim "fluid, not pinned" is a measurement and not a preference.
 *    ⚠ The pins are not thrown away: `reports/REFACTOR-R6B/<ts>-evidence/` carries the
 *    transcribed variant AND its measurement, which is how the paragraph above stops
 *    being an argument.
 *
 * ⚠ SELECTORS ARE **NOT** TRIPLED HERE, AND THE PARAGRAPH ABOVE ABOUT (0,3,0) IS LEFT
 *    STANDING BECAUSE IT IS RIGHT ABOUT A PAGE LAYER. It is not right about this file:
 *    R0's FINDINGS 5 is about a `.mcp-N` page class LOSING to a component's own
 *    `.mc-header__logo img` at (0,1,1). Every rule below is written at the same
 *    specificity as the component rule it refines and sits in the handle that loads
 *    AFTER it (`mc-chrome` is fifth of five in `Styles\McSystem::FILES`), so later-wins
 *    decides — deterministically, and without a selector nobody can read. The one
 *    element-qualified pair below (`.mc-header__logo img`) is (0,1,1) in both files.
 */

/* ══ THE TWO RULES THAT WERE HERE ARE GONE, AND THAT IS SEAT REFACTOR-R1's FIX ════════
   SEAT REFACTOR-R6B stated two rules here because both were questions about
   `03-layout.css` rather than about the chrome, and fixing that file was outside its
   authorisation. **Both are now fixed in the primitives, by SEAT REFACTOR-R1 on
   11 September 2026, and the restatements are deleted rather than left to agree.**

     1 · `.mc-header__inner, .mc-footer__grid { max-width: min(100%, var(--mc-shell-max)) }`
          — `03-layout.css` now places the `.mc-shell__inner` block AFTER the widget
          wrapper reset that was beating it by source order. The measurement that found it
          stands: the header's inner rendered **1420 px wide at x=10 where the served one
          is 1140 at x=150**.
     2 · `padding: 10px; gap: var(--mc-gap)` on the chrome's six column classes —
          `03-layout.css` now carries it on the three flow primitives, which is what every
          `.e-con` child container has. The measurement stands: without the padding the
          header logo renders **112 px wide instead of 75.19**, and without the gap the
          footer is **213.844 px tall where the served one is 233.844**.

   ⛔ THE DELETION IS NOT A TIDY-UP AND IT IS GATED LIKE A CHANGE. Two rules moving from the
      file that loads LAST into the file that loads THIRD can only be equivalent if nothing
      between them says anything about the same properties on the same elements, and the
      thing that says so is the gate: the sixteen chrome slots at 1440, 1024 and 390 on
      staging, and the five offline pages at TWELVE widths, re-run after the move.
   ⚠ AND IF EITHER RULE IS EVER RESTORED HERE, IT IS A SIGN THE PRIMITIVE IS WRONG for some
      element — which is a question about `03-layout.css`, not about the chrome. */

/* ══ HEADER — css/post-214.css, template 214 ══════════════════════════════════════════
   `.elementor-214 .elementor-element-0fc1d52 { --width: 10% }` inside `@media(min-width:768px)`
   `.elementor-214 .elementor-element-3d3bd09 { --width: 90% }` inside the same query
   ⚠ NEITHER HAS A BASE VALUE. Elementor writes the two ends and nothing between, so below
     768 the ≤767 pair below is the whole story and the two queries are written the way the
     source writes them rather than folded into one. */
/* `.elementor-214 .elementor-element-f6635a3 { --gap: 0px 0px; --row-gap: 0px;
   --column-gap: 0px }` — the header band's row has NO gap, where `.mc-shell__inner`
   (03-layout.css:66) gives every inner `gap: var(--mc-gap)` = 20 px. MEASURED: with the
   20 px the two columns come out 112.297 + 1007.703 (1,140 − 20) instead of 114 + 1,026,
   and the logo is 73.83 px wide instead of 75.19. The footer keeps the 20 px, which is
   what post-915 leaves it at, and its two grid columns are 560 + 20 + 560. */
.mc-header__inner { gap: 0; }

@media (min-width: 768px) {
  .mc-header__brand { width: 10%; }
  .mc-header__menu  { width: 90%; }
}
@media (max-width: 767px) {
  .mc-header__brand { width: 25%; }   /* post-214 `-0fc1d52 --width` @≤767 */
  .mc-header__menu  { width: 75%; }   /* post-214 `-3d3bd09 --width` @≤767 */
}

/* `.elementor-214 .elementor-element-c220e67 img { width: 80% }` is in `04-components.css`
   as `.mc-header__logo img`, because the header is on 79 of 79 pages and a per-document
   rule about it is per-SITE in substance. The two responsive overrides are the same rule
   at the other two widths and belong beside it. */
@media (max-width: 1024px) { .mc-header__logo img { width: 100%; } }
@media (max-width: 767px) {
  /* `.elementor-214 .elementor-element-c220e67` @≤767 — the widget box, not the image */
  .mc-header__logo { width: 100%; max-width: 100%; padding: 0; text-align: start; }
  .mc-header__logo img { width: 100%; }
}

/* ══ FOOTER — css/post-915.css, template 915 ══════════════════════════════════════════
   `.elementor-915 .elementor-element-0d5db8b { --width: 15% }` inside `@media(min-width:768px)`
   — the logo column, and again with no value below 768. */
@media (min-width: 768px) { .mc-footer__logo-col { width: 15%; } }

/* `.elementor-915 .elementor-element-135f59b { --align-items: flex-start }` */
.mc-footer__social-col { align-items: flex-start; }

/* `.elementor-915 .elementor-element-89d4651 { text-align: start }` — the site-logo widget
   overrides `.mc-media`'s centred text (03-layout.css:138). */
.mc-footer__logo { text-align: start; }

/* `.elementor-915 .elementor-element-89d4651 img { width: 18% }` @≤767 */
@media (max-width: 767px) { .mc-footer__logo img { width: 18%; } }

/* `.elementor-915 .elementor-element-3a5240c { --e-con-grid-template-columns: repeat(1, 1fr) }`
   @≤767 — the two-column band becomes one column. `--mc-cols` is the token
   `03-layout.css`'s `.mc-grid` reads; `04-components.css` sets it to 2 for this grid. */
@media (max-width: 767px) { .mc-footer__grid { --mc-cols: 1; } }

/* `.elementor-915 .elementor-element-40c0ceb { --icon-size: 20px }` @≤767. The social
   link's box is `calc(icon + 2 * padding)` in `04-components.css`, so ONE token moves the
   seven icons from 50 px to 40 px exactly as the served rule does. */
@media (max-width: 767px) { .mc-footer .mc-social { --mc-icon-size: 20px; } }

/* `.elementor-915 .elementor-element-cb06f87 { --justify-content: center }` and the same
   on `-3e97540` — the two legal columns, which are flex COLUMNS, so this centres them
   vertically inside the grid row. */
.mc-footer__legal-col { justify-content: center; }

/* ⛔ THE TWO LEGAL BLOCKS ARE NOT SET IN THE SAME TYPE, AND `04-components.css` CARRIES
   ONLY ONE OF THEM. `.mc-footer__legal` there is `-ec755dd`'s rule — AllProDisplay 18/500,
   line-height 24, letter-spacing 0.5px — and that element is the NARROW copy. The WIDE
   copy (`-ed8577f`) has no per-element rule at all and takes the kit's `text` typography,
   whose letter-spacing is 2px (`--mc-t-body-ls`, kit `--e-global-typography-text`). Two
   paragraphs of the same words at two letter-spacings; the measured residue names it as a
   `letter-spacing` difference on that one element on all five pages. */
.mc-footer__legal--wide { letter-spacing: var(--mc-t-body-ls); }

/* `.elementor-915 .elementor-element-ec755dd { font-size: 14px }` @≤767 — the narrow copy
   only, which is the only one visible there. */
@media (max-width: 767px) { .mc-footer__legal--narrow { font-size: 14px; } }
