/* ============================================================
   SECTION 03 — "ONE DASHBOARD, BUILT ROUND YOUR BUSINESS", on the light ground.

   It was a black slab (`.sec--ink` + `data-theme="dark"`). Founder-directed
   back to light: the same warm off-white the rest of the page uses.

   Both came off TOGETHER — leaving `data-theme="dark"` behind is how a section
   ends up carrying the dark token layer on a light ground with no visible
   cause, and leaving `.sec--ink` behind would have kept painting it black.

   Everything the dark version needed then falls away with it, and that is the
   point of having done it with a theme attribute rather than by hand: the
   scoped neutral greys, the re-solved --accent-ink, the light-surface paper
   scope. On paper the root tokens are already correct.

   WHAT STILL NEEDS SAYING. `.plat__p` is `--white` from home.css, and this
   section's ground is `--paper-warm` — three units apart. The panels therefore
   read as panels on their border and their shadow, not on their fill, which is
   exactly how they read before the black experiment. The AI panel is white with
   them rather than reverting to home.css's `background: var(--ink)`, because
   founder-directed it stopped being the one black object in the set.
   ============================================================ */
.sec--dash { background: var(--paper-warm); }

/* The AI panel does NOT revert to home.css's black fill. Its text colours stay
   as they are: #0F0F0F, #3F3F3F and #4E4E4E were solved against the MOCHA,
   which is darker than white, so they clear by a wider margin here than where
   they were chosen. */
/* ⚠️ AND THE PADDING AND THE BORDER BACK WITH THEM. Below 1040 home.css turns
   this panel INTO the container's own content — `background: none; border: 0;
   padding: 0` — because at that width the black stack IS the card and a card
   inside a card is two cards. This rule then put the white fill back and left
   the other two behind, so on every phone the AI panel was a white box with
   its text flush to all four edges and no border: the heading touched the left
   edge and the sentence ran into the right one. It looked like an overflow and
   it was a padding.
   A partial restore of a state that was removed as a SET is the failure here —
   the fill, the border and the padding were taken off together and only one
   came back. */
.sec--dash .plat__p--ask { background: var(--white); border-color: var(--line); }
@media (max-width: 1040px) {
  .sec--dash .plat__p--ask { border: 1px solid var(--line); padding: var(--s3); }
}
.sec--dash .plat__p--ask .plat__k { color: #6E6E6E; }
.sec--dash .plat__p--ask .plat__q { color: var(--ink); }
.sec--dash .plat__p--ask .plat__a { color: var(--ink-2); border-top-color: var(--line); }
.sec--dash .plat__p--ask .plat__a b { color: var(--ink); }

/* the four number tiles: white with the hairline, which is the only thing
   separating them from a white panel */
.sec--dash .dash__tile { background: var(--white); border-color: var(--line); }


/* ---- MORE AIR ABOVE IT ON A PHONE ---------------------------
   Founder-directed, "add padding top to the dashboard section" — and the same
   96/64 split section 01 took, so the two sections above and below the
   automations rail open on the same rhythm rather than each having its own.
   The bottom stays at --s6: the section under this one needs no help. */
@media (max-width: 760px) {
  .sec--dash { padding-block: var(--s7) var(--s6); }
}