/* The app shell: everything behind sign-in, under /app.

   Loaded on top of platform.css and only on `/app` pages, the same way
   builder.css sits on top of it for the builder. The card at `/@slug` never
   loads this file, and neither does the funnel.

   **Amendment 2 is why this file has its own scale.** Ramon opened the
   density pass and said: *"so far, what has been built is not my favorite. it
   looks very cluttered, a ton of fluff. The UI is terrible."* The first two
   passes had moved boxes around while keeping the landing page's tokens, and
   the landing page's tokens are a 17px paragraph, a 44px capsule, a 19px
   sub-heading and a blue text link. That is a scale for a page somebody reads
   once. An app is read hundreds of times by somebody who is not reading it at
   all, and it runs at 13 and 14px with 32px controls. DESIGN.md 1's "The app
   scale" is the table; every number in here is one of its rows.

   The five defects it closes, named off the 1280 shots:

   1. **Two chromes.** The marketing bar sat above the rail on every screen,
      carrying a wordmark and a support link the rail can carry. Two
      navigations on one screen is the defect the shell was built to fix. The
      bar is off inside `/app` now (base.html), and the rail is the only
      chrome. That is why the rail starts at `top: 0` and is a full `100dvh`.
   2. **Narration.** A sentence under every title, a paragraph in every panel,
      a hint under every control, and buttons that said "Publish it" and "Fill
      in the rest". A customer reads none of it and sees all of it. What is
      left is labels and verbs, and the three sentences that state a RULE
      somebody needs in order to act.
   3. **Marketing tokens on a working screen.** 17px body, 980px-radius
      capsules, 19px blue text links inside panels, "Not published" in alert
      red. All four are gone: 13/14px, `.btn` at 32px and 6px, and status as a
      dot plus a word where grey means off and red means a payment failed.
   4. **Boxes inside boxes.** A bordered preview inside a bordered panel
      inside a bordered column. Nothing inside a panel has a border of its own
      now except inputs, table rules and the phone frame; a preview sits on a
      `--light` inset instead.
   5. **The system font.** The quiet reason a screen reads generic however the
      boxes are arranged. Inter Variable is self-hosted below, with `cv01` and
      `ss03` on, which is what separates Linear's Inter from everybody's.

   Where the grammar comes from, since it is not invented here:

   - **Linear** supplies the anatomy: a rail that is a luminance step off the
     canvas rather than a boxed card, 13px/500 labels in 30px rows, depth as a
     step in ground rather than a shadow, and `"cv01", "ss03"` on all of it.
     In light mode that inverts cleanly, so the rail takes `--light` and the
     canvas takes `--white`.
   - **Vercel** supplies the pacing and the panel: a white canvas, one
     hairline in a grey a shade lighter than the page's borders, 6px on
     anything you press, and no section that announces itself with a colour.
   - **beui.dev `button` / `switch`** supply the press: every interactive
     element scales a touch under a finger, because a control that does not
     answer a press is a control somebody presses twice.

   What is refused from both, on purpose: Vercel's shadow-as-border, which
   would be a second border grammar beside `--panel-edge`, and Linear's
   translucent surfaces and indigo, which are a dark-mode system. Nothing of
   either palette is imported. */

/* ------------------------------------------------------------- the face */
/* Self-hosted, `swap`, and the two upright faces preloaded from
   `app_base.html` on app screens and from `sign_in.html` (DESIGN.md 2.2b).
   `tools/fonts.py` cuts all three from the google/fonts sources (OFL, licences
   in `platform/fonts/`): Latin-1 plus the dashes, the quotes and the ellipsis.
   Instrument Sans is the UI, `wdth` pinned at 100 and `wght` 400 to 700;
   Newsreader is the titles, `opsz` pinned at 36, upright 300 to 600 and italic
   300 to 500. The three `@font-face` rules live in platform.css, right after
   its `:root`, because the sign-in page draws these faces without app.css;
   every app screen loads platform.css first, so nothing here changed. */

/* --------------------------------------------------------- the app scale */
/* Scoped to `body.app`, so the landing page, the builder, checkout, the
   install page and the card are all untouched by every line of it. */
body.app {
  /* The Daybook UI face, with the system stack under it for the moment
     before it lands and for a glyph outside the subset. */
  font-family: var(--sans-ui);
  /* Every figure in the app is in a column with other figures: a plan, a
     date, an opened count, an order id. Proportional figures make a ragged
     column of all of them. */
  font-variant-numeric: tabular-nums;
  font-size: 14px;
  line-height: 1.45;
  letter-spacing: normal;
  /* The linen ground; the screen itself is the ivory window `.app-main`
     draws on top of it (DESIGN.md 2.2b). */
  background: var(--ground);
  color: var(--ink-warm);
}

/* The one exception, and it is the customer's own artwork. A signature is a
   table of inline-styled pixel boxes drawn for a mail client; the app's face
   and the app's figures have no business inside it, and `--font` is exactly
   what it was rendered against before this file existed. */
.cardhost, .row-shot {
  font-family: var(--font);
  font-feature-settings: normal;
  font-variant-numeric: normal;
}

/* The way past the chrome, and it is the first thing in the document because
   that is the only position that makes it work. It lands on the page's own
   heading rather than on the shell, because the shell is what somebody is
   trying to skip. */
.skip {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 40;
  padding: 8px 14px;
  background: var(--white);
  border: 1px solid var(--hair);
  border-radius: 0 0 8px 0;
  font-size: 13px;
  font-weight: 600;
  color: var(--ink);
  text-decoration: none;
}
.skip:focus { left: 0; }

/* A name a screen reader needs and a sighted reader already has from the
   layout: the picture column of a table, the chevron at the end of a row. */
.vis {
  position: absolute;
  width: 1px;
  height: 1px;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
}

/* ------------------------------------------------------------ the shell */
/* Two columns at 1024 and up, one below it, and NOTHING above either. There
   was a 52px marketing bar here until amendment 2; what it carried was a
   wordmark and a support address, and the rail carries both now.

   `minmax(0, 1fr)` and not `1fr`, and this one fails silently. A bare `1fr`
   is `minmax(auto, 1fr)`, whose MINIMUM is the column's min-content width, so
   one wide child - the install build at 508px, the live card at 380 - pushes
   the whole column past the viewport and the document scrolls sideways.
   Measured at 375 before the fix: the main column went to 415px on Home and
   430 on Card with every visible box apparently inside it. */
.app-grid {
  flex: 1 0 auto;
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  align-items: start;
}

/* ---------------------------------------------------------- the rail */
/* 220px at 1024 and 248 from 1280, sticky against the top of the window
   rather than under a bar, and as tall as the window. `align-self: start` is
   what lets a sticky grid item stick at all: a grid child stretches to its
   row's height by default, which makes the rail exactly as tall as the screen
   beside it and gives `sticky` nothing to move inside. */
.side {
  display: none;
  position: sticky;
  top: 0;
  align-self: start;
  height: 100dvh;
  background: var(--ground);
  border-right: 0;
  padding: 20px 14px 14px 16px;
  overflow-y: auto;
  overscroll-behavior: contain;
}
.side-inner { display: flex; flex-direction: column; gap: 20px; min-height: 100%; }

/* The wordmark row, which is the whole of what the bar used to be for. Still
   48px, because that is the height the rest of the rail is measured against,
   but what stands in it is the drawn lockup now instead of the brand set in
   Inter beside a 9px square. The square was a placeholder for a mark the
   product did not have yet; it has one, so the placeholder goes and the row
   carries the real thing. The lockup is two stacked lines, so 30px of height
   is 61px of width — small enough to leave the 48px row its air, large enough
   that SELF and MARK read as letters rather than as a grey smudge. The
   on-light file, because the rail's ground is `--light` and the letters in
   that one are the ink. It is a link to the marketing site, as it was in the
   bar. */
.side-mark {
  display: flex;
  align-items: center;
  justify-content: flex-start;
  height: 30px;
  padding: 0 6px;
  text-decoration: none;
}
/* Centred across the rail rather than flush with the rows under it: a lockup
   is a badge, and a badge sits in the middle of the band it is on, where a
   word of text would have hung off the left edge with the rows. The owner
   asked for exactly this on seeing it drawn flush. */
.side-mark img { display: block; height: 30px; width: auto; }

/* The workspace chip (DESIGN.md 2.2b): whose account this is, as a name and
   a plan, in the window's ivory between the wordmark and the nav. */
.side-space {
  display: flex;
  align-items: center;
  gap: 10px;
  padding: 8px 10px;
  border-radius: 12px;
  background: var(--window);
  box-shadow: var(--sh-1);
  color: var(--ink-warm);
  text-decoration: none;
  transition: box-shadow 150ms var(--ease-expo);
}
.side-space:hover { box-shadow: var(--sh-2); }
.side-space > span:last-child { min-width: 0; }
.side-space-face {
  flex: none;
  width: 24px;
  height: 24px;
  border-radius: 50%;
  object-fit: cover;
}
.side-space-name, .side-space-sub {
  display: block;
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
.side-space-name { font-size: 13.5px; font-weight: 600; line-height: 1.2; }
.side-space-sub { font-size: 12px; line-height: 1.3; color: var(--mute); }

.side-nav { display: flex; flex-direction: column; }

/* ------------------------------------------------------ the three groups */
/* Amendment 3 rule 1. Six rows in one undivided list is a table of contents;
   the same six in three groups with two labels is a navigation whose shape
   can be read before a word of it is. Mercury's rail is the reference and it
   is what a rail of the same width looks like when it is full rather than
   wide.

   The gap between groups is 14 rather than the app's 16, because a label
   already carries 4px of its own under it and 16 + 4 reads as a missing row.
   The first group has no label and no gap above it: it is one row, and a
   heading over one row is a heading about nothing. */
.side-group + .side-group { margin-top: 0; }
.side-group { display: flex; flex-direction: column; gap: 1px; }

/* The table header's own rung, 11px at 600 with .06em of tracking, which is
   what every other quiet label in this app is set at. `--muted-light` on
   `--light` measures 4.78:1, which clears the bar at this size. */
.side-label {
  display: block;
  margin: 0;
  padding: 14px 10px 6px;
  font-size: 12px;
  font-weight: 500;
  line-height: 1;
  color: var(--faint);
}

/* One rail item, and it is a 34px row since amendment 3. 13px at 500, a 16px
   glyph in the same paint as the word so the row reads as one object, 6px of
   radius because it is a functional control rather than a card.

   34 rather than 30, and it is the one number in this pass that is about feel
   rather than about content: a row carrying a value on its right needs the
   value to sit in air rather than against the row's own edge, and four pixels
   is the difference between a list and a set of rows. */
.nav-item {
  display: flex;
  align-items: center;
  gap: 10px;
  height: 34px;
  padding: 0 10px;
  border-radius: 9px;
  font-size: 13.5px;
  font-weight: 500;
  line-height: 1.25;
  color: var(--ink-2);
  text-decoration: none;
  transition: background var(--t-base) var(--ease-out),
              color var(--t-base) var(--ease-out),
              transform var(--t-fast) var(--ease-out);
}
/* The word takes whatever the glyph and the fact leave, and gives up
   characters rather than pushing the fact off the row: a rail at 220 with a
   long label and a four-character price has to break somewhere, and an
   ellipsis on a word somebody already knows is the cheapest place. */
.nav-name {
  flex: 1 1 auto;
  min-width: 0;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
}
.nav-item:hover { background: var(--ground-2); color: var(--ink-warm); }
.nav-item:active { transform: scale(.99); }
/* Where you are, in three signals and no layout shift: the white ground that
   hover uses, the weight to 600, and a 2px accent bar drawn INSIDE the item
   as an inset shadow rather than as a border, so marking an item never moves
   its label by 2px. `--ink` on white measures 15.8:1; the blue is the bar
   only, because `#0071e3` on `--light` is 4.31 and the panel taught us that
   once already. */
.nav-item[aria-current] {
  background: var(--window);
  color: var(--ink-warm);
  font-weight: 600;
  box-shadow: var(--sh-1);
}
.nav-item[aria-current] .nav-glyph { color: var(--blue); }

.nav-glyph { flex: none; display: block; width: 17px; height: 17px; color: var(--mute); }
.nav-glyph svg { display: block; width: 17px; height: 17px; }

/* -------------------------------------------------- the facts on the rows */
/* Amendment 3 rule 2, and the whole of what separates this rail from the one
   Ramon called small. A row that says "Signatures" is a link; a row that says
   "Signatures 2" is a fact about his business. 12px against the label's 13,
   `--muted-light` against its ink, tabular so two rows of digits line up.

   It stays 12px/500 under `[aria-current]` while the label goes to 600: the
   mark is about where you are standing, and thickening the number with it
   would make the count look like it had changed. */
.nav-fact {
  flex: none;
  margin-left: auto;
  font-size: 12px;
  font-weight: 500;
  line-height: 1.3;
  color: var(--faint);
  font-variant-numeric: tabular-nums;
}
/* A dot and no word. The card is either drawing for strangers or it is not,
   which is a binary and the app's own six-pixel disc is how it says one
   everywhere else. Grey is off and green is live; nothing here is ever
   `--alert`, because an unpublished card is a choice rather than a fault. */
.nav-dot {
  flex: none;
  width: 7px;
  height: 7px;
  margin-right: 2px;
  border-radius: 50%;
  background: var(--hair);
}
.nav-dot-live { background: var(--live-dot); }

/* ------------------------------------------------------- the mini block */
/* Amendment 3 rule 3, and it is Mercury's bookmarks: two numbers standing in
   the rail so the question "is any of this working" is answered before
   anything is opened. A label and two rows, no chart, no delta, no control.
   The whole block is one link to Home, because the answer to "and then what"
   is the dashboard and a second control here would be a second dashboard.

   The hairline above it is the rail's own `--hair`, pulled out to the rail's
   edges by the negative margin, so it reads as a division of the rail rather
   than as a box inside it. Nothing in this app announces a section with a
   ground. */
.rail-mini {
  display: block;
  margin: 0;
  padding: 0 10px;
  border-top: 0;
  color: var(--mute);
  text-decoration: none;
  border-radius: 0;
}
.rail-mini-label {
  display: block;
  margin-bottom: 2px;
  font-size: 12px;
  line-height: 1.3;
}
.rail-mini-row {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 8px;
  min-height: 24px;
  font-size: 12.5px;
  line-height: 1.3;
}
.rail-mini-row strong {
  font-weight: 500;
  color: var(--ink);
  font-variant-numeric: tabular-nums;
}
/* The one thing it does under a pointer: the label wakes up. A ground here
   would make it a card, and it is a glance. */
.rail-mini:hover .rail-mini-label { color: var(--ink); }
.rail-mini:focus-visible { border-radius: 6px; }

/* The foot of the rail: the way to reach a person, then who is signed in and
   the way out. Pushed down by the spacer rather than by a fixed height, so a
   rail with six items and a rail with nine both put it in the same place. */
.side-foot { display: flex; flex-direction: column; gap: 8px; margin-top: auto; }

/* Who this is, and the way out, on ONE 40px row, which is where every
   application in the world has trained people to look for it. */
.side-who {
  display: flex;
  align-items: center;
  gap: 8px;
  padding: 6px 8px;
}
/* The customer's own face, at 24px. Amendment 3 rule 4, and it reverses
   amendment 2's argument rather than ignoring it: that argument was that a
   24px crop of a card's portrait is a smudge, and it is right about THAT
   crop. This one is cut at 48 for this disc, so it is a real picture at a
   retina 2x rather than a 256px hero squeezed into a sixth of itself, and it
   is the one thing that makes the foot of the rail somebody's rather than an
   account's. */
.side-face {
  flex: none;
  width: 24px;
  height: 24px;
  border-radius: 50%;
  object-fit: cover;
  background: var(--white);
  border: 1px solid var(--hair);
}
/* The fallback, and it is most accounts on their first day: initials, for an
   identity with no photograph in it yet. */
.side-disc {
  flex: none;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 24px;
  height: 24px;
  border-radius: 50%;
  background: var(--white);
  border: 1px solid var(--hair);
  font-size: 10px;
  font-weight: 600;
  letter-spacing: .01em;
  color: var(--muted-light);
}
/* One line, cut with an ellipsis, and the whole of it in `title`. An address
   wrapped at any character inside a 220px rail leaves a single letter alone
   on the last line, which reads as a rendering fault rather than as an email
   address. Nothing is lost: the full text is in the attribute and Settings
   prints it whole. */
.side-mail {
  flex: 1 1 auto;
  min-width: 0;
  font-size: 12.5px;
  line-height: 1.3;
  color: var(--mute);
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
.side-out { flex: none; }
.side-out button {
  font-size: 12px;
  line-height: 1.3;
  color: var(--muted-light);
  padding: 2px;
  border-radius: 4px;
  transition: color var(--t-base) var(--ease-out);
}
.side-out button:hover { color: var(--ink); text-decoration: underline; }

/* ------------------------------------------------------ the main column */
/* 1240 and 24px gutters, which is Linear's and Vercel's content width to
   within a few pixels. On a phone the gutters are 16, because 24 either side
   of a 375px screen is 13 per cent of it spent on nothing. */
.app-main {
  --col-max: 1240px;
  width: 100%;
  padding: 18px 12px 110px;
  /* The Daybook window (DESIGN.md 2.2b). Below 1024 it is the whole screen,
     square and flat; from 1024 it is an inset ivory sheet on the linen. */
  background: var(--window);
  /* Centred in whatever is left of the window once the rail has its 220.
     The column was left-pinned, which reads as intended next to the rail up
     to about 1600px and as a page stuck in a corner on an ultrawide: the
     owner saw his own dashboard with more empty field than content. Auto
     margins cost nothing below the point where they matter. */
  margin-inline: auto;
}
/* The ivory window fills the grid column at every width and the 1240 cap is
   on what is in it (DESIGN.md 2.2b Home), so Home's grid can use all of it. */
.app-main > .app-head, .app-main > .view-bar, .app-main > .lens-bar,
.app-body { max-width: var(--col-max); margin-inline: auto; }

/* The support desk's lens, said on every screen it changes. A bar rather than
   a card because it is not a message about the screen, it is a condition the
   whole screen is being read under: a card would sit in the content as one
   more thing to read past, and this has to be the first thing seen and the
   last thing still there. Nobody but an admin who turned it on ever sees it,
   so it costs a customer nothing but the rule. */
.lens-bar {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
  padding: 8px 24px;
  margin-bottom: 16px;
  font-size: 13px;
  color: var(--ink);
  background: var(--well);
  border-radius: 12px;
}
.lens-bar form { margin: 0; }

/* The support view's bar: the lens bar's shape in amber, because it is the
   louder of the two conditions. Under a lens the account is the admin's own;
   under this one it is somebody else's, and the colour has to say so before
   the sentence is read. */
.view-bar {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
  padding: 8px 24px;
  margin-bottom: 16px;
  font-size: 13px;
  color: var(--ink);
  background: var(--well);
  border-radius: 12px;
}
.view-bar form { margin: 0; display: flex; gap: 8px; align-items: center; }

/* The page header, and it is ONE row with no sentence under it. 20px at 600
   with -0.2px of tracking: the app scale's own top rung, and not the section
   heading's 22 and not the page heading's 44, both of which are billboards.
   A screen with an action puts it on this line, right. */
.app-head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 8px 16px;
  min-height: 40px;
  padding-bottom: 12px;
  margin-bottom: 16px;
}
.app-head h1 {
  font: 400 40px/1.02 var(--serif);
  letter-spacing: -.026em;
  color: var(--ink-warm);
}
.app-head-do {
  flex: none;
  display: flex;
  align-items: center;
  gap: 8px;
}
/* The inline confirmation, beside the button it belongs to, at the micro
   rung. It fades on the timing platform.css already owns. */
.app-head .said {
  font-size: 12px;
  line-height: 1.3;
  color: var(--good);
  min-height: 0;
  margin: 0;
  max-width: 22ch;
}

/* --------------------------------------------------------- the panels */
/* White on a white canvas, told apart by one hairline in `--panel-edge`,
   which is the light-mode grammar Vercel runs and a shade lighter than the
   `--hair` the funnel's forms use. 8px of radius and 16px of padding: 12 and
   16 was amendment 1's, and 20 around a 16px inset is what put the corner of
   the content further from the edge than the middle of it was. */
.panel {
  background: none;
  border: 0;
  border-radius: 0;
  padding: 0;
}
.panel + .panel { margin-top: 34px; }

/* A 40px header row: the title at 13px/600 on the left, whatever the panel
   itself can be told to do on the right, and a hairline under the whole of it
   running edge to edge. The negative margin is what makes the rule reach the
   panel's own border instead of stopping 16px short of it on both sides,
   which is the difference between a header and a paragraph in bold. */
.panel-head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 8px 12px;
  min-height: 40px;
  margin: 0;
  padding: 0 0 6px;
}
.panel-head h2 {
  font: 450 21px/1.2 var(--serif);
  letter-spacing: -.01em;
  min-width: 0;
}
.panel-head-do {
  flex: none;
  display: flex;
  align-items: center;
  gap: 8px;
  min-width: 0;
}
/* What the right of a header row carries when it is a fact rather than a
   control: the theme a card is wearing, beside the picker that changes it. */
.panel-head-say {
  font-size: 12px;
  color: var(--muted-light);
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
.panel-head .said {
  font-size: 12px;
  color: var(--good);
  min-height: 0;
  margin: 0;
  max-width: 20ch;
}
/* A panel whose whole content is a table. The 16px is delivered by the cells
   instead, so a row's hover tint and its hairline run the full width of the
   panel rather than stopping short of it. */
.panel-flush { padding: 0; }
.panel-flush > .panel-head { margin: 0; }

/* The ONE line a panel is allowed, and only where it states a rule somebody
   needs in order to act: what the phone switch is off by default for, what a
   photograph may weigh, that a signature already sent is not rebuilt. 12px,
   `--muted-light`, and #6e6e73 on white measures 5.2:1. */
.rule {
  margin-top: 12px;
  max-width: 78ch;
  font-size: 12px;
  line-height: 1.4;
  color: var(--mute);
}
.rule a { color: var(--mute); }

/* ---------------------------------------------------- key and value rows */
/* The app's workhorse. A panel says four true things in the space a paragraph
   said one, and every screen in here is scanned rather than read. 36px rows
   with a hairline between them, the key quiet on the left and the value in
   the ink on the right. */
.lines { margin: 0; }
.lines > div {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 8px 16px;
  min-height: 36px;
  padding: 10px 8px;
  margin: 0 -8px;
  border-top: 0;
  border-radius: 10px;
  font-size: 13px;
  line-height: 1.4;
  transition: background var(--t-base) var(--ease-out);
}
.lines > div:first-child { border-top: 0; }
.lines > div:hover { background: var(--well); }
.lines dt { flex: none; color: var(--muted-light); }
.lines dd {
  min-width: 0;
  text-align: right;
  color: var(--ink);
  overflow-wrap: anywhere;
}
/* The two rows whose value is a control rather than a word. */
.lines dd .btn-text { margin-left: 8px; }
.lines-do dd {
  display: flex;
  align-items: center;
  justify-content: flex-end;
  gap: 2px 8px;
  flex-wrap: wrap;
}

/* What names one table inside a panel that holds several: Billing on an
   account with two signatures. The table header's own rung, so it reads as
   part of the table rather than as a second panel title. */
.group {
  margin-top: 20px;
  padding-bottom: 4px;
  font-size: 11px;
  font-weight: 600;
  letter-spacing: .06em;
  text-transform: uppercase;
  color: var(--muted-light);
}
.group:first-child { margin-top: 0; }

/* A quiet row of facts under a picture: what template, what plan, which day.
   Horizontal, because three short values in a column is three lines of white
   beside them, and the key is the table header's own rung. */
.facts {
  display: flex;
  flex-wrap: wrap;
  gap: 10px 28px;
  margin-top: 14px;
  padding-top: 0;
  border-top: 0;
}
.facts > div {
  font-size: 12.5px;
  font-weight: 500;
  letter-spacing: 0;
  text-transform: none;
  color: var(--mute);
}
.facts strong {
  display: block;
  margin-top: 4px;
  font: 400 22px/1.05 var(--serif);
  letter-spacing: normal;
  text-transform: none;
  color: var(--ink-warm);
}

/* ------------------------------------------------------------ controls */
/* Three tiers and no capsules. `.pill` is the landing page's action language
   and it is 980px of radius at 17px, which on a working screen reads as a
   marketing button that wandered in; nothing under `/app` draws one.

   32px tall, 6px of radius, 13px at 500, 12px of horizontal padding. The
   height is what makes a header row 40 and a kv row 36 sit together. */
.btn, .btn-primary, .btn-text {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 6px;
  height: 38px;
  padding: 0 15px;
  border: 1px solid transparent;
  border-radius: 11px;
  font-family: inherit;
  font-size: 13.5px;
  font-weight: 600;
  line-height: 1;
  letter-spacing: normal;
  white-space: nowrap;
  text-decoration: none;
  cursor: pointer;
  background: none;
  transition: background var(--t-base) var(--ease-out),
              border-color var(--t-base) var(--ease-out),
              color var(--t-base) var(--ease-out),
              transform var(--t-fast) var(--ease-out);
}
.btn {
  background: var(--window);
  border-color: transparent;
  box-shadow: inset 0 0 0 1px var(--line-warm), var(--sh-1);
  color: var(--ink-warm);
}
.btn:hover { background: var(--well); }
/* A locked control reads as locked: the owner Ask box on a plan without Mark. */
.btn:disabled, .btn-primary:disabled { opacity: .45; cursor: default; }
.btn:disabled:hover { background: transparent; }
.btn-primary { background: var(--blue); color: #fff; }
.btn-primary:hover { background: var(--blue-hover); }
/* No fill and no rule until a pointer is on it. `--ink` rather than `--blue`,
   because these sit inside kv rows and beside 13px values, and a blue word in
   a table is a link pretending to be data. */
.btn-text { height: 32px; padding: 0 4px; border-radius: 6px; font-size: 13px; font-weight: 600; color: var(--blue); }
.btn-text:hover { text-decoration: underline; }
.btn:active, .btn-primary:active, .btn-text:active { transform: scale(.98); }
.btn[hidden], .btn-primary[hidden], .btn-text[hidden] { display: none; }
.btn[aria-disabled="true"] {
  color: var(--muted-light);
  cursor: default;
  pointer-events: none;
}
/* A row of them, under a preview or at the end of a form. */
.dorow { display: flex; flex-wrap: wrap; align-items: center; gap: 8px; }

/* ------------------------------------------------------------- status */
/* A 6px disc and one word. Grey is off, green is live, and red is reserved
   for a state that has actually failed - a payment - because "Not published"
   in `--alert` reads as a fault on a screen where it is a choice. */
.state {
  display: inline-flex;
  align-items: center;
  gap: 7px;
  white-space: nowrap;
}
.state::before {
  content: "";
  flex: none;
  width: 7px;
  height: 7px;
  border-radius: 50%;
  background: none;
  box-shadow: inset 0 0 0 1.5px var(--faint);
}
.state-live::before { background: var(--live-dot); box-shadow: none; }
.state-bad::before { background: var(--alert); box-shadow: none; }

/* ----------------------------------------------------------- the table */
/* A list of things with a template, a price, a state and a date is a table.
   The header row is 12.5px `--mute` over one `--line-warm` rule, the only
   rule in the table; the cells are 13px. */
.dtable { width: calc(100% + 16px); margin: 0 -8px; border-collapse: separate; border-spacing: 0; }
.dtable th {
  padding: 0 8px 8px;
  text-align: left;
  font-size: 12.5px;
  font-weight: 500;
  letter-spacing: 0;
  text-transform: none;
  color: var(--mute);
  border-bottom: 1px solid var(--line-warm);
  white-space: nowrap;
}
.dtable td {
  padding: 10px 8px;
  font-size: 13px;
  vertical-align: middle;
  border-bottom: 0;
}
.dtable tbody td:first-child { border-radius: 10px 0 0 10px; }
.dtable tbody td:last-child { border-radius: 0 10px 10px 0; }
.dtable tbody tr:last-child td { border-bottom: 0; }
/* The row answers a pointer, and the whole of it is pressable. It cannot BE
   the link: a signature's own markup carries anchors, and an anchor around
   those is invalid nesting a browser silently unpicks. One link, stretched
   over the row by its own pseudo-element, and the focus ring is drawn on the
   row so what a keyboard highlights is what a pointer presses. */
.dtable tbody tr {
  position: relative;
  transition: background var(--t-base) var(--ease-out);
}
.dtable tbody tr:hover > td { background: var(--well); }
.dtable tbody tr:has(.row-link:focus-visible) {
  outline: 3px solid var(--blue);
  outline-offset: -3px;
}
.row-link { font-size: 13px; font-weight: 500; color: var(--ink); text-decoration: none; }
.row-link::after { content: ""; position: absolute; inset: 0; }
.row-link:hover { text-decoration: underline; }
.row-link:focus-visible { outline: none; }

/* The card at a fifth of the size, on a `--light` inset with no border of its
   own: a bordered thumbnail inside a bordered row inside a bordered panel is
   three rules to say one thing. `zoom` rather than `transform: scale()`,
   which is DESIGN.md 5's rule and the same reason the stage has it: the build
   is a table of inline-styled pixel boxes, so `zoom` keeps the layout honest
   and a transform would leave the unscaled 508px box behind for the cell to
   lay itself out against.

   120 x 72 is the whole card rather than a band of it. The install build
   measures 508 by 288 to 292 depending on the template, which is 69 at this
   scale. The box is FIXED rather than sized to its contents, because a table
   whose rows are each as tall as the template they hold is a ragged table.

   96 until amendment 3, and the twenty-four pixels are the rule's own: the
   row carries two more columns of numbers now, so it is taller, and a 96px
   picture in a taller row reads as a stamp on a form rather than as the thing
   the row is about. 160 is still wrong, and it is what the density pass
   reached for when it was looking for something to fill the width with. */
.row-shot {
  display: flex;
  align-items: center;
  justify-content: center;
  width: 120px;
  height: 72px;
  border-radius: 8px;
  background: var(--light);
  overflow: hidden;
}
.row-zoom { flex: none; zoom: .2362; }             /* 508 -> 120 */
/* `max-width: none`, and it is worth four points of best practices. The reset
   in platform.css gives every image `max-width: 100%`, which is right for a
   page and wrong inside a signature: the build is a table of inline-styled
   pixel boxes, and a 72px monogram told it may be no wider than its cell is
   drawn 46 x 72 in a cell the table then squeezes. Lighthouse's
   `image-aspect-ratio` is what named it. */
.row-shot img { max-width: none; }
.c-shot { width: 120px; }
/* Amendment 3 rule 9. Two columns of counts, and they follow the app's own
   rule for a figure: tabular, right-aligned so the digits stack, never
   wrapped. `--ink` rather than the muted grey the plan and the date wear,
   because these two are the reason somebody opened the list. */
.dtable .c-num {
  width: 1%;
  text-align: right;
  white-space: nowrap;
  font-variant-numeric: tabular-nums;
}
.dtable td.c-num { color: var(--ink); }
/* The name takes whatever is left, so the six columns after it sit together
   against the right of the table rather than being sprayed evenly across
   1400px of row. `width: 100%` on one cell of an auto-laid table is how that
   is said; every other column is then as wide as what is in it. */
.dtable th:nth-child(2), .dtable td:nth-child(2) { width: 100%; }
/* The two lines a row wears when the table is too narrow to be one: the plan,
   the state and the date said in one muted line under the name. */
.c-sub { display: block; margin-top: 3px; font-size: 12px; color: var(--muted-light); }
.c-go { width: 24px; color: var(--muted-light); }
.c-go svg { width: 16px; height: 16px; display: block; }
.dtable .c-when, .dtable .c-plan { color: var(--muted-light); white-space: nowrap; }
/* A phone number is the point of a contact, so it keeps its column at every
   width, unlike the other muted columns (Codex, 2026-10-09). */
.dtable .c-phone { color: var(--muted-light); white-space: nowrap; }
@media (max-width: 699px) {
  /* The name cell already carries the address in its sub line, so the
     Email column steps aside on a phone and the phone number keeps its room. */
  .dtable .c-mail { display: none; }
  .dtable .c-phone { white-space: normal; }
}
/* The desk's tables are wider than a phone and use no `c-*` classes, so
   nothing steps aside: the table scrolls inside its panel instead of the
   page scrolling sideways. */
.scroll-x { overflow-x: auto; -webkit-overflow-scrolling: touch; }
.app-admin .dtable th { white-space: nowrap; }
.app-admin .dtable td { white-space: normal; }
.app-admin .dtable td.c-what { white-space: nowrap; width: 1%; }
@media (max-width: 699px) { .app-admin .dtable td { white-space: nowrap; } }
.app-admin .dtable td.wrap { white-space: pre-wrap; min-width: 24ch; }
.app-admin form { display: inline; }
.app-admin textarea { width: 100%; min-height: 28rem; font: 13px/1.5 ui-monospace, Menlo, monospace; }
/* Mark Studio's diff (SEL-39): what the card says now, struck through in
   the muted grey, beside what the draft would make it, both keeping the
   line breaks a bio has. A high-risk tier wears the alert red. */
.diff-before { color: var(--muted-light); text-decoration: line-through; white-space: pre-wrap; }
.diff-after { white-space: pre-wrap; }
.diff-before, .diff-after { width: 42%; }

/* ---------------------------------------------------------- the wells */
/* Where a preview object sits: `--light`, 8px, no border. Rule 2's "nothing
   inside a panel has a border of its own" is the whole point - the panel is
   already a box, and a second one around the picture inside it is the "boxes
   inside boxes" Ramon was looking at. */
.well {
  display: flex;
  align-items: center;
  justify-content: center;
  padding: 12px;
  border-radius: 8px;
  background: var(--light);
  overflow-x: auto;
  overflow-y: hidden;
}
.well .cardhost { overflow: visible; }

/* The real card at phone width, in its own frame. It is the same component as
   the picker's `.shot` at a different scale: the card is laid out at 380 and
   then photographed, never laid out small, because a card laid out small is a
   different design. 380 x 500 is measured rather than guessed - every one of
   the seven documents reports exactly 500px of scroll height at 380 wide.

   The phone frame keeps its hairline, and it is the one exception rule 2
   names: it is a frame around a live document rather than a border around a
   picture, and without it the white card bleeds into the white panel. */
.livecard {
  --live: .726;
  display: block;
  width: calc(380px * var(--live));
  height: calc(500px * var(--live));
  max-width: 100%;
  border-radius: 8px;
  overflow: hidden;
  background: var(--light);
  border: 1px solid var(--panel-edge);
  position: relative;
  pointer-events: none;
}
.livecard iframe {
  position: absolute;
  top: 0;
  left: 0;
  width: 380px;
  height: 500px;
  border: 0;
  transform-origin: 0 0;
  transform: scale(var(--live));
}
/* Below 700 there is one column and the card is the only thing in its panel,
   so it is centred: air on one side reads as a box that failed to fill and
   air on both reads as a phone held up. */
@media (max-width: 699px) {
  .card-preview .livecard { margin-left: auto; margin-right: auto; }
}

/* ------------------------------------------------------- the theme grid */
/* Seven live cards at 150px in a four-up grid, the name under each at 12px,
   and NOTHING else: the blurb and the "add a photo to fill this one" italics
   are both gone. Seven previews are seven answers to what a theme looks like,
   and a sentence under each of them is a paragraph nobody reads standing in
   front of the picture it describes.

   `auto-fill` rather than a fixed four, because the column this sits in is
   656px inside at 1280 and wider at 1440, and a fixed four would crop the
   frame the moment the column was narrower than 636. */
.app-main .themes {
  grid-template-columns: repeat(auto-fill, minmax(150px, 1fr));
  gap: 12px;
  margin: 0;
}
.app-main .themes label {
  padding: 0;
  border: 0;
  border-radius: 8px;
  background: none;
  gap: 6px;
}
.app-main .themes label:hover { background: none; }
.app-main .themes label:hover .shot { transform: translateY(-1px); }
.app-main .themes .pick:checked + label { background: none; border: 0; }
/* A 2px ring in `--blue` on the tile itself, drawn as a shadow so choosing a
   theme never moves the grid by 2px. */
.app-main .themes .pick:checked + label .shot {
  box-shadow: 0 0 0 2px var(--blue);
}
.app-main .themes .pick:focus-visible + label .shot {
  outline: 3px solid var(--blue);
  outline-offset: 3px;
}
.app-main .themes .pick:focus-visible + label { outline: none; }
.app-main .shot {
  width: 150px;
  height: 197px;
  border-radius: 8px;
  background: var(--light);
  transition: transform var(--t-base) var(--ease-out),
              box-shadow var(--t-base) var(--ease-out);
}
.app-main .shot .mini { transform: scale(.3947); }   /* 380 -> 150 */
.app-main .themes .tname {
  font-size: 12px;
  font-weight: 500;
  color: var(--muted-light);
  margin: 0;
}
.app-main .themes .pick:checked + label .tname { color: var(--ink); font-weight: 600; }
.app-main .themes .tblurb, .app-main .themes .tnote { display: none; }

/* ------------------------------------------------------ the starter shelf */
/* The Brand screen's eight presets and the None tile in front of them, in the
   theme grid's own grammar: a real radio, a label around a tile, the name
   under it at 12px. The tile is a SWATCH rather than an iframe: a 3:2 block
   painted in the starter's surface, a wide bar of its accent, a thin bar of
   its second colour, and its name set in its ink on its surface, which is the
   four colours shown doing the four jobs they will do on the card.

   Two across until 1280 and four from it, keyed to the COLUMN rather than
   to the phone: from 700 the screen is already two columns and the form's
   is 364px wide at 768 and 400 at 1024, where four tiles would be narrower
   than the word inside them. At 1280 the column is 884 and four is right. */
.app-main .presets { grid-template-columns: repeat(2, minmax(0, 1fr)); }
@media (min-width: 1280px) {
  .app-main .presets { grid-template-columns: repeat(4, minmax(0, 1fr)); }
}
.app-main .preset-tile {
  display: grid;
  grid-template-rows: 1fr auto auto;
  gap: 4px;
  width: 100%;
  aspect-ratio: 3 / 2;
  padding: 10px;
  box-sizing: border-box;
  border-radius: 8px;
  background: var(--tile-surface);
  border: 1px solid var(--panel-edge);
  transition: transform var(--t-base) var(--ease-out),
              box-shadow var(--t-base) var(--ease-out);
}
.app-main .preset-word {
  font-size: 13px;
  font-weight: 600;
  line-height: 1.2;
  color: var(--tile-ink);
  align-self: start;
}
.app-main .preset-bar {
  display: block;
  height: 8px;
  border-radius: 4px;
  background: var(--tile-accent);
}
.app-main .preset-bar-2 {
  height: 3px;
  width: 55%;
  background: var(--tile-accent-2);
}
.app-main .presets label:hover .preset-tile { transform: translateY(-1px); }
.app-main .presets .pick:checked + label .preset-tile {
  box-shadow: 0 0 0 2px var(--blue);
}
.app-main .presets .pick:focus-visible + label .preset-tile {
  outline: 3px solid var(--blue);
  outline-offset: 3px;
}
.app-main .presets .pick:focus-visible + label .shot { outline: none; }
.app-main .presets .tmood {
  display: block;
  font-size: 12px;
  line-height: 1.3;
  color: var(--muted-light);
}

/* ------------------------------------------------------- the picture shelf */
/* The Social screen's eight presets, in the starter shelf's grammar: a real
   radio, a label around a tile, the name under it, two across and four from
   1280 for the column's own reason. The tile is the 320 preview itself,
   playing, and it is cropped to a circle because every slot the picture is
   for crops to one: what the tile shows is what LinkedIn or Discord will
   show, and nothing they will cut away. The ring on the checked tile is the
   theme grid's 2px shadow, drawn round. A tile is never wider than its 320
   source, so nothing on the shelf is an upscale.

   The big one on the left is the same circle from the 1024, which
   downsamples on every display it is shown on, or the 320 preview in the
   same footprint while the full-size one is being made, so the panel does
   not change height when the render lands. */
.app-main .pic-tile {
  display: block;
  width: 100%;
  max-width: 320px;
  aspect-ratio: 1 / 1;
  transition: transform var(--t-base) var(--ease-out);
}
.app-main .pic-tile img {
  display: block;
  width: 100%;
  height: 100%;
  border-radius: 50%;
  background: var(--light);
  transition: box-shadow var(--t-base) var(--ease-out);
}
.app-main .pic-shelf label:hover .pic-tile { transform: translateY(-1px); }
.app-main .pic-shelf .pick:checked + label .pic-tile img {
  box-shadow: 0 0 0 2px var(--blue);
}
.app-main .pic-shelf .pick:focus-visible + label .pic-tile img {
  outline: 3px solid var(--blue);
  outline-offset: 3px;
}
/* The frame round the big one wears the accent as its ring and the surface
   behind it, as two custom properties the screen's script rewrites the
   instant a swatch moves, before any server has drawn a thing. */
.app-main .pic-frame {
  --pic-accent: var(--blue);
  --pic-surface: var(--light);
  width: min(100%, 512px);
  margin: 0 auto;
  padding: 6px;
  box-sizing: border-box;
  border: 2px solid var(--pic-accent);
  border-radius: 50%;
  background: var(--pic-surface);
  transition: border-color var(--t-base) var(--ease-out),
              background var(--t-base) var(--ease-out);
}
.app-main .pic-big {
  display: block;
  width: 100%;
  aspect-ratio: 1 / 1;
  margin: 0 auto;
}
.app-main .pic-big img {
  display: block;
  width: 100%;
  height: 100%;
  border-radius: 50%;
  background: var(--light);
}
.app-main .pic-drawing { margin: 10px 0 0; text-align: center; }
.app-main .pic-get {
  display: flex;
  justify-content: center;
  gap: 8px;
  margin: 12px 0 0;
}
.app-main .pic-lede { margin: 0 0 16px; }

/* A mode the files cannot draw: the row keeps its place and goes muted, and
   the sentence under the name says what unlocks it. The pointer is left
   alone so the hint reads on hover. */
.app-main .switch input:disabled { opacity: .45; cursor: default; }
.app-main .switch-off { cursor: default; }
.app-main .switch-off strong { color: var(--muted-light); }

/* The words, dimmed while another mode is checked: still a field, still
   posted, so what was typed survives a change of mind. */
.app-main .pic-dim { opacity: .5; }
.app-main .pic-dim:hover { opacity: .8; }

/* From your Brand: the mark in the Brand screen's own well, then three
   colour rows, each a 28px circle of the colour, its name, the picker, the
   hex in mono and the way back to Brand. */
.app-main .pic-mark { display: flex; align-items: center; gap: 12px; margin-bottom: 4px; }
.app-main .pic-mark .rule { margin: 0; }
.app-main .pic-colour { margin-top: 10px; gap: 8px; flex-wrap: wrap; }
.app-main .pic-swatch {
  flex: none;
  width: 28px;
  height: 28px;
  border-radius: 50%;
  border: 1px solid var(--hair);
  box-sizing: border-box;
}
.app-main .pic-colour-name { flex: 0 0 56px; font-size: 13px; }
.app-main .pic-colour input[type="color"] { width: 28px; height: 28px; border-radius: 50%; }
.app-main .pic-colour input[type="text"] {
  width: 84px;
  font-family: ui-monospace, "SF Mono", Menlo, Consolas, monospace;
  font-size: 12px;
}
.app-main .pic-colour .pic-reset { font-size: 12px; color: var(--muted-light); }
.app-main .pic-colour .err { flex-basis: 100%; }

/* ---------------------------------------------------------- the switches */
/* A real 36 x 20 toggle, and it is still a real checkbox in a real label,
   which is what makes it save with scripting off. `appearance: none` is what
   lets the box be drawn as a track and its `::after` as the thumb.
   40px rows: the label at 13px/500 over one 12px line, and the toggle on the
   right, where an app puts the thing you flip. */
.app-main .switch {
  display: flex;
  flex-direction: row-reverse;
  align-items: center;
  justify-content: space-between;
  gap: 16px;
  min-height: 40px;
  padding: 4px 0;
  margin: 0;
  border: 0;
  border-radius: 0;
  background: none;
  font-size: 13px;
  cursor: pointer;
  transition: transform var(--t-fast) var(--ease-out);
}
.app-main .switch + .switch { border-top: 1px solid var(--panel-edge); }
.app-main .switch:hover { background: none; }
.app-main .switch:has(input:checked) { background: none; border-color: var(--panel-edge); }
.app-main .switch input {
  appearance: none;
  -webkit-appearance: none;
  flex: none;
  position: relative;
  width: 36px;
  height: 20px;
  margin: 0;
  border-radius: 999px;
  background: var(--hair);
  cursor: pointer;
  transition: background var(--t-base) var(--ease-out);
}
.app-main .switch input::after {
  content: "";
  position: absolute;
  top: 2px;
  left: 2px;
  width: 16px;
  height: 16px;
  border-radius: 50%;
  background: #fff;
  box-shadow: 0 1px 2px rgba(0, 0, 0, .28);
  transition: transform var(--t-base) var(--ease-out);
}
.app-main .switch input:checked { background: var(--blue); }
.app-main .switch input:checked::after { transform: translateX(16px); }
.app-main .switch .choice-body { min-width: 0; }
.app-main .switch strong { display: block; font-size: 13px; font-weight: 500; line-height: 1.3; }
.app-main .switch span {
  display: block;
  margin-top: 2px;
  font-size: 12px;
  line-height: 1.35;
  color: var(--muted-light);
}
.switch:active { transform: scale(.995); }

/* ------------------------------------------------------------ the form */
/* 32px fields under 12px labels, 8px between a label and its field and 16px
   between rows. One step under amendment 1's 36 and 13, which is the step
   between a form somebody fills in once and a screen somebody corrects. */
.app-main .field { margin-top: 16px; }
.app-main .field:first-of-type { margin-top: 0; }
.app-main .field label {
  display: block;
  font-size: 12.5px;
  font-weight: 500;
  color: var(--mute);
  margin-bottom: 8px;
}
.app-main .field .opt { color: var(--muted-light); font-weight: 400; }
.app-main .field input[type="text"],
.app-main .field input[type="email"],
.app-main .field input[type="url"],
.app-main .field input[type="password"] {
  height: 38px;
  font-size: 13px;
  line-height: 1.3;
  padding: 0 10px;
  border: 0;
  border-radius: 10px;
  box-shadow: inset 0 0 0 1px var(--line-warm);
  background: var(--window);
}
.app-main .field input:focus {
  outline: 2px solid var(--blue);
  outline-offset: 2px;
  box-shadow: inset 0 0 0 1px var(--line-warm);
}
/* Two fields on one line, and the row owns the 16px rather than the fields
   in it. `.field:first-of-type` is scoped to a PARENT, so inside a two-column
   grid the left field is the first of its type and the right one is not: the
   left kept its zero margin and the right took 16, and the two halves of one
   row sat 16px out of step. Measured on Profile at 1280: Title's box at 218
   and Company's at 234. */
.app-main .row2 { margin-top: 16px; gap: 12px 16px; }
.app-main .row2 > .field { margin-top: 0; min-width: 0; }
.app-main .err { margin-top: 6px; font-size: 12px; }

/* The week, one line a day. A day is a switch, two times and the word
   between them, and it fits on one 48px line because seven of them are one
   answer rather than seven forms: stacked as labelled fields it was a
   three-line block each and the screen became a scroll of twenty-one boxes.
   The hairline between rows is the row2 grammar, not a border on a box.

   A day that is closed DIMS rather than disappears. The times it used to
   open at are the times somebody switching it back on means, so taking the
   two inputs off the row would throw away the answer and ask for it again;
   at .45 they are still there, still filled in, and plainly not in force.
   `.hours-off` is the first paint, drawn from what was saved, and the two
   `:has` rules take it over the moment the switch moves, the way
   `.switch:has(input:checked)` above already does. */
.app-main .hours { display: grid; }
.app-main .hours-row {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: space-between;
  gap: 8px 16px;
  min-height: 48px;
  padding: 4px 0;
}
.app-main .hours-row + .hours-row { border-top: 1px solid var(--line-soft); }
.app-main .hours-row .switch { flex: 1 1 140px; min-height: 0; padding: 0; }
.app-main .hours-span { display: flex; align-items: center; gap: 8px; }
.app-main .hours-to { font-size: 12px; color: var(--muted-light); }
.app-main .hours-span input[type="time"] {
  height: 38px;
  width: 120px;
  font-family: inherit;
  font-size: 13px;
  line-height: 1.3;
  padding: 0 8px;
  border: 0;
  border-radius: 10px;
  box-shadow: inset 0 0 0 1px var(--line-warm);
  background: var(--window);
  color: var(--ink);
}
.app-main .hours-span input[type="time"]:focus {
  outline: 2px solid var(--blue);
  outline-offset: 2px;
}
.app-main .hours-off .hours-span { opacity: .45; }
.app-main .hours-row:has(input[type="checkbox"]:checked) .hours-span { opacity: 1; }
.app-main .hours-row:has(input[type="checkbox"]:not(:checked)) .hours-span { opacity: .45; }
.app-main .hours-row .err { flex-basis: 100%; margin-top: 0; }

/* The service editor's other two controls, at the field's own 32px and 6px:
   a select is the input with the browser's arrow, a textarea is the input
   three lines tall. `resize: vertical` because a box somebody can drag
   sideways out of its column is a box that breaks the grid. */
.app-main .field select,
.app-main .field textarea {
  display: block;
  width: 100%;
  font-family: inherit;
  font-size: 13px;
  line-height: 1.3;
  padding: 0 10px;
  border: 0;
  border-radius: 10px;
  box-shadow: inset 0 0 0 1px var(--line-warm);
  background: var(--window);
  color: var(--ink);
}
.app-main .field select { height: 38px; }
.app-main .field textarea { min-height: 80px; padding: 8px 10px; resize: vertical; }
.app-main .field select:focus,
.app-main .field textarea:focus {
  outline: 2px solid var(--blue);
  outline-offset: 2px;
}
/* A label over a row of radios, drawn as the field's label is; and the row
   itself: native radios beside 13px words, 20px apart, wrapping. A choice of
   three words is a row rather than three 40px switch rows. */
.app-main .field-label {
  display: block;
  font-size: 12px;
  font-weight: 500;
  color: var(--muted-light);
  margin-bottom: 8px;
}
.app-main .choices { display: flex; flex-wrap: wrap; gap: 8px 20px; min-height: 32px; align-items: center; }
.app-main .choice { display: inline-flex; align-items: center; gap: 6px; font-size: 13px; cursor: pointer; }
.app-main .choice input { margin: 0; accent-color: var(--blue); }
/* A field row folded away by the editor's script. `.row2` is a grid, so
   the attribute alone would lose, as it does on the chips. */
.app-main .row2[hidden], .app-main .field[hidden] { display: none; }
/* Under a form's last panel, the two secondary things it can do. */
.app-main .dorow-tail { margin-top: 16px; }
/* A flush panel that holds one line rather than a table. */
.panel-pad { padding: 16px; }
/* The two cells in a row-link table that hold their own forms. The stretched
   link is drawn over the whole row, so anything else pressable in it has to
   sit above that layer, or the row opens instead of the button pressing. */
.dtable .c-move, .dtable .c-do { width: 1%; white-space: nowrap; }
.dtable .c-move form, .dtable .c-do form { position: relative; z-index: 1; display: inline-flex; gap: 2px; }
.dtable .c-move .btn-text { padding: 0 6px; }

/* A label drawn as a button, which is what the photograph's Upload is: the
   real file input is off screen and this is the thing a pointer presses.
   `display` has to be restated, because `.portrait-say label` in platform.css
   is more specific than `.btn` and made it a full-width block. */
.app-main label.btn {
  display: inline-flex;
  margin-bottom: 0;
  font-size: 13px;
  font-weight: 500;
  color: var(--ink);
}

/* A file input at this scale. The browser's own chrome is the one control in
   here that cannot be redrawn, so what is set is what it will take: 12px, and
   its button at the app's 32px and 6px rather than the funnel's capsule. */
.app-main input[type="file"] { font-size: 12px; }
.app-main input[type="file"]::file-selector-button {
  height: 32px;
  padding: 0 12px;
  margin-right: 10px;
  margin-top: 0;
  border-radius: 6px;
  font-size: 13px;
  font-weight: 500;
  background: var(--white);
  border-color: var(--hair);
}

/* The card address, with the `/@` drawn INSIDE the field as an affix rather
   than repeated under it as a sentence. The affix is a real box in the flow
   and the input is what is left, so nothing overlaps at any width. */
.affixed {
  display: flex;
  align-items: center;
  height: 38px;
  border: 0;
  border-radius: 10px;
  box-shadow: inset 0 0 0 1px var(--line-warm);
  background: var(--window);
  overflow: hidden;
  transition: border-color .15s ease, box-shadow .15s ease;
}
.affixed:focus-within {
  outline: 2px solid var(--blue);
  outline-offset: 2px;
}
.affix {
  flex: none;
  padding: 0 0 0 10px;
  font-size: 13px;
  color: var(--muted-light);
  white-space: nowrap;
}
.app-main .affixed input[type="text"] {
  flex: 1 1 auto;
  min-width: 0;
  height: 38px;
  border: 0;
  border-radius: 0;
  box-shadow: none;
  padding: 0 10px 0 0;
  background: none;
}
.app-main .affixed input[type="text"]:focus { box-shadow: none; outline: none; }

/* The portrait, at 64px, and the control beside it. */
.app-main .portrait { display: flex; align-items: center; gap: 14px; flex-wrap: wrap; }
.app-main .portrait-shot {
  width: 64px;
  height: 64px;
  border-radius: 8px;
  border: 1px solid var(--panel-edge);
}
.app-main .portrait-mono { font-size: 22px; }
.app-main .portrait-say { flex: 1 1 130px; min-width: 0; }
/* A file input is about 230px of browser chrome that neither wraps nor
   ellipsizes politely, so it is hidden and the label beside it is the button.
   The input is still a real input in the real form and still what a keyboard
   focuses, because the `<label for>` moves the press onto it. */
.app-main .portrait-say input[type="file"] {
  position: absolute;
  width: 1px;
  height: 1px;
  overflow: hidden;
  clip-path: inset(50%);
}
.app-main .portrait-say input[type="file"]:focus-visible + .btn {
  outline: 3px solid var(--blue);
  outline-offset: 2px;
}
.app-main .filename {
  display: block;
  margin-top: 6px;
  font-size: 12px;
  color: var(--muted-light);
  overflow-wrap: anywhere;
}

/* The colour, on one row: a 32px swatch and the hex beside it. */
.app-main .swatch { display: flex; align-items: center; gap: 10px; min-width: 0; }
.app-main .swatch input[type="color"] {
  width: 32px;
  height: 32px;
  border-radius: 6px;
  border-color: var(--hair);
  padding: 0;
}
/* The hex, beside the swatch. Read-only, because the swatch is the control
   and two writable inputs for one value is two places a customer can disagree
   with themselves; it is a real field rather than a `<code>` so the value can
   be selected and copied the way a colour usually is. */
.app-main .swatch input[type="text"] {
  flex: none;
  width: 96px;
  min-width: 0;
  height: 32px;
  padding: 0 10px;
  font-family: inherit;
  font-size: 13px;
  line-height: 1.3;
  color: var(--muted-light);
  background: var(--white);
  border: 1px solid var(--hair);
  border-radius: 6px;
  text-transform: uppercase;
}
/* The rest of the link list, closed. Its summary IS the "Add link" control,
   so it wears `.btn-text` and has to be told the size twice: `.addmore >
   summary` in platform.css is more specific than the class. What opens is a
   plain run of fields, not a dashed box: a bordered container inside a
   bordered panel is the "boxes inside boxes" this pass is about. */
.app-main .addmore { margin-top: 16px; }
.app-main .addmore > summary {
  display: inline-flex;
  font-size: 13px;
  list-style: none;
}
.app-main .addmore > summary::-webkit-details-marker { display: none; }
.app-main .addmore-body {
  margin-top: 4px;
  padding: 0;
  border: 0;
  border-radius: 0;
}
.app-main .addline label { display: flex; align-items: center; gap: 7px; }

/* --------------------------------------------------- the brand dashboard */
/* Everything below draws ONE screen, and it is the screen the whole product
   is about. Ramon on the analytics screen this replaces: "that dashboard is
   really ugly... we are offering a brand dashboard.. aka signatures, digital
   profiles... i feel like they should be able to have a small preview of it in
   the dashboard." And on the first answer to that: "It's very generic. Make it
   interactive and dynamic, please."

   The grammar is Mercury's, measured off its live demo (`qa/ref-mercury-demo.png`,
   reference only, never traced): a greeting at a weight nothing else in the
   product uses, a row of pill verbs directly under it, ONE hero panel carrying
   one trusted number over the shape of it, and smaller object cards below. The
   subject is the only thing that changed, and it is the whole change: Mercury's
   hero is a balance and ours is the customer's signature.

   Four things here are exceptions to the app scale in DESIGN.md 1, and each is
   named there rather than smuggled in: the h1 at 24px/500, 999px of radius on
   the chips, 12px of radius on the hero panel, and the hero being the one
   panel in the app with any depth at all. */

/* ------------------------------------------------------------- the header */
/* Two rows where every other screen has one: the greeting with the period
   beside it, and the verbs under it. Mercury puts Send / Transfer / Deposit
   directly under "Welcome, Jane" and it is right for the reason the "next up"
   strip was wrong — a customer arriving at their own dashboard has three or
   four verbs in mind, and a paragraph introducing one of them answers none. */
.app-head-tall {
  display: block;                 /* the rows stack; `.app-head-row` is flex */
  padding-bottom: 14px;
}
.app-head-row {
  display: flex;
  align-items: flex-end;
  justify-content: space-between;
  gap: 24px;
  min-height: 40px;
  flex: 1 1 auto;                 /* fills `.app-head`, which is flex too */
  min-width: 0;
}
/* The app's only h1 at 500, and its only one over 20px. Mercury's greeting is
   28px LIGHT because a greeting is not a heading — it is the one line on the
   screen addressed to a person, and setting it at the weight of a section
   title makes the screen shout somebody's name at them. 24 rather than 28
   because this column is 1240 and Mercury's is 1220 with a search bar over it,
   and because 24/500 is one clean step off the 20/600 every other screen
   uses rather than two. */
.app-head h1.h1-big { font-size: 54px; }
/* Home's head (DESIGN.md 2.2b Home): the day and the workspace above the
   greeting, one sentence of news under it. `.sub` is a marketing class in
   platform.css, so the size and colour are set here, scoped to the head. */
.app-head-say { min-width: 0; }
.app-head .kick { margin: 0 0 10px; font-size: 13px; line-height: 1.3; color: var(--mute); }
.app-head .sub { margin: 10px 0 0; font-size: 15px; line-height: 1.45; color: var(--ink-2); }

/* ------------------------------------------------------------- the chips */
/* 32px capsules, and 999px of radius appears HERE and nowhere else under
   /app. Amendment 2 rule 5 threw the landing page's capsule out of the app and
   it stays out: `.pill` is 980px of radius at 17px and reads as a marketing
   button that wandered onto a working screen. This is a different object at a
   different size — 13px on a 32px row, a ground rather than a fill, in a row
   of four — and it is the shape Mercury, Linear and Vercel all use for a row
   of verbs under a greeting. The rule it replaces is not "no round corners",
   it is "no marketing buttons", and a 32px chip is not one.

   The ground is Mercury's own `rgba(112,115,147,.1)`: a cool grey at a tenth,
   which sits on white without becoming a box and darkens on hover rather than
   growing a border. */
.chips-do {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 8px;
  margin-top: 12px;
}
.chip {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  height: 32px;
  padding: 0 14px;
  border: 0;
  border-radius: 999px;
  background: rgba(112, 115, 147, .10);
  font-family: inherit;
  font-size: 13px;
  font-weight: 500;
  line-height: 1;
  letter-spacing: normal;
  white-space: nowrap;
  color: var(--ink);
  text-decoration: none;
  cursor: pointer;
  transition: background var(--t-base) var(--ease-out),
              transform var(--t-fast) var(--ease-out);
}
.chip:hover { background: rgba(112, 115, 147, .16); }
.chip:active { transform: scale(.97); }
.chip[hidden] { display: none; }
/* The one loud one, and there is exactly one on the screen. */
.chip-loud { background: var(--blue); color: #fff; }
.chip-loud:hover { background: var(--blue-hover); }

/* A missing field's name, under the profile object. Not a chip: it is a label
   for something that is NOT there, so it takes the quiet 22px ground the app
   already had rather than the shape of a thing to press. */
.tag {
  display: inline-flex;
  align-items: center;
  height: 22px;
  padding: 0 8px;
  border-radius: 6px;
  background: var(--light);
  font-size: 12px;
  color: var(--muted-light);
  white-space: nowrap;
}
.tag-tier { height: 18px; padding: 0 6px; font-size: 11px; letter-spacing: .01em; margin-left: 6px; vertical-align: middle; }
.micro span .tag-tier, .meter-say .tag-tier { display: inline-flex; text-transform: none; letter-spacing: .01em; font-weight: 500; }
.tag-verified { background: color-mix(in srgb, var(--good) 14%, transparent); color: var(--good); }
.tag-attributed { background: var(--light); color: var(--ink-2, inherit); }
.tag-low { background: transparent; box-shadow: inset 0 0 0 1px var(--hair); color: var(--muted-light); }
.tag-bad { background: color-mix(in srgb, var(--alert) 12%, transparent); color: var(--alert); }
.chips { display: flex; flex-wrap: wrap; gap: 6px; min-width: 0; }

/* ------------------------------------------------------ the period control */
/* 7, 30, 90 as one 32px segmented control right of the greeting. Real links,
   so it works with no script and each period is an address somebody can
   bookmark; the indicator that glides between them is `dash.js`. */
.period {
  position: relative;
  display: inline-flex;
  gap: 2px;
  height: auto;
  padding: 3px;
  border: 0;
  border-radius: 11px;
  background: var(--well-2);
}
.period a {
  position: relative;
  z-index: 1;
  display: inline-flex;
  align-items: center;
  height: 30px;
  padding: 0 13px;
  border-radius: 9px;
  font-size: 13px;
  font-weight: 500;
  line-height: 1;
  color: var(--mute);
  text-decoration: none;
  transition: color var(--t-base) var(--ease-out);
}
.period a:hover { color: var(--ink); }
.period a[aria-current] { color: var(--ink-warm); font-weight: 600; }
/* With no script the current segment wears the pill itself, drawn as a
   background. With a script the pill is a real element that travels, and the
   background comes off so the two never draw on top of each other. */
.period:not(.has-pill) a[aria-current] {
  background: var(--window);
  box-shadow: var(--sh-1);
}
/* beui `tabs`, adapted: one indicator that travels to the segment just
   pressed rather than blinking. `--ease-spring` overshoots, which is the
   property the spring in the original was there for. */
.period-pill {
  position: absolute;
  top: 3px;
  left: 0;
  bottom: 3px;
  border-radius: 9px;
  background: var(--window);
  box-shadow: var(--sh-1);
  transition: transform var(--t-glide) var(--ease-spring),
              width var(--t-glide) var(--ease-spring);
}
.period-pill[hidden] { display: none; }

/* --------------------------------------------------------- the hero panel */
/* The one panel in the app with depth, and the design ruleset is why: the
   thing a screen is about has to read as a real, lit object rather than a
   correct rectangle, and every other panel here is deliberately a correct
   rectangle. Three layers and no more — a 0-to-2.8% `--blue` wash falling to
   nothing by two thirds down, a 1px white highlight along the top edge where
   the light would catch it, and a soft ambient shadow under it. The two object
   cards below stay flat, which is what makes this one read as raised.

   12px of radius rather than the app's 8, which is Mercury's card radius and
   the one place in this product that borrows it. Both exceptions are recorded
   in DESIGN.md 1. */
.panel-hero {
  position: relative;
  height: 430px;
  border-radius: 22px;
  overflow: hidden;
  isolation: isolate;
  padding: 0;
  background:
    radial-gradient(58% 54% at 50% 44%, #FFFEFA 0%, rgba(255, 254, 250, 0) 74%),
    radial-gradient(80% 70% at 88% -4%, #FBE6C8 0%, rgba(251, 230, 200, 0) 62%),
    linear-gradient(172deg, #FBF6EC 0%, #F5EBDB 60%, #F0E2CC 100%);
  box-shadow: inset 0 0 0 1px rgba(120, 85, 40, .07);
}
.panel-hero::before {
  content: "";
  position: absolute;
  inset: -25%;
  z-index: -1;
  pointer-events: none;
  background: repeating-linear-gradient(116deg, rgba(255, 255, 255, 0) 0 90px, rgba(255, 251, 242, .95) 90px 150px, rgba(255, 255, 255, 0) 150px 260px);
  filter: blur(20px);
  opacity: 1;
  -webkit-mask-image: radial-gradient(70% 70% at 78% 8%, #000 0%, transparent 80%);
  mask-image: radial-gradient(70% 70% at 78% 8%, #000 0%, transparent 80%);
}
.panel-hero::after {
  content: "";
  position: absolute;
  inset: 0;
  z-index: -1;
  pointer-events: none;
  opacity: .22;
  mix-blend-mode: multiply;
  background-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' width='180' height='180'><filter id='n'><feTurbulence type='fractalNoise' baseFrequency='.85' numOctaves='2' stitchTiles='stitch'/><feColorMatrix values='0 0 0 0 .45  0 0 0 0 .33  0 0 0 0 .2  0 0 0 .55 0'/></filter><rect width='100%' height='100%' filter='url(%23n)'/></svg>");
}
/* The title is for a screen reader; what shows of the header is the
   signature picker, floating in the plate's top right corner. */
.panel-hero > .panel-head {
  position: absolute;
  top: 14px;
  right: 14px;
  z-index: 2;
  min-height: 0;
  margin: 0;
  padding: 0;
}
.panel-hero > .panel-head h2 {
  position: absolute;
  width: 1px;
  height: 1px;
  overflow: hidden;
  clip: rect(0 0 0 0);
  clip-path: inset(50%);
  white-space: nowrap;
}
.hero, .hero-art { min-width: 0; }
.hero-art .well-lit {
  position: absolute;
  inset: 0 0 54px 0;
  display: grid;
  place-items: center;
  background: none;
  box-shadow: none;
  padding: 0;
  overflow: visible;
}
.hero-art .cardhost {
  box-shadow: var(--lit, 0 0 0 1px rgba(90, 60, 20, .035), 0 2px 3px rgba(90, 60, 20, .06), 0 16px 30px -12px rgba(90, 60, 20, .20), 0 64px 110px -34px rgba(110, 70, 25, .42));
  border-radius: calc(12px * var(--zoom-card));
}
/* The artwork's zoom, set on the plate by the width the left column really
   has, so the signature is never wider than the plate holding it. */
.app-home .panel-hero { --zoom-card: .66; }
/* The caption row along the foot of the plate. */
.cap {
  position: absolute;
  left: 0;
  right: 0;
  bottom: 0;
  height: 54px;
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
  padding: 0 16px 0 20px;
  font-size: 13px;
  color: var(--ink-2);
}
.cap-l, .cap-r { display: flex; align-items: center; gap: 8px; min-width: 0; white-space: nowrap; }
.cap-r span { overflow: hidden; text-overflow: ellipsis; }

/* ------------------------------------------------------ the Daybook home */
/* The two columns (DESIGN.md 2.2b Home): the plate, the team, Ask Mark and
   the day's lists on the left; the number, the card and the person in a
   340px column on the right from 1260. One column below that. */
.app-body > .home {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 32px;
  margin-top: 24px;
}
.col { min-width: 0; }
.strip-h .h2, .blk-h .h2 { font: 450 21px/1.2 var(--serif); letter-spacing: -.01em; color: var(--ink-warm); }
.home .lnk { color: var(--blue); font-weight: 600; font-size: 13px; text-decoration: none; }
.composer, .note a, .desk .row > a { text-decoration: none; }
/* the team strip */
.strip { margin-top: 22px; }
.strip-h { display: flex; align-items: baseline; justify-content: space-between; gap: 12px; }
.faces { display: flex; gap: 4px; margin-top: 12px; overflow-x: auto; scrollbar-width: none; }
.fc { flex: none; width: 60px; display: grid; justify-items: center; gap: 6px; font-size: 12.5px; color: var(--mute); padding: 3px 0; border-radius: 12px; transition: background var(--t-fast); }
.fc:hover { background: var(--well); }
.fc .ph-w { position: relative; width: 54px; height: 54px; }
.fc img, .fc-disc { width: 54px; height: 54px; border-radius: 50%; object-fit: cover; }
.fc-disc { display: grid; place-items: center; background: var(--well-2); font-size: 15px; font-weight: 600; color: var(--ink-2); }
.fc .st { position: absolute; right: -1px; bottom: -1px; width: 14px; height: 14px; border-radius: 50%; border: 2.5px solid var(--window); background: var(--faint); }
.fc .st-live { background: var(--live-dot); }
.fc.invited img, .fc.invited .fc-disc { opacity: .55; }
.fc.invited .st { background: var(--window); border: 2.5px dashed var(--faint); }
/* Ask Mark */
.composer { margin-top: 18px; display: flex; align-items: center; gap: 10px; height: 52px; padding: 0 14px 0 12px; border-radius: 15px; background: var(--window); box-shadow: inset 0 0 0 1px var(--line-warm), var(--sh-2); color: var(--faint); font-size: 14.5px; }
.composer:hover { box-shadow: inset 0 0 0 1px #DDD5C6, var(--sh-2); }
.composer > span:last-child { min-width: 0; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; }
.composer .disc { width: 28px; height: 28px; border-radius: 50%; background: var(--blue); display: grid; place-items: center; flex: none; }
.notes { display: flex; gap: 22px; margin-top: 10px; overflow: hidden; }
.note { display: inline-flex; align-items: center; gap: 8px; height: 28px; font-size: 12.5px; color: var(--ink-2); white-space: nowrap; min-width: 0; }
.note .nt { min-width: 0; overflow: hidden; text-overflow: ellipsis; }
.note .stack { flex: none; display: flex; }
.note .stack img, .note .stack .fc-disc { width: 24px; height: 24px; border-radius: 50%; object-fit: cover; font-size: 10px; }
.note a { flex: none; color: var(--blue); font-weight: 600; }
/* the day's lists. Scoped to `.desk`, because the Inbox screen has a bare
   `.row` of its own. */
.desk { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 28px; margin-top: 30px; }
.blk-h { display: flex; align-items: baseline; justify-content: space-between; gap: 12px; }
.desk .rows { list-style: none; margin: 6px 0 0; padding: 0; }
.desk .row { display: grid; grid-template-columns: 44px minmax(0, 1fr); gap: 12px; align-items: center; padding: 10px 8px; margin: 0 -8px; border-radius: 10px; transition: background var(--t-fast); }
.desk .row:hover { background: var(--well); }
.desk .row > a { display: contents; }
.desk .date { display: grid; justify-items: center; line-height: 1; }
.desk .date small { font-size: 11px; color: var(--mute); }
.desk .date b { font: 400 22px/1.05 var(--serif); margin-top: 2px; }
.desk .rt { min-width: 0; }
.desk .rt b { display: block; font-weight: 600; font-size: 13.5px; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; }
.desk .rt span { display: block; color: var(--mute); font-size: 12.5px; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; }
.desk .row.in { grid-template-columns: minmax(0, 1fr) auto; }
.desk .row.in time { font-size: 12px; color: var(--faint); }
.desk .row.in .rt b { font-weight: 500; color: var(--ink-2); }
.desk .row.in .rt b.new { font-weight: 650; color: var(--ink-warm); }
.desk .row.ct { grid-template-columns: minmax(0, 1fr); }
.desk .row-none { color: var(--mute); font-size: 13px; padding: 10px 0; }
/* the number, as a quiet block at the top of the right column */
.metric .figure { font: 300 76px/.9 var(--serif); letter-spacing: -.03em; font-variant-numeric: tabular-nums; color: var(--ink-warm); }

/* The well, with light in it. A signature is the lit focal object this screen
   is built around, so its ground is a soft pool falling to `--light` rather
   than a flat grey box: the artwork sits IN something. Nothing animates and
   nothing is a shadow; it is one radial gradient. */
.well-lit {
  background:
    radial-gradient(120% 92% at 50% 18%, #fff 0%, var(--light) 66%);
}

/* ----------------------------------------------------------- the figures */
/* One number big enough to read from across a desk, and exactly one. The
   dataviz skill puts a hero figure at 48px and up and says there is one per
   view; this is 40 because the app scale's top rung is 20 and 48 on a 14px
   screen is a billboard. 500 rather than 600 for the reason the greeting is:
   Mercury's own figure is light, and a number that heavy reads as an alert.

   Tabular figures, and here the app scale's rule (`marks-and-anatomy.md`
   prefers proportional at display sizes) is not merely tolerated but
   required: this number counts itself up, and proportional digits would make
   it breathe in and out through the twelve hundred milliseconds. */
.figure {
  margin: 2px 0 0;
  font-size: 40px;
  font-weight: 500;
  line-height: 1.02;
  letter-spacing: -.6px;
  font-variant-numeric: tabular-nums;
  color: var(--ink);
}
.figure-sm { font-size: 28px; letter-spacing: -.4px; }
.figure-label {
  margin: 0;
  font-size: 13px;
  line-height: 1.3;
  color: var(--mute);
}
/* Two changes on one line, said as counts. Up is `--good` and down is
   `--muted-light`; down is never `--alert`, because a quiet fortnight is not a
   fault and a dashboard that flags one is a dashboard nobody opens. */
.figure-change {
  display: flex;
  flex-wrap: wrap;
  gap: 4px 16px;
  margin: 8px 0 0;
  font-size: 13px;
  line-height: 1.3;
}
.delta { color: var(--muted-light); white-space: nowrap; }
.delta-up { color: var(--good); }
.figure-since {
  margin: 4px 0 0;
  font-size: 12px;
  line-height: 1.3;
  color: var(--muted-light);
}
/* What the deltas do while a day is under the crosshair. "+129 views vs
   previous 30 days" beside a Tuesday's own count is a sentence about a
   different number, so it goes; `opacity` rather than `hidden` so nothing on
   the panel moves while a pointer is sweeping across it. */
.is-away { opacity: 0; }
[data-aside] { transition: opacity var(--t-base) var(--ease-out); }

/* Three facts under the chart, in Mercury's Bill Pay shape: an 11px label
   over a 14px value, no chart under either. */
.micro {
  display: flex;
  flex-wrap: wrap;
  gap: 10px 24px;
  margin-top: 16px;
  padding-top: 12px;
}
.micro > div { min-width: 0; }
.micro span {
  display: block;
  font-size: 11px;
  font-weight: 600;
  line-height: 1;
  letter-spacing: .06em;
  text-transform: uppercase;
  color: var(--muted-light);
}
.micro strong {
  display: block;
  margin-top: 4px;
  font-size: 14px;
  font-weight: 600;
  line-height: 1.2;
  color: var(--ink);
}

/* ------------------------------------------------------------ the charts */
/* Two marks and no library, plus a row of bars and a meter. DESIGN.md 9 is the
   written version and `~/.claude/skills/dataviz` is where the rules come from;
   what follows is the CSS half. Every magnitude mark is `--blue` and nothing
   else: there is no categorical palette here because no chart in this product
   carries more than one series, and a ramp across nominal categories would
   double-encode a bar's length as its colour. */

/* The wash under the line. `marks-and-anatomy.md` puts an area fill at about a
   tenth of the series hue; this is a gradient from .18 at the line to nothing
   at the floor, which averages just under nine, so the darkest pixel of it is
   where the data is and the bottom of the plot is the panel's own ground.
   The stops take `--blue` from here rather than from a hex in the template. */
.wash-top { stop-color: var(--blue); stop-opacity: .18; }
.wash-foot { stop-color: var(--blue); stop-opacity: 0; }

.chart { margin: 16px 0 0; }
.chart-plot { position: relative; }
.chart-plot:focus-visible {
  outline: 2px solid var(--blue);
  outline-offset: 3px;
  border-radius: 4px;
}
.chart-plot svg { display: block; }
/* The UA stylesheet's `[hidden] { display: none }` does not reach inside an
   SVG, so the crosshair and its marker would be drawn at 0,0 on every chart
   before a pointer had touched one: a blue dot in the corner of the plot,
   including on an empty one, which reads as a data point. */
.chart-plot svg [hidden] { display: none; }
.area-fill { stroke: none; }
.area-line {
  fill: none;
  stroke: var(--blue);
  stroke-width: 1.5;
  stroke-linecap: round;
  stroke-linejoin: round;
  vector-effect: non-scaling-stroke;
}
.area-base { stroke: var(--panel-edge); stroke-width: 1; }
/* The crosshair finds the day. A reader aims at a date, never at a 1.5px
   line, so the pointer's x is snapped to the nearest of them and the whole
   height of the plot is that day's hit target. */
.area-cross {
  stroke: var(--hair);
  stroke-width: 1;
  vector-effect: non-scaling-stroke;
}
/* An 8px marker with a 2px ring in the surface colour, so it stays legible
   where it crosses the line it is sitting on. HTML rather than an SVG circle,
   because the plot is stretched horizontally and a circle in a stretched
   viewBox is an ellipse: `vector-effect` rescues a stroke and nothing rescues
   a radius. Its left is a percentage of the plot and its top is the plot's own
   pixels, which are the SVG's user units on the vertical because the height
   never stretches. */
.area-dot {
  position: absolute;
  width: 8px;
  height: 8px;
  margin: -4px 0 0 -4px;
  border-radius: 50%;
  background: var(--blue);
  box-shadow: 0 0 0 2px var(--white);
  pointer-events: none;
}
/* The day band lives UNDER the plot rather than inside it, so a fixed height
   can never crop it: `anti-patterns.md`'s "container whose fixed height
   excludes the x-axis band". */
.chart-x {
  display: flex;
  justify-content: space-between;
  margin: 8px 0 0;
  font-size: 11px;
  color: var(--muted-light);
}
.chart-x span:nth-child(2) { transform: translateX(-50%); }
/* Never a blank panel and never a sample line. The baseline draws and the plot
   area says what is missing. */
.chart-none {
  position: absolute;
  inset: 0;
  display: flex;
  align-items: center;
  justify-content: center;
  font-size: 13px;
  color: var(--muted-light);
}
.chart-none-flat {
  position: static;
  display: block;
  margin: 0;
  padding: 14px 0;
  text-align: center;
}
/* Right of the plot it belongs to, at the app's own text-control size: rule 5
   says a control under /app is 32px at 13px, and quietening this one to 12
   would be the amendment's own scale broken for tidiness. */
.chart-more { margin-top: 4px; text-align: right; }
.chart-more > summary { list-style: none; cursor: pointer; display: inline-flex; }
.chart-more > summary::-webkit-details-marker { display: none; }
.chart-table { width: 100%; margin-top: 8px; border-collapse: collapse; }
.chart-table th {
  padding: 4px 8px 4px 0;
  text-align: left;
  font-size: 11px;
  font-weight: 600;
  letter-spacing: .06em;
  text-transform: uppercase;
  color: var(--muted-light);
  border-bottom: 1px solid var(--panel-edge);
}
.chart-table td {
  padding: 4px 8px 4px 0;
  font-size: 12px;
  color: var(--ink);
  border-bottom: 1px solid var(--panel-edge);
}
.chart-table td:last-child, .chart-table th:last-child { text-align: right; }

/* The same chart small, beside the card's own count: 48px, no baseline, no
   day labels, no crosshair. Every day of it is in the hero's table. */
.spark { display: block; width: 100%; margin-top: 12px; overflow: visible; }

/* One measure across categories. The name carries the identity, the bar
   carries the comparison and the numbers carry the value, so there is no table
   view here: the row already is one. The name and the value share the first
   line and the bar takes the whole of the second, because three of these stand
   side by side inside one panel and a name, a track and a value on ONE line
   leaves the track about fifty pixels of range. */
.bars { list-style: none; margin: 0; padding: 0; display: grid; gap: 10px; }
.bars li {
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  align-items: baseline;
  column-gap: 10px;
  row-gap: 4px;
}
.bar-name {
  font-size: 13px;
  color: var(--ink);
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
.bar-track {
  grid-column: 1 / -1;
  height: 6px;
  border-radius: 0 3px 3px 0;
  background: var(--light);
}
/* Square at the baseline, rounded at the data end, one hue for every bar.
   `min-width` so a category with one event is a mark rather than nothing. */
.bar-fill {
  display: block;
  height: 100%;
  min-width: 3px;
  border-radius: 0 3px 3px 0;
  background: var(--blue);
}
.bars li:hover .bar-fill { background: var(--blue-hover); }
.bar-value { font-size: 13px; color: var(--ink); white-space: nowrap; }
.bar-value i { font-style: normal; margin-left: 6px; color: var(--muted-light); }

.groups { display: grid; grid-template-columns: minmax(0, 1fr); gap: 20px; }
.groups > * { min-width: 0; }
.chart + .groups, .bars + .group { margin-top: 20px; }

/* ------------------------------------------------------------- the meter */
/* Mercury's Credit Card row: a 4px bar and one line under it saying what its
   two ends are. One measure of a whole, so the track is a lighter step of the
   fill's own hue rather than a second colour — `marks-and-anatomy.md`'s meter
   rule — and the legend is what a sighted reader gets, because 4px of bar
   carries no text of its own. */
.meter-block { margin-top: 16px; }
.meter {
  display: block;
  width: 100%;
  height: 4px;
  border-radius: 999px;
  background: rgba(0, 113, 227, .14);
  overflow: hidden;
}
.meter span { display: block; height: 100%; background: var(--blue); }
.meter-say {
  display: block;
  margin-top: 8px;
  font-size: 12px;
  color: var(--muted-light);
}

/* ------------------------------------------------------- the object cards */
/* Two smaller cards under the hero, seven twelfths against five. Flat, both of
   them, which is what leaves the hero the only lit thing on the screen. */
.objects {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  align-items: start;
  gap: 30px;
  margin-top: 30px;
}
.objects > .panel + .panel { margin-top: 0; }
.object { display: grid; grid-template-columns: auto minmax(0, 1fr); align-items: start; gap: 16px; }
.object-art .well-lit { background: none; }
.object-art { flex: none; }
.object-say { flex: 1 1 190px; min-width: 0; }
/* The row a card ends on: what state it is in on the left, what to do about it
   on the right. */
.object-foot {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 8px 12px;
  margin-top: 16px;
  padding-top: 12px;
  border-top: 1px solid var(--panel-edge);
  font-size: 13px;
}
.object-do { flex: none; display: flex; align-items: center; gap: 8px; }

/* The card at 132px, in its own frame, tilting under a pointer. Two classes
   rather than one, because `.livecard` is re-set by two later media queries
   for the Card screen's own preview and a single class loses to them. */
.livecard.livecard-mini { --live: .3158; }

/* beui `tilt-card`, adapted. The rotation is a CSS transition rather than a
   spring: 200ms of `--ease-spring` under a stream of pointermoves is a follow
   with lag and overshoot, which is the property the spring was there for, at
   no bytes. The glare has no transition on its POSITION at all, so the light
   leads and the object follows, which is the original's own split. */
.tilt { position: relative; display: block; overflow: hidden; }
.tilt-face {
  display: block;
  transform-style: preserve-3d;
  transition: transform 200ms var(--ease-spring);
}
/* `--foreground` in the original; here it is the ink, at 12% rather than 15,
   because this is a 132px preview on a working screen and not a hero on a
   marketing page. Off until a pointer arrives — beui leaves it painted always,
   which on a dashboard is a permanent highlight on an idle panel, and
   DESIGN.md 4 does not allow motion or light that says nothing. Its POSITION
   is deliberately not reset on leave, which is the original's own choice: the
   light stays where it was. */
.tilt-glare {
  position: absolute;
  inset: 0;
  pointer-events: none;
  opacity: 0;
  background: radial-gradient(circle at var(--gx, 50%) var(--gy, 50%),
                              var(--ink), transparent 50%);
  transition: opacity var(--t-base) var(--ease-out);
}
.can-tilt:hover .tilt-glare { opacity: .12; }

/* ------------------------------------------------------------ the person */
/* The identity as the CARD draws it, because that is what a stranger meets and
   this is a brand dashboard. A meter on its own would be a score; a face, a
   name, a title, a company and the colour is the brand, with the score under
   it. */
.who { display: flex; align-items: center; gap: 12px; }
.who-face {
  flex: none;
  width: 48px;
  height: 48px;
  border-radius: 50%;
  object-fit: cover;
}
.who-disc {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  font-size: 15px;
  font-weight: 600;
  letter-spacing: .01em;
  color: #fff;
}
.who-say { min-width: 0; }
.who-name {
  margin: 0;
  font-size: 16px;
  font-weight: 600;
  line-height: 1.25;
  letter-spacing: -.1px;
  color: var(--ink);
  overflow-wrap: anywhere;
}
.who-role {
  display: flex;
  align-items: center;
  gap: 8px;
  margin: 2px 0 0;
  font-size: 13px;
  line-height: 1.3;
  color: var(--muted-light);
  min-width: 0;
}
/* The customer's own colour, said once, as a 12px disc after the company. It
   is the only place the accent touches this screen: it is the artwork's
   colour, not the tool's, which is DESIGN.md 1's rule about `--accent`. */
.who-dot { flex: none; width: 12px; height: 12px; border-radius: 50%; }

/* -------------------------------------------------------------- the folds */
/* beui `bouncy-accordion`'s measured-height morph on a real `<details>`, so
   every number inside is reachable with no script at all and the morph is the
   enhancement. The summary is the 12px text control, right-aligned at the
   panel's edge. */
.fold { margin-top: 16px; text-align: right; }
.fold-body { text-align: left; }
/* Straight under the row a card closes on, so the two read as one foot rather
   than as two afterthoughts. */
.object-foot + .fold { margin-top: 2px; }
/* Right-aligned by the block rather than floated. A float leaves the
   `<details>` itself zero pixels tall, which puts the summary outside its own
   panel's height: the shot pass measures the air under a panel's last child
   and read 49px of it. */
.fold > summary {
  list-style: none;
  cursor: pointer;
  display: inline-flex;
}
.fold > summary::-webkit-details-marker { display: none; }
.fold-body { padding-top: 12px; }
.can-fold .fold-body { overflow: hidden; }
.fold[open] > summary { margin-bottom: 4px; }

/* ----------------------------------------------------------- the entrance */
/* The greeting first, then the hero, then the two object cards: 8px of rise
   and a fade, 320ms each, 60ms apart, on `--ease-land`. One movement in four
   parts rather than four movements, which is what the stagger buys.

   `from` only, with `backwards` fill. The end state is the element's own
   computed style, so `animation: none` under reduced motion leaves every box
   exactly where it belongs rather than needing a second set of rules to undo a
   `to`. Nothing moves after this except what a pointer asks for. */
@keyframes land {
  from { opacity: 0; transform: translateY(8px); }
}
@keyframes rise {
  from { transform: translateY(8px); }
}
@media (prefers-reduced-motion: no-preference) {
  .app-home .app-head,
  .app-home .panel-hero,
  .app-home .strip,
  .app-home .desk,
  .app-home .metric,
  .app-home .objects > .panel {
    animation: land 320ms var(--ease-land) backwards;
  }
  /* The greeting RISES but does not fade, and that is a measurement rather
     than a taste decision. At 24px over two lines on a phone it is the
     largest contentful paint on this screen, and Chrome does not count a
     fully transparent element as painted: the fade put the LCP 320ms after
     the first paint of the same words and cost a point of Lighthouse
     performance on mobile. A transform does not affect paint timing, so the
     rise stays and the fade goes. Measured: 1.8s and 99 with the fade,
     1.2s and 100 without it. The contract's instruction was to fix the cause
     rather than cut the motion, and the cause was the opacity on one
     element. */
  .app-home .app-head {
    animation-name: rise;
    animation-delay: 0ms;
  }
  .app-home .panel-hero { animation-delay: 60ms; }
  .app-home .strip { animation-delay: 120ms; }
  .app-home .desk { animation-delay: 180ms; }
  .app-home .metric { animation-delay: 120ms; }
  .app-home .objects > .panel:first-child { animation-delay: 180ms; }
  .app-home .objects > .panel:last-child { animation-delay: 240ms; }
}

/* --------------------------------------------------------- the breakpoints */
/* The hero's left column reaches 325px of room for the signature at 1024, 417
   at 1100 and its real 508 at 1260, measured against
   `(main - 48) * .583 - 40 - 24`, which is the column minus the hero panel's
   20px padding either side and the well's 12. */
@media (min-width: 700px) {
  .groups { grid-template-columns: repeat(3, minmax(0, 1fr)); }
  .groups-two { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}
@media (min-width: 1024px) { .app-home .panel-hero { --zoom-card: .82; } }
@media (min-width: 1100px) { .app-home .panel-hero { --zoom-card: .95; } }
@media (min-width: 1260px) {
  .app-home .panel-hero { --zoom-card: 1.1; }
  .app-body > .home { grid-template-columns: minmax(0, 1fr) 340px; }
}
@media (min-width: 1440px) { .app-home .panel-hero { --zoom-card: 1.28; } }
/* A phone: one column, the plate at 262, the strip scrolling, and no Ask
   Mark bar or notices because the top bar carries the Mark disc. */
@media (max-width: 1023px) {
  .panel-hero { height: 262px; border-radius: 18px; }
  .hero-art .well-lit { inset: 0 0 46px 0; }
  .cap { height: 46px; }
  .composer, .notes { display: none; }
  .desk { grid-template-columns: minmax(0, 1fr); gap: 24px; }
  .metric .figure { font-size: 56px; }
}

/* ------------------------------------------------- the install steps */
/* Four client names as a strip of 32px tabs and a list of numbered steps
   under whichever one is pressed. No prose intro over it: the legend is the
   question and the tab is the answer. */
.app-main .clients { margin-top: 0; }
.app-main .clients legend {
  font-size: 12px;
  font-weight: 500;
  color: var(--muted-light);
  margin-bottom: 10px;
}
.app-main .client-tabs { gap: 6px; margin-bottom: 16px; }
.app-main .client-tabs label {
  height: 32px;
  display: inline-flex;
  align-items: center;
  padding: 0 12px;
  border-radius: 6px;
  border-color: var(--hair);
  font-size: 13px;
  font-weight: 500;
}
#cl-gmail:checked   ~ .client-tabs label[for="cl-gmail"],
#cl-outlook:checked ~ .client-tabs label[for="cl-outlook"],
#cl-apple:checked   ~ .client-tabs label[for="cl-apple"],
#cl-zoho:checked    ~ .client-tabs label[for="cl-zoho"] {
  background: var(--blue);
  border-color: var(--blue);
  color: #fff;
}
.app-main .howto { margin-top: 0; }
.app-main .howto li { font-size: 13px; line-height: 1.5; }
.app-main .howto li + li { margin-top: 6px; }
.app-main .client-panel h3 {
  font-size: 12px;
  font-weight: 600;
  letter-spacing: .06em;
  text-transform: uppercase;
  color: var(--muted-light);
  margin-bottom: 8px;
}

/* ----------------------------------------------------- the connect row */
/* One row above the four client tabs, and it is the same species as a
   key/value row rather than a panel of its own: a mark, what it does, and the
   control. The hairline under it is the rule that separates it from the tab
   strip, which is the one border amendment 2 rule 2 allows inside a panel —
   the same one `.lines` draws between two facts.
   Nothing here is a new token. 18px mark, 13px/600 name, the 12px `.rule`
   line, and 32px controls: the app scale, on a row Google's own mark happens
   to sit in. */
.connect {
  display: flex;
  align-items: center;
  flex-wrap: wrap;
  gap: 10px 12px;
  padding-bottom: 16px;
  margin-bottom: 16px;
  border-bottom: 1px solid var(--panel-edge);
}
/* Capped to the name rather than centred on the block. The say column is two
   lines and the row can grow to three, so a centred mark drifts down beside
   the rule line instead of reading as the row's own initial. */
.connect-mark {
  flex: none;
  display: block;
  width: 18px;
  height: 18px;
  align-self: flex-start;
  margin-top: 1px;
}
.connect-mark svg { display: block; width: 18px; height: 18px; }
.connect-say { flex: 1 1 240px; min-width: 0; }
.connect-name {
  display: block;
  font-size: 13px;
  font-weight: 600;
  line-height: 1.3;
}
/* 4px rather than the rule's own 12: this line is the name's second line,
   not a note under a block. */
.connect-say .rule { margin-top: 4px; }
.connect-was {
  display: flex;
  align-items: center;
  flex-wrap: wrap;
  gap: 4px;
  margin-top: 4px;
  font-size: 12px;
  color: var(--muted-light);
}
.connect-do {
  flex: none;
  display: flex;
  align-items: center;
  flex-wrap: wrap;
  gap: 8px;
}
.connect-form { display: flex; align-items: center; gap: 8px; }
.connect-alias {
  height: 32px;
  max-width: 220px;
  padding: 0 8px;
  border: 1px solid var(--hair);
  border-radius: 6px;
  background: var(--white);
  color: var(--ink);
  font: inherit;
  font-size: 13px;
}
.connect-alias:focus {
  outline: none;
  border-color: var(--blue);
  box-shadow: 0 0 0 3px rgba(0, 113, 227, .18);
}
/* The one thing on the row that takes a line of its own: the error, and the
   warning that stands until Google's review finishes. */
.connect-wide { flex: 1 0 100%; margin-top: 0; }

/* --------------------------------------------------- what is left over */
/* Everything platform.css draws that an app screen still uses, brought to
   this scale in one place rather than fought with inline styles. */
.app-main .sub { font-size: 13px; line-height: 1.45; }
.app-main .hint { font-size: 12px; line-height: 1.4; margin-top: 8px; }
.app-main .copied { margin-top: 0; font-size: 12px; min-height: 0; }
.app-main .kv { margin-top: 8px; font-size: 12px; }
.app-main .kv code { font-size: 12px; }
.app-main .micro { font-size: 12px; }
.app-main code { font-size: 12px; overflow-wrap: anywhere; }
.app-main .cardhost { overflow: visible; }
.app-main .choices { gap: 8px; }
.app-main .choices .choice {
  border-radius: 6px;
  border-color: var(--panel-edge);
  padding: 10px 12px;
}
.app-main .choices .choice-body strong { font-size: 13px; font-weight: 500; }
.app-main .choices .choice-body span { font-size: 12px; }

/* --------------------------------------------------------- the grids */
/* Panels side by side once there is room. `align-items: start` so two panels
   of different heights are two panels of different heights, rather than the
   short one being stretched to the tall one and ending in a field of white. */
.card-cols, .form-cols, .split {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  align-items: start;
  gap: 16px;
}
.split > * { min-width: 0; }
/* A column of panels inside one cell of a grid.

   `min-width: 0`, and it is the same silent failure `minmax(0, 1fr)` closes on
   the track: zeroing the TRACK's minimum does nothing while the ITEM in it
   still has `min-width: auto`, so a panel whose content cannot shrink grows
   out of its cell and paints over the column beside it. The Brand panel found
   it — a row of two swatches and a field with a button after it are both wider
   than four twelfths of 1240 at their min-content — and the page does not
   scroll sideways when it happens, so nothing else catches it. */
.stack-col { display: grid; align-items: start; gap: 16px; min-width: 0; }
.form-cols > *, .card-cols > *, .stack-col > * { min-width: 0; }

/* ------------------------------------------------ the two-panel screens */
/* Amendment 3 rules 7, 8 and 10, and one class rather than three: Billing,
   Settings and a signature's own screen were each a single column of short
   panels down the middle of a 1240px field, which is the whole of "the main
   body of each space is also very open and not optimal".

   Seven against five is the split Home already uses for its two object
   cards, so the app has one proportion rather than four. The signature's
   screen inverts it, because what is on its left is a 508px object rather
   than a table.

   The seven-five pair splits at 1024, where the rail arrives and there is a
   column to divide. The five-seven pair waits for 1280: at 1024 its left is
   308px wide and the signature inside it would be drawn at half size, which
   is a worse answer than one column. */
@media (min-width: 1024px) {
  .split-75 { grid-template-columns: minmax(0, 7fr) minmax(0, 5fr); }
  /* The bare split is the editors' (a booking, a service, an action), and
     it divides seven to five as their comments say. */
  .split:not(.split-75):not(.split-57) {
    grid-template-columns: minmax(0, 7fr) minmax(0, 5fr);
    gap: 32px;
  }
}
@media (min-width: 1280px) {
  .split-57 { grid-template-columns: minmax(0, 5fr) minmax(0, 7fr); }
  /* The signature is the subject of its own screen, so it stays on it while
     the install steps beside it scroll. */
  .split-57 > .stack-col:first-child { position: sticky; top: 16px; }
  /* And its own rung of the card ladder, because five twelfths of the column
     is not what `.app-main` sized the ladder against. The room is the column
     minus the 16px gap, times 5/12, minus the panel's two 16s and the well's
     two 12s: 347 at 1280, 414 at 1440, 481 from 1600. The card is 508, so the
     rungs are the largest of .53/.64/.8/.9 that fits each of those. */
  .split-57 > .stack-col:first-child { --zoom-card: .64; }
}
@media (min-width: 1440px) {
  .split-57 > .stack-col:first-child { --zoom-card: .8; }
}
@media (min-width: 1600px) {
  .split-57 > .stack-col:first-child { --zoom-card: .9; }
}

/* A switch standing between two key/value tables in one panel, which is what
   Settings' Account panel is: the address, then the one thing on this screen
   that changes something, then the way out. It takes the rows' own hairline
   above and below, so the three blocks read as one table rather than as three
   things that happen to be stacked. */
.app-main .switch-inline { border-top: 1px solid var(--line-soft); }
.lines-tail > div:first-child { border-top: 1px solid var(--panel-edge); }
/* One panel after another: the hero, the two objects, and whatever follows. */
.app-body > * + * { margin-top: 16px; }

/* -------------------------------------------------------- the tab bar */
/* Below 1024 the rail becomes five tabs across the bottom of the window,
   which is where a thumb is. Four destinations and More, and More is a real
   <details> so it opens with no script at all. 56px stays: the rail's rows
   are 30 because a pointer is exact and a thumb is not, and 44 is the floor
   for a target. The labels are 12px, which is the rail's own micro rung. */
.tabs {
  position: fixed;
  left: 0;
  right: 0;
  bottom: 0;
  z-index: 18;
  display: grid;
  grid-template-columns: repeat(5, 1fr);
  height: calc(66px + env(safe-area-inset-bottom));
  padding: 0 4px calc(6px + env(safe-area-inset-bottom));
  background: rgba(255, 253, 250, .94);
  backdrop-filter: blur(14px);
  -webkit-backdrop-filter: blur(14px);
  border-top: 1px solid var(--line-soft);
}
.tab {
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 3px;
  min-height: 44px;
  padding: 0 4px;
  font-size: 11px;
  font-weight: 500;
  line-height: 1.2;
  color: var(--mute);
  text-decoration: none;
  transition: color var(--t-base) var(--ease-out),
              background var(--t-base) var(--ease-out),
              transform var(--t-fast) var(--ease-out);
}
.tab:active { transform: scale(.97); }
.tab[aria-current] { color: var(--blue); }
.tab .nav-glyph, .tab .nav-glyph svg { width: 21px; height: 21px; }
.tab .nav-glyph { color: inherit; }

/* More, and what is behind it. The panel opens upward off the tab, which is
   the only direction there is from the bottom of a window. */
.tab-more { position: relative; }
.tab-more > summary { list-style: none; cursor: pointer; }
.tab-more > summary::-webkit-details-marker { display: none; }
.tab-more-body {
  position: absolute;
  right: 8px;
  bottom: calc(100% + 8px);
  min-width: 180px;
  background: var(--window);
  border: 0;
  border-radius: 14px;
  padding: 6px;
  box-shadow: var(--sh-2);
}
.tab-more-body a {
  display: flex;
  align-items: center;
  gap: 10px;
  min-height: 40px;
  padding: 8px 12px;
  border-radius: 6px;
  font-size: 13px;
  font-weight: 500;
  color: var(--ink);
  text-decoration: none;
  transition: background var(--t-base) var(--ease-out);
}
.tab-more-body a:hover { background: var(--light); }
.tab-more-body a[aria-current] { background: var(--light); font-weight: 600; }

/* ---------------------------------------------------------- the top bar */
/* Below 1024 only (DESIGN.md 2.2b): the workspace chip and the Mark disc,
   sticky over the window, in place of the rail. */
.topbar {
  position: sticky;
  top: 0;
  z-index: 20;
  height: 58px;
  display: flex;
  align-items: center;
  justify-content: space-between;
  padding: 0 12px 0 14px;
  background: rgba(255, 253, 250, .9);
  backdrop-filter: blur(14px);
  -webkit-backdrop-filter: blur(14px);
  border-bottom: 1px solid var(--line-soft);
}
.topbar .side-space {
  height: 44px;
  padding: 0 14px 0 10px;
  border-radius: 999px;
  background: var(--well);
  box-shadow: none;
}
.mark-go {
  display: grid;
  place-items: center;
  width: 44px;
  height: 44px;
  border-radius: 50%;
}
.topbar .mark-disc {
  width: 34px;
  height: 34px;
  border-radius: 50%;
  background: var(--blue);
  display: grid;
  place-items: center;
}
.topbar .mark-disc svg { display: block; width: 64%; height: 64%; }

/* --------------------------------------------------------- breakpoints */
/* A signature is 508px wide and the room a WELL leaves is the window minus
   two gutters, two panel paddings and two well paddings: `viewport - 88` at
   the phone's 16px gutters and `viewport - 104` from 700, where they go to
   24. The rungs are the widths at which 269, 325, 417 and 508 next fit. */
.app-main { --zoom-card: .53; }
@media (min-width: 420px) { .app-main { --zoom-card: .64; } }
@media (min-width: 512px) { .app-main { --zoom-card: .82; } }
@media (min-width: 600px) { .app-main { --zoom-card: 1; } }
@media (min-width: 440px) { .livecard { --live: .8947; } }

@media (min-width: 700px) {
  /* Six columns of facts fit; below this the plan, the date and the chevron
     fold into one muted line under the name. */
  .dtable .c-sub { display: none; }

  /* The card screen splits here rather than at the rail's 1024, because the
     thing that must not happen on this screen is a phone-shaped preview alone
     in a 688px panel. 308 is 276 of card plus the panel's two 16s, and it is
     also what leaves the controls column the 636px four theme tiles and their
     gaps need at 1280 - until amendment 3 took 28 of those pixels for the
     rail. See the 1280-to-1359 band below, where the two gaps close by four
     rather than the card giving ground: the screen's own floor is 270 and
     .726 is 274, so there is nothing to give. */
  .card-cols { grid-template-columns: 308px minmax(0, 1fr); }
  .card-cols .livecard { --live: .726; }
}
@media (max-width: 699px) {
  .dtable .c-plan, .dtable .c-when, .dtable .c-state, .dtable .c-go,
  .dtable .c-num { display: none; }
  /* The whole header row rather than each cell in it: a `thead` whose every
     `th` is hidden is still a row, so it still draws its own bottom hairline
     over the first signature in the list. */
  .dtable thead { display: none; }
  .dtable td { padding: 8px 12px; }
  .dtable .c-shot { padding-right: 0; }
}
/* The desk keeps its headers on a phone: its columns do not step aside, so
   a header row is what says which is which. After the block above, so it
   wins by order as well as by weight. */
.app-admin .dtable thead { display: table-header-group; }

/* Billing and Settings are one panel each now, so nothing splits here any
   more; what does split at 860 is the signature screen's two columns, whose
   left holds a 508px object. */
@media (min-width: 860px) {
  .form-cols { grid-template-columns: minmax(0, 4fr) minmax(0, 8fr); }
}

/* Eight columns need a rail's worth of width to sit in. Measured at 768: the
   header labels alone - an 11px tracked CLICKS 30D is 96px with its padding -
   put the table 29px past the viewport and scrolled the document sideways.
   The price is what gives way, because it is the one fact on this list that
   is on three other screens: Billing's own table, the signature's facts row,
   and the rail's Billing row since amendment 3. Views and Clicks are the
   reason the list was opened. */
@media (max-width: 1023px) {
  .dtable .c-plan { display: none; }
  /* The head's control drops under the title rather than pushing the page
     sideways (Bookings' four views do not fit beside it on a phone). */
  .app-head-row { flex-wrap: wrap; row-gap: 12px; }
  .app-head h1 { font-size: 31px; }
  .app-head h1.h1-big { font-size: 36px; }
  .btn, .btn-primary { height: 44px; }
}

/* The phone and tablet shell, amended 2026-10-09: the window is at least the
   screen and clears the tab bar by 28px plus the home indicator, and the top
   bar carries a flat workspace name and one labelled button. */
@media (max-width: 1023px) {
  /* The window fills the screen: no linen under a short page. */
  .app-grid { align-items: stretch; min-height: calc(100dvh - 58px); }
  .app-main { min-height: 100%; padding-bottom: calc(66px + 28px + env(safe-area-inset-bottom)); }
  /* The chip is flat; Ask Mark is a labelled capsule, so it reads as a
     button rather than an avatar. The label is decoration: the link keeps
     its aria-label. */
  .topbar { height: 52px; padding: 0 12px 0 16px; border-bottom-color: var(--line-soft); }
  .topbar .side-space { height: 44px; padding: 0 8px 0 0; background: none; box-shadow: none; gap: 8px; }
  .topbar .side-space-face, .topbar .side-disc { width: 26px; height: 26px; }
  .topbar .side-space-name { font-size: 15px; max-width: 62vw; }
  .topbar .mark-go { width: auto; height: 36px; padding: 0 12px 0 5px; grid-auto-flow: column; gap: 7px; border-radius: 999px; background: var(--well-2); color: var(--ink-warm); text-decoration: none; }
  .topbar .mark-go::after { content: "Ask Mark"; font: 600 13px/1 var(--sans-ui); letter-spacing: -.01em; }
  .topbar .mark-disc { width: 26px; height: 26px; }
  /* Panel heads: the say-line wraps under the heading; the heading never breaks. */
  .panel-head { flex-wrap: wrap; row-gap: 2px; }
  .panel-head h2 { flex: none; white-space: nowrap; }
  .panel-head-say { white-space: normal; overflow: visible; text-overflow: clip; }
}

/* The phone gutter is 16, as on iOS; every bleed below cancels it. */
@media (max-width: 699px) {
  .app-main { padding-left: 16px; padding-right: 16px; padding-top: 14px; }
}

/* The head on a phone: one headline band, then one row of actions. It sits
   after the 1023 block above because that block's 31/36px headline sizes
   would otherwise win the tie. */
@media (max-width: 699px) {
  .app-head { margin-bottom: 10px; padding-bottom: 6px; }
  .app-head h1 { font-size: 29px; }
  .app-head h1.h1-big { font-size: 32px; letter-spacing: -.028em; }
  .app-head .kick { font-size: 12.5px; margin-bottom: 8px; }
  .app-head .sub { margin-top: 5px; font-size: 14px; }
  /* Headings inside the page, one step under the headline. */
  .panel-head h2, .strip-h .h2, .blk-h .h2 { font-size: 19px; }
  /* Type and density: rows and quiet lines one notch tighter. */
  .lines > div { padding-top: 9px; padding-bottom: 9px; font-size: 13px; }
  .rule { font-size: 13.5px; }
  .panel-head-say { font-size: 12px; }
  .c-sub { font-size: 11.5px; }
  /* The bar names the workspace; the date line is Home's alone. */
  body.app:not(.app-home) .app-head .kick { display: none; }
  /* A segmented control in the head goes full width, equal segments. */
  .app-head-do:has(> .period) { flex: 1 1 100%; }
  .app-head-do > .period { display: flex; width: 100%; }
  .app-head-do > .period a { flex: 1 1 0; justify-content: center; padding: 0; height: 34px; }
  /* Home: the greeting, the period right-aligned under it (beside the sub
     line it would squeeze the greeting onto two lines), then one row of
     chips you swipe. The fade sits on the scroller, so it stays at the edge. */
  .app-home .app-head-tall { display: grid; grid-template-columns: minmax(0, 1fr); align-items: end; }
  .app-home .app-head-row { display: contents; }
  .app-home .app-head-say { grid-column: 1; grid-row: 1; order: unset; }
  .app-home .app-head-do { grid-column: 1; grid-row: 2; justify-self: end; order: unset; margin: 0 0 1px; width: auto; align-self: end; }
  .app-home .app-head-do > .period { display: inline-flex; width: auto; }
  .app-home .app-head-do > .period a { flex: none; height: 30px; padding: 0 10px; font-size: 12.5px; }
  .app-home .chips-do { grid-column: 1 / -1; grid-row: 3; order: unset; margin: 14px -16px 0; padding: 0 40px 0 16px; flex-wrap: nowrap; overflow-x: auto; scrollbar-width: none; scroll-snap-type: x proximity; -webkit-overflow-scrolling: touch; mask-image: linear-gradient(90deg, #000 0, #000 calc(100% - 28px), transparent); -webkit-mask-image: linear-gradient(90deg, #000 0, #000 calc(100% - 28px), transparent); }
  .app-home .chips-do::-webkit-scrollbar { display: none; }
  .app-home .chips-do .chip { flex: none; height: 34px; padding: 0 13px; scroll-snap-align: start; }
}

/* The shell proper. The rail appears, the tabs go away, and the bottom
   padding that was clearing them goes with it. */
@media (min-width: 1024px) {
  .app-grid { grid-template-columns: 248px minmax(0, 1fr); min-height: 100vh; }
  .side { display: block; }
  .tabs { display: none; }
  .app-main {
    width: auto;
    margin: 10px 10px 10px 0;
    padding: 30px 40px 40px;
    border-radius: 18px;
    box-shadow: 0 0 0 1px rgba(90,60,20,.06), 0 1px 2px rgba(64,44,18,.05), 0 18px 50px -24px rgba(64,44,18,.18);
    min-height: calc(100vh - 20px);
  }
  .topbar { display: none; }

  /* The card is the subject of its screen, so it stays on it while the
     controls beside it scroll. */
  .card-preview { position: sticky; top: 16px; }
}

/* The one place in the app that had no 28 pixels to give. The theme picker is
   four 150px tiles and three 12px gaps, which is 636, and at 1280 the wider
   rail leaves the panel 626. So both gaps close by four at this one band -
   the preview column's and the tiles' - and the picker is back at four across
   with six pixels to spare. From 1360 there is room for twelve again, and
   from 1600 there is room for a fifth tile. Nothing about the card itself
   moves: it stays at .726, which is the 274px the screen's own floor asks
   for. */
@media (min-width: 1280px) and (max-width: 1359px) {
  .card-cols { gap: 12px; }
  .app-main .themes { gap: 8px; }
}

/* Above 1440 the content column has stopped growing at 1240, so the room the
   rail was taking comes back to the preview. */
@media (min-width: 1440px) {
  .card-cols { grid-template-columns: 372px minmax(0, 1fr); }
  .card-cols .livecard { --live: .8947; }
}
/* Amendment 3 rule 6, and it is the second half of the centring rule the
   branch opens with. Centring a 1240px column stopped the dashboard sitting
   in the top-left corner of a 1920px window; what it did not do is USE the
   window, and Ramon's sentence was about the emptiness rather than about the
   position: "the main body of each space is also very open and not optimal."
   1240 is right up to about 1600 - it is Linear's and Vercel's own content
   width - and past that it is a column with 340px of nothing either side of
   it. One step, to 1400, and no further: a 7/5 grid at 1400 puts the right
   panel at 570, and a key/value row much wider than that is a row whose key
   and value are no longer read as a pair. */
@media (min-width: 1600px) {
  .app-main { --col-max: 1400px; }
  .card-cols { grid-template-columns: 412px minmax(0, 1fr); }
  .card-cols .livecard { --live: 1; }
}

@media (prefers-reduced-motion: reduce) {
  /* platform.css already drops every transition. What is left is the press
     feedback, which is a transform rather than a transition and would
     otherwise still jump under a finger. */
  .side-space { transition: none; }
  .nav-item:active, .tab:active, .switch:active,
  .btn:active, .btn-primary:active, .btn-text:active { transform: none; }
  .app-main .themes label:hover .shot { transform: none; }
}

/* ------------------------------------------------------------- the brand */
/* The Brand panel on Profile, and the proposal screen the Import row leads
   to. Nothing here is a new token: 32px controls at 6px, the 40px switch
   track already on the card's own switches, the `--light` well every preview
   object in this app sits on, and the same 12px muted for anything that is
   not a value. */

/* A colour that may be absent. The switch goes at the head of the swatch row
   rather than in a 40px row of its own, because "second colour" is one
   decision and a toggle stacked above the thing it governs reads as two. It
   is the same 36 x 20 track the card's switches use, drawn on the same real
   checkbox, so it saves with no script and the whole panel still works with
   scripting off. */
.app-main input.use {
  appearance: none;
  -webkit-appearance: none;
  flex: none;
  position: relative;
  width: 36px;
  height: 20px;
  margin: 0;
  padding: 0;
  border: 0;
  border-radius: 999px;
  background: var(--hair);
  cursor: pointer;
  transition: background var(--t-base) var(--ease-out);
}
.app-main input.use::after {
  content: "";
  position: absolute;
  top: 2px;
  left: 2px;
  width: 16px;
  height: 16px;
  border-radius: 50%;
  background: #fff;
  box-shadow: 0 1px 2px rgba(0, 0, 0, .28);
  transition: transform var(--t-base) var(--ease-out);
}
.app-main input.use:checked { background: var(--blue); }
.app-main input.use:checked::after { transform: translateX(16px); }
/* Off, the hex beside it says None rather than a colour nobody is wearing.
   The server renders that word too, so the state a customer reads is the
   state that saves whether or not the script ran. */
.app-main .swatch input.use:not(:checked) ~ input[type="color"] { opacity: .45; }

/* The mark, in the Photo panel's own well. `object-fit: contain` because a
   logo is a wide thing in a square box and cropping one is losing it. */
.app-main .mark-shot {
  border: 0;
  background: var(--light);
  object-fit: contain;
  padding: 6px;
}
.app-main .mark-none { display: block; }

/* Two colour rows side by side is the card's ink and its surface, which are a
   pair and read as one decision. Two 32px controls and a hex in half a column
   is tight, so the hex gives up its fixed 96 and takes what is left. */
.app-main .row2 .swatch { gap: 8px; }
.app-main .row2 .swatch input[type="text"] { flex: 1 1 60px; width: auto; }

/* A field with its own verb beside it: the address to read, and Import. Not
   two rows, because pressing Import is what the address is for. */
.app-main .pairline { display: flex; align-items: center; gap: 8px; }
.app-main .pairline input[type="text"] { flex: 1 1 auto; min-width: 0; }
.app-main .pairline .btn { flex: none; }

/* ------------------------------------------------------- the proposal row */
/* One row per thing the import found: the switch that decides it, the name,
   what the card carries now, and what the site says. Read left to right as a
   sentence with no words in it, which is why the arrow is a glyph rather than
   the word "becomes". */
.swap {
  display: flex;
  align-items: center;
  gap: 10px;
  min-height: 44px;
  padding: 6px 0;
  border-top: 1px solid var(--panel-edge);
  font-size: 13px;
  line-height: 1.3;
}
.swap:first-of-type { border-top: 0; }
.swap-use { display: flex; flex: none; }
.swap-name { flex: none; width: 56px; font-weight: 500; }
.swap-was {
  color: var(--muted-light);
  font-variant-numeric: tabular-nums;
  /* The one span in the row allowed to give way. At 375 the row's min-content
     ran 2px past the column, and the value standing here is the one a reader
     needs least: its dab is beside it, drawn. The proposed value never
     truncates. */
  min-width: 0;
  flex: 0 1 auto;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
}
.swap-is { color: var(--ink); font-variant-numeric: tabular-nums; }
/* Everything from here right is the proposal rather than what stands. */
.swap-to { display: flex; margin-left: auto; color: var(--muted-light); }
.swap-to svg { display: block; width: 16px; height: 16px; }
/* A colour, as itself. The inset hairline is what gives a near-white swatch
   an edge on a white panel, which is the same problem `accent_edge` solves on
   the card and the same answer scaled to 20 pixels. */
.dab {
  flex: none;
  display: block;
  width: 20px;
  height: 20px;
  border-radius: 4px;
  background: var(--c, var(--light));
  box-shadow: inset 0 0 0 1px rgba(0, 0, 0, .14);
}
.dab-none { background: var(--light); }
.dab-shot { background: var(--light); object-fit: contain; padding: 2px; }
/* A row whose proposal is None is a row with nothing to decide, so its switch
   is disabled and the whole row reads as quiet rather than as an option. */
.swap:has(input:disabled) .swap-is,
.swap:has(input:disabled) .swap-name { color: var(--muted-light); }
.swap input:disabled { opacity: .4; cursor: default; }

/* ------------------------------------------------------------ set up
   The checklist at the top of Home and of the empty state. One panel, one
   row per thing the plan asks for, and the row that is next is the only one
   with a ground under it, so the eye lands on what to press without a second
   colour being spent on it. From the 09-14 onboarding mock, scoped to
   `.steps` so nothing else inherits a 24px disc. */
.steps { padding: 0; }
.steps .panel-head { padding: 16px 16px 12px; }
.step-row {
  display: flex; align-items: flex-start; gap: 12px;
  padding: 14px 16px; border-radius: 10px;
  transition: background var(--t-fast);
}
.step-row:hover { background: var(--well-2); }
.step-row.is-now { background: var(--well); }
.step-disc {
  flex: none; width: 24px; height: 24px; border-radius: 50%;
  border: 1px solid var(--hair); background: transparent;
}
.step-disc.is-done { background: var(--blue); border-color: var(--blue); }
.step-say { flex: 1 1 auto; min-width: 0; }
.step-name { display: block; font-size: 13px; font-weight: 600; color: var(--ink); }
.step-note { display: block; margin-top: 2px; font-size: 12px; color: var(--muted-light); }
.step-do { flex: none; margin-left: auto; padding: 8px 16px; font-size: 13px; }

/* Home on a phone, after the set-up rules so the steps' own padding and the
   "Do it" fill give way: three blue pills under a blue chip is the loudest
   thing on the screen, so a step's action is a blue word, and only the
   current step says its note and its action. Figures and the plot come down
   to the width they sit in. */
@media (max-width: 699px) {
  .app-body > .home { gap: 22px; margin-top: 18px; }
  .steps .panel-head { padding: 14px 14px 8px; }
  .steps .panel-head h2 { font-size: 18px; }
  .step-row { padding: 10px 14px; gap: 10px; }
  .step-row:not(.is-now) .step-note { display: none; }
  .step-row:not(.is-now) .step-do { display: none; }
  .step-do { background: none; color: var(--blue); padding: 0; font-weight: 600; font-size: 13px; align-self: center; }
  .step-row.is-now .step-do { align-self: flex-start; margin-top: 1px; }
  .panel-hero { height: 248px; border-radius: 16px; }
  .hero-art .well-lit { inset: 10px 0 42px 0; }
  .cap { height: 42px; font-size: 12.5px; padding: 0 14px; }
  .strip { margin-top: 18px; }
  .strip .faces { gap: 2px; margin: 12px -16px 0; padding: 0 16px; }
  .fc { width: 64px; text-decoration: none; }
  .metric .figure { font-size: 44px; }
  .metric [data-plot] svg, .metric .plot svg { height: 84px; width: 100%; }
  .micro { gap: 8px 18px; margin-top: 12px; }
  .desk { gap: 20px; }
  .objects { gap: 20px; margin-top: 20px; }
}

/* ------------------------------------------------------------- the team */
/* The People table is the `dtable` with a face in front of the name, so what
   is here is the disc and the two cells the seats screen adds. 28px rather
   than the rail's 24: this is a row about a person, and the rail's disc is a
   corner of the chrome. The sub line under a name carries the title and the
   address, which is a second line inside one cell rather than two more
   columns of mostly-empty width. */
.row-face{display:inline-flex;align-items:center;justify-content:center;width:28px;height:28px;border-radius:50%;background:var(--well-2);color:var(--ink-2);font-size:11px;font-weight:600;letter-spacing:.02em}
.row-face img{width:28px;height:28px;border-radius:50%;object-fit:cover}
.dtable .c-face{width:1%;padding-right:0}
.dtable .c-state{white-space:nowrap}
/* Several addresses at one press: a box that takes a paste of them, grown by
   the person pasting rather than by the page. */
.invite-many{width:100%;min-height:72px;font:inherit;padding:8px 10px;border:0;border-radius:10px;box-shadow:inset 0 0 0 1px var(--line-warm);resize:vertical}

/* ------------------------------------------------- the business screens */
/* Bookings opens on the next seven days in the owner's zone: a count per
   day and nothing else, because a booking belongs to this identity and a
   face in a day cell would claim to know who on a team it is with. */
.week {
  display: grid;
  grid-template-columns: repeat(7, minmax(0, 1fr));
  gap: 10px;
  margin-top: 22px;
}
.day {
  display: flex;
  flex-direction: column;
  min-height: 122px;
  padding: 14px 14px 12px;
  border-radius: 16px;
  background: var(--well);
  box-shadow: inset 0 0 0 1px var(--line-soft);
}
.day.today {
  background: var(--window);
  box-shadow: inset 0 0 0 1px var(--line-warm), var(--sh-2);
}
.day small { font-size: 12px; color: var(--mute); }
.day b { font: 400 34px/1 var(--serif); margin-top: 4px; }
.day-n, .day-none { margin-top: auto; font-size: 12px; }
.day-n { color: var(--ink-2); font-weight: 500; }
.day-none { color: var(--faint); }
/* The People screen's overview (SEL-70): five tiles, each a link to where
   its count lives, two to a row on a phone and the record's across both, on
   the Bookings week's `--well`. Scoped to the strip: `.tile` is the team
   screen's already. */
.strip-tiles { display: grid; grid-template-columns: repeat(5, 1fr); gap: 12px; margin-bottom: 22px; }
.strip-tiles .tile { display: block; padding: 14px; border-radius: 12px; background: var(--well); text-decoration: none; color: inherit; }
.strip-tiles .tile small { display: block; opacity: .7; }
.strip-tiles .tile b { display: block; font-size: 28px; font-weight: 500; line-height: 1.1; margin-top: 4px; }
.strip-tiles .tile span { display: block; font-size: 13px; opacity: .7; margin-top: 2px; }
@media (max-width: 640px) { .strip-tiles { grid-template-columns: repeat(2, 1fr); } .strip-tiles .tile:last-child { grid-column: 1 / -1; } }
/* A line of Mark's brief and the row it came from, or "likely" */
.brief-line { margin: 0 0 8px; }
.brief-line .tag { margin-left: 6px; vertical-align: middle; }

/* Inbox is a list and a reading pane. The pane holds the message named by
   `?open=`, else the newest; opening one marks nothing read. */
.inbox-grid {
  display: grid;
  grid-template-columns: 380px minmax(0, 1fr);
  margin-top: 22px;
  border-radius: 18px;
  box-shadow: inset 0 0 0 1px var(--line-warm);
  overflow: hidden;
  min-height: 600px;
}
.inbox-list {
  list-style: none;
  margin: 0;
  padding: 8px;
  border-right: 1px solid var(--line-warm);
}
.inbox-list a {
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  gap: 2px 10px;
  padding: 10px 10px;
  border-radius: 10px;
  text-decoration: none;
}
.inbox-list a:hover { background: var(--well); }
.inbox-list li[aria-current] a {
  background: var(--well);
  box-shadow: inset 0 0 0 1px var(--line-soft);
}
.inbox-list a b {
  font-weight: 500;
  font-size: 13.5px;
  color: var(--ink-2);
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
.inbox-list b.new { font-weight: 650; color: var(--ink-warm); }
.inbox-list a span {
  grid-column: 1 / -1;
  font-size: 12.5px;
  color: var(--mute);
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
.inbox-list time { font-size: 12px; color: var(--faint); }
.read { padding: 30px 36px; }
.read h2 { font: 400 32px/1.1 var(--serif); letter-spacing: -.015em; }
.read-meta { color: var(--mute); font-size: 13px; margin-top: 10px; }
.read h2, .read-meta, .read-msg { overflow-wrap: anywhere; }
.read-msg {
  font: 400 19px/1.55 var(--serif);
  color: var(--ink-warm);
  margin-top: 24px;
  max-width: 560px;
  white-space: pre-wrap;
}
.read-do { margin-top: 26px; }
/* A contact's address is its own link in a row the name's stretched link
   covers, so it is lifted above that link the way a row's forms are. */
.dtable td > a[href^="mailto:"] { position: relative; z-index: 1; }
/* Contacts puts the name first and the address second, so the note is the
   long cell that takes the slack, and the name and address hold one line. */
@media (min-width: 700px) {
  .dtable:has(.c-note) th:nth-child(2),
  .dtable:has(.c-note) td:nth-child(2) { width: auto; white-space: nowrap; }
  .dtable:has(.c-note) td:first-child { white-space: nowrap; }
  .dtable .c-note { width: 100%; }
}

/* Team: the look the lock carries as one strip (the company or its mark,
   the accent colours, the switch), then the people as a wall of faces. */
.kit {
  display: flex;
  align-items: center;
  gap: 22px;
  margin-top: 22px;
  padding: 14px 18px;
  border-radius: 16px;
  background: var(--well);
  box-shadow: inset 0 0 0 1px var(--line-soft);
  flex-wrap: wrap;
}
.kit-name { font: 450 18px/1 var(--serif); }
.kit-logo { height: 26px; width: auto; max-width: 220px; object-fit: contain; }
.kit-sw {
  display: flex;
  gap: 6px;
  align-items: center;
  font-size: 12.5px;
  color: var(--mute);
}
.kit-sw i {
  width: 22px;
  height: 22px;
  border-radius: 50%;
  box-shadow: inset 0 0 0 1px rgba(0, 0, 0, .08);
}
.kit-sep { width: 1px; height: 26px; background: var(--line-warm); }
.kit-lock { display: flex; align-items: center; gap: 12px; margin-left: auto; }
.kit-lock .switch-inline { border: 0; padding: 0; }
.roster {
  display: grid;
  grid-template-columns: repeat(6, minmax(0, 1fr));
  gap: 22px 16px;
  margin-top: 8px;
}
.tile { position: relative; display: grid; gap: 8px; align-content: start; }
.tile-pic {
  position: relative;
  border-radius: 14px;
  overflow: hidden;
  aspect-ratio: 1 / 1.06;
  background: var(--well-2);
}
.tile-pic img {
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: 50% 28%;
}
.tile-disc {
  display: grid;
  place-items: center;
  width: 100%;
  height: 100%;
  font: 400 40px/1 var(--serif);
  color: var(--ink-2);
}
.tile.invited .tile-pic { opacity: .6; }
.tile-badge {
  position: absolute;
  left: 8px;
  top: 8px;
  font-size: 11.5px;
  font-weight: 600;
  padding: 3px 9px;
  border-radius: 999px;
  background: rgba(255, 253, 250, .92);
  box-shadow: var(--sh-1);
}
.tile h4 { font-weight: 600; font-size: 14.5px; line-height: 1.2; margin: 4px 0 0; }
.tile p { color: var(--mute); font-size: 12.5px; margin: 0; overflow-wrap: anywhere; }
.tile-ln { display: flex; gap: 10px; align-items: center; margin-top: 2px; }
.tile-ln b { margin-left: auto; font: 400 22px/1 var(--serif); }
/* The name is a stretched link over its tile (`.row-link::after`), so the
   tile is the positioned box and its forms sit above the link, the way
   `.c-do` forms do in a row. */
.tile form { display: inline; position: relative; z-index: 1; }
/* The role control shares the action line with Remove (SEL-71): the select
   wears the field look at the action row's height. */
.tile .tile-role { display: inline-flex; align-items: center; gap: 4px; }
.tile .tile-role select {
  height: 32px; padding: 0 8px; font: inherit; font-size: 13px; line-height: 1.3;
  border: 0; border-radius: 8px; box-shadow: inset 0 0 0 1px var(--line-warm);
  background: var(--window); color: var(--ink);
}
.tile .tile-role select:focus { outline: 2px solid var(--blue); outline-offset: 1px; }

@media (max-width: 1279px) {
  .roster { grid-template-columns: repeat(4, minmax(0, 1fr)); }
}
@media (max-width: 1023px) {
  .roster { grid-template-columns: repeat(3, minmax(0, 1fr)); }
  .inbox-grid {
    grid-template-columns: minmax(0, 1fr);
    box-shadow: none;
    min-height: 0;
  }
  .read { order: -1; padding: 0 0 24px; }
  .inbox-list { border-right: 0; padding: 0; }
}
@media (max-width: 699px) {
  .week {
    display: flex;
    overflow-x: auto;
    scrollbar-width: none;
    margin-left: -12px;
    margin-right: -12px;
    padding: 0 12px;
  }
  .day { flex: 0 0 112px; min-height: 96px; }
  .roster { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .kit-sep { display: none; }
}
/* Inbox pane: let the serif overhang breathe. After the 1023 block above,
   whose `.read` padding and the base grid's `overflow: hidden` it replaces. */
@media (max-width: 1023px) {
  .inbox-grid { overflow: visible; }
  .read { padding: 0 2px 24px; }
}
/* Team on a phone: facts as key and value rows, and people as a list rather
   than 2-up tiles. `.tile-pic` stops being a box, so what painted it (radius,
   ground, the invited fade, the badge's corner) is re-aimed at its parts. */
@media (max-width: 699px) {
  .facts { display: grid; grid-template-columns: minmax(0, 1fr); gap: 0; margin-top: 10px; }
  .facts > div { display: flex; justify-content: space-between; align-items: baseline; gap: 12px; padding: 9px 0; border-top: 1px solid var(--line-soft); font-size: 13px; color: var(--ink-2); }
  .facts > div:first-child { border-top: 0; }
  .facts strong { display: inline; margin: 0; font-size: 17px; }
  .kit { gap: 12px 16px; margin-top: 18px; padding: 12px 14px; border-radius: 14px; }
  .kit-name { font-size: 17px; }
  .kit-lock { margin-left: 0; width: 100%; justify-content: space-between; }
  /* People as a list: face left, everything else in one column. */
  .roster { display: flex; flex-direction: column; gap: 0; margin-top: 4px; }
  .tile { grid-template-columns: 48px minmax(0, 1fr); column-gap: 12px; row-gap: 3px; padding: 11px 0; border-top: 1px solid var(--line-soft); }
  .tile:first-child { border-top: 0; }
  .tile > * { grid-column: 2; }
  .tile-pic { display: contents; }
  .tile-pic img, .tile-disc { grid-column: 1; grid-row: 1 / span 6; width: 48px; height: 48px; border-radius: 50%; object-fit: cover; background: var(--well-2); }
  .tile-disc { display: grid; place-items: center; font-size: 20px; }
  .tile.invited .tile-disc { opacity: .6; }
  .tile-badge { position: static; grid-column: 2; justify-self: start; font-size: 10.5px; padding: 2px 7px; background: var(--well-2); }
  .tile h4 { font-size: 14px; }
  .tile p { margin: 0; font-size: 12.5px; line-height: 1.35; }
  .tile-ln { gap: 12px; margin-top: 2px; }
  .tile-ln b { font-size: 18px; }
  .dorow { gap: 14px; margin-top: 2px; }
}
/* Bookings on a phone, after the scroller above so it wins: the week is
   seven cells across rather than three and a third in a scroller. */
@media (max-width: 699px) {
  /* Seven days across, numbers only; a booked day is a dot. */
  .week { display: grid; grid-template-columns: repeat(7, minmax(0, 1fr)); gap: 3px; margin: 14px 0 0; padding: 0; overflow: visible; }
  .day { flex: none; min-height: 0; padding: 7px 0 7px; align-items: center; text-align: center; border-radius: 9px; }
  .day small { font-size: 10.5px; letter-spacing: .01em; }
  .day b { font-size: 19px; margin-top: 2px; }
  .day-none { display: none; }
  .day-n { margin-top: 6px; width: 6px; height: 6px; border-radius: 50%; background: var(--blue); font-size: 0; color: transparent; overflow: hidden; }
  /* The list keeps its times. */
  body.app-bookings .dtable .c-when { display: table-cell; width: 1%; white-space: nowrap; font-size: 12.5px; color: var(--mute); vertical-align: top; }
  /* An empty view is one line: the tabs above already name it. */
  body.app-bookings .panel:has(> .panel-head + p.rule:last-child) .panel-head { display: none; }
  body.app-bookings .panel:has(> .panel-head + p.rule:last-child) .rule { margin-top: 18px; font-size: 14px; }
}

/* --------------------------------------------------- the chat launcher */
/* Chatwoot's SDK appends its stylesheet to <body> (DOMHelpers.js:4-10) while
   both of our sheets are <link>s in <head>, so sdk.css wins every
   equal-specificity tie and anything below that has to beat it carries
   `!important` with the line it beats named beside it. The button's ground is
   worse than a stylesheet: IFrameHelper.js:330-331 writes
   `chatIcon.style.background` inline from the inbox's widget colour, and an
   inline style beats any external rule that is not `!important`.

   What changes: 64px becomes 56 on `--blue`, the vendor's 0 8px 24px/.16 drop
   becomes the app's own lift, the hover stops growing the shadow, and the
   Chatwoot logo inside the button (bubbleHelpers.js:30-48) is hidden and
   replaced by a plain speech bubble drawn as a mask on `::before`. Below
   1024px the tab bar owns the bottom 66px of the window (`.tabs` above),
   so the bubble and the window are both lifted clear of it. */
.woot-widget-bubble {
  width: 56px !important;            /* sdk.css 42-55 is 64 */
  height: 56px !important;
  bottom: 20px !important;
  background: var(--blue) !important; /* beats the inline widget colour */
  box-shadow: 0 4px 16px rgba(0, 0, 0, .12) !important; /* sdk.css 47 is !important */
  transition: background var(--t-base) var(--ease-out),
              transform var(--t-base) var(--ease-out);
}
.woot-elements--right.woot-widget-bubble { right: 20px !important; }
/* sdk.css 149-152 keeps the vendor blue and grows the shadow on hover. The
   action language here is the button's hover colour and nothing moving. */
.woot-widget-bubble:hover {
  background: var(--blue-hover) !important;
  transform: none;
}
.woot-widget-bubble:focus-visible {
  outline: 3px solid var(--blue);
  outline-offset: 2px;
}
.woot-widget-bubble svg { display: none !important; } /* sdk.css 154-160 is !important */
/* The glyph, drawn rather than shipped. A single-layer mask: an `exclude`
   composite is dropped by a production build, which is the DEOS hazard. The
   close button's two bars are drawn on the same pseudo-element by sdk.css
   179-189, so `:not(.woot--close)` keeps this off them. */
.woot-widget-bubble:not(.woot--close)::before {
  content: "";
  position: absolute;
  inset: 0;
  margin: auto;
  width: 24px;
  height: 24px;
  background: #fff;
  -webkit-mask: url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'><path d='M12 3C7 3 3 6.4 3 10.6c0 2.3 1.2 4.4 3.2 5.8L5.4 21l4.6-2.2c.6.1 1.3.2 2 .2 5 0 9-3.4 9-7.6S17 3 12 3z'/></svg>") center / 24px 24px no-repeat;
  mask: url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'><path d='M12 3C7 3 3 6.4 3 10.6c0 2.3 1.2 4.4 3.2 5.8L5.4 21l4.6-2.2c.6.1 1.3.2 2 .2 5 0 9-3.4 9-7.6S17 3 12 3z'/></svg>") center / 24px 24px no-repeat;
}
/* sdk.css 179-189 centres the 2 x 24px bars for a 64px button. */
.woot--close::before,
.woot--close::after {
  left: 28px !important;
  top: 16px !important;
}
.woot-widget-bubble.unread-notification::after {
  background: var(--alert) !important; /* sdk.css 86-97 is #ff4040 */
}
.woot-widget-holder {
  border-radius: 16px !important;
  box-shadow: 0 12px 40px rgba(0, 0, 0, .14) !important; /* sdk.css 7 */
}
@media (min-width: 667px) {
  /* 56 for the bubble, 20 under it, 16 of air: sdk.css 344 assumed 64. */
  .woot-widget-holder { bottom: 92px !important; }
}
@media (min-width: 667px) and (max-width: 1023.98px) {
  .woot-widget-bubble { bottom: calc(66px + 10px + env(safe-area-inset-bottom)) !important; }
  .woot-widget-holder { bottom: calc(148px + env(safe-area-inset-bottom)) !important; }
  /* sdk.css 345-347 keeps height: calc(90% - 84px) with a 250px floor, sized
     for a 104px bottom. Raised to 148px, a landscape phone (844x390) would put
     the window's top above the viewport, so the height is what is left above
     the new bottom, and the floor is lowered to match. */
  body .woot-widget-holder {
    /* sdk.css 347 is also !important and is injected into <body>, so it
       wins an equal-specificity tie; the body prefix breaks the tie. */
    height: calc(100% - 164px - env(safe-area-inset-bottom)) !important;
    min-height: 200px !important;
  }
}
@media (max-width: 666.98px) {
  /* The window is full-screen here (sdk.css 303-309), so only the bubble
     needs lifting off the tab bar. */
  .woot-widget-bubble { bottom: calc(66px + 10px + env(safe-area-inset-bottom)) !important; }
}
@media (prefers-reduced-motion: reduce) {
  .woot-widget-bubble { transition: none; }
}

/* ------------------------------------------------------ the motion kit */
/* The rolling Save (DESIGN.md 2.2b, "Motion kit"). motion.js wraps the label
   of a primary Save-type button at runtime into three stacked words and puts
   `data-state` on the button; the stack moves up one line for busy and two
   for done. The markup in the templates is untouched, height and radius are
   the button's own, and the script freezes the width before the wrap, so a
   longer word never moves the head the button sits in. */
body.app .btn-primary[data-roll] { position: relative; overflow: hidden; display: inline-flex; align-items: center; justify-content: center; gap: 6px; }
body.app .roll { display: block; height: 1.2em; line-height: 1.2em; overflow: hidden; text-align: center; }
body.app .roll > span { display: block; height: 1.2em; transition: transform var(--t-swap) var(--ease-glide); }
body.app [data-state="busy"] .roll > span { transform: translateY(-100%); }
body.app [data-state="done"] .roll > span { transform: translateY(-200%); }

/* The glyph beside the word (DESIGN.md 2.2b, "Motion kit"): nothing at idle,
   which is what the button looked like before; a 14px ring while the request
   is out, the one loop allowed and only for as long as it is true; a 14px
   check once the page says it saved. The state word also goes to assistive
   tech through `.roll-say`, so no new paragraph is drawn anywhere. */
body.app .roll-glyph { width: 14px; height: 14px; flex: none; display: none; }
body.app [data-state="busy"] .roll-glyph {
  display: block;
  border: 2px solid rgba(255, 255, 255, .45);
  border-top-color: #fff;
  border-radius: 50%;
  animation: roll-spin 700ms linear infinite;
}
body.app [data-state="done"] .roll-glyph {
  display: block;
  background: #fff;
  -webkit-mask: url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 14 14'><path d='M3 7.4l2.6 2.6L11 4.6' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'/></svg>") center / 14px 14px no-repeat;
  mask: url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 14 14'><path d='M3 7.4l2.6 2.6L11 4.6' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'/></svg>") center / 14px 14px no-repeat;
}
@keyframes roll-spin { from { transform: rotate(0deg); } to { transform: rotate(360deg); } }
body.app .roll-say { position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0 0 0 0); }

/* The tab pill (DESIGN.md 2.2b, "Motion kit"). motion.js appends it as the
   last child of `.tabs`; it is absolute, so it takes no grid cell, and
   `.tabs` is already fixed, which makes it the containing block. Blue,
   because the active tab's label already is. The script places it with a
   transform from the active tab's centre and stretches it across a tap with
   a scale from its left edge; without the script there is no pill. */
body.app .tab-pill {
  position: absolute;
  left: 0;
  bottom: calc(6px + env(safe-area-inset-bottom));
  width: 28px;
  height: 4px;
  border-radius: 2px;
  background: var(--blue);
  transform-origin: 0 50%;
  transition: transform var(--t-swap) var(--ease-out);
  pointer-events: none;
}
html:not(.js) body.app .tab-pill { display: none; }

/* Reduced motion (DESIGN.md 2.2b, "Motion kit"): the roll and the pill land
   at once, and the ring stands still while the request is out. */
@media (prefers-reduced-motion: reduce) {
  body.app .roll > span, body.app .tab-pill { transition: none; }
  body.app .roll-glyph, body.app [data-state="busy"] .roll-glyph { animation: none; }
}

/* The fold (DESIGN.md 2.2b, "Motion kit"). A deleted quote or a removed
   member: motion.js freezes the row at its measured height, then sets
   `data-fold` and a height of 0. Height is the one length the kit animates,
   because a list changing length has no transform equivalent; everything
   else here is opacity. `data-h` carries the measure, so the unfold runs the
   same way back. */
body.app [data-h] { transition: height var(--t-fast) var(--ease-out), opacity var(--t-fast) var(--ease-out), margin var(--t-fast) var(--ease-out), padding var(--t-fast) var(--ease-out); }
body.app [data-fold] { overflow: hidden; opacity: 0; margin-top: 0; margin-bottom: 0; padding-top: 0; padding-bottom: 0; }

/* The toast with Undo (DESIGN.md 2.2b, "Motion kit"). One at a time, on the
   body and never in `.app-main`, 12px above the phone tab bar, 20px off the
   bottom from 1024 up. The 2px bar along its bottom edge is the six seconds, drawn
   as a scale so nothing but a transform runs. */
body.app .toast {
  position: fixed;
  left: 50%;
  bottom: calc(66px + 12px + env(safe-area-inset-bottom));
  z-index: 30;
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 24px;
  height: 44px;
  min-width: 280px;
  padding: 0 10px 0 16px;
  background: var(--window);
  color: var(--ink-warm);
  font-size: 14px;
  border-radius: 12px;
  box-shadow: var(--sh-2);
  overflow: hidden;
  opacity: 0;
  pointer-events: none;
  transform: translate(-50%, 8px);
  transition: opacity var(--t-swap) var(--ease-out), transform var(--t-swap) var(--ease-out);
}
body.app .toast[data-on] { opacity: 1; transform: translate(-50%, 0); pointer-events: auto; }
body.app .toast-bar { position: absolute; left: 0; right: 0; bottom: 0; height: 2px; background: var(--line-warm); transform-origin: 0 50%; transition: transform 6s linear; }
@media (min-width: 1024px) { body.app .toast { bottom: 20px; } }

/* Copy confirms on itself (DESIGN.md 2.2b, "Motion kit"): for two seconds
   the card address's Copy reads "Copied" with a 12px check before it. */
body.app .btn-text[data-done]::before {
  content: "";
  display: inline-block;
  width: 12px;
  height: 12px;
  margin-right: 4px;
  vertical-align: -1px;
  background: var(--blue);
  -webkit-mask: url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 14 14'><path d='M3 7.4l2.6 2.6L11 4.6' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'/></svg>") center / 12px 12px no-repeat;
  mask: url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 14 14'><path d='M3 7.4l2.6 2.6L11 4.6' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'/></svg>") center / 12px 12px no-repeat;
}

/* The drop rows (DESIGN.md 2.2b, "Motion kit"). Under the Profile photo,
   the Brand logo and the Team list once a file is chosen or dropped: a 28px
   thumbnail (a document glyph when the file is not a picture), the name, the
   size, and the verdict the server would give. A bad verdict is in alert
   red with "Choose another" under it. The 2px hairline is still until the
   form sends; then a 40% segment slides along it, the one loop, and only
   while `data-busy` is true. No paragraphs, so no screen's budget moves. */
body.app .drop-row { display: grid; grid-template-columns: 28px 1fr auto; gap: 4px 10px; align-items: center; position: relative; margin-top: 10px; padding: 8px 0 10px; overflow: hidden; }
body.app .drop-thumb { width: 28px; height: 28px; border-radius: 6px; background: var(--well); overflow: hidden; }
body.app .drop-thumb img { display: block; width: 100%; height: 100%; object-fit: cover; }
body.app .drop-thumb:empty::after {
  content: "";
  display: block;
  width: 100%;
  height: 100%;
  background: var(--mute);
  -webkit-mask: url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 28 28'><path d='M10 8.5h5.5l3 3V19a.5.5 0 0 1-.5.5h-8a.5.5 0 0 1-.5-.5V9a.5.5 0 0 1 .5-.5zM15.5 8.5v3h3' fill='none' stroke='black' stroke-width='1.3' stroke-linejoin='round'/></svg>") center / 28px 28px no-repeat;
  mask: url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 28 28'><path d='M10 8.5h5.5l3 3V19a.5.5 0 0 1-.5.5h-8a.5.5 0 0 1-.5-.5V9a.5.5 0 0 1 .5-.5zM15.5 8.5v3h3' fill='none' stroke='black' stroke-width='1.3' stroke-linejoin='round'/></svg>") center / 28px 28px no-repeat;
}
body.app .drop-name { font-weight: 500; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
body.app .drop-size, body.app .drop-say { color: var(--mute); font-size: 12px; }
body.app .drop-say { grid-column: 2 / -1; }
body.app .drop-row .btn-text { grid-column: 2 / -1; justify-self: start; }
body.app [data-bad="1"] .drop-say { color: var(--alert); }
body.app .drop-bar { position: absolute; left: 0; right: 0; bottom: 0; height: 2px; background: var(--line-warm); }
body.app .drop-bar::after { content: ""; position: absolute; inset: 0; width: 40%; background: var(--blue); transform: translateX(-100%); }
body.app [data-busy="1"] .drop-bar::after { animation: drop-run 1.2s var(--ease-glide) infinite; }
@keyframes drop-run { to { transform: translateX(250%); } }
body.app .is-over { outline: 2px dashed var(--blue); outline-offset: 6px; border-radius: 12px; }

/* Reduced motion, part two: the fold and the toast land at once, and a
   sending row's bar stands still and blue instead of sliding. */
@media (prefers-reduced-motion: reduce) {
  body.app [data-h], body.app .toast, body.app .toast-bar { transition: none; }
  body.app [data-busy="1"] .drop-bar::after { animation: none; }
  body.app [data-busy="1"] .drop-bar { background: var(--blue); }
}

/* Needs (SEL-67) */
.need-list{list-style:none;margin:0;padding:0}
.need-row{display:flex;gap:16px;align-items:flex-start;padding:14px 0;border-top:1px solid var(--line-soft)}
.need-row:first-child{border-top:0}
.need-main{flex:1;min-width:0}
.need-main p{margin:4px 0 0}
.need-actions{display:flex;flex-wrap:wrap;gap:8px 12px;align-items:center;flex:0 0 auto}
@media (max-width: 480px){.need-row{flex-direction:column;gap:8px}}

.style-pick{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:12px;border:0;padding:0;margin:0}
.style-pick label{display:grid;align-content:start;gap:8px;padding:10px;border:1px solid var(--hair);border-radius:10px;cursor:pointer}
.style-pick label:has(input:checked){border-color:var(--ink);box-shadow:inset 0 0 0 1px var(--ink)}
.style-pick .mini{border-radius:6px;aspect-ratio:4/3;display:grid;place-items:start center;overflow:hidden;background:var(--mb-mesa,#131313);padding:0}
.style-pick .mini .mb-mini-doc{zoom:.3;width:640px;min-height:0;padding-top:24px;overflow:hidden}
.style-pick .mini .mb-mini-doc :is([data-p=de],[data-p=para],[data-p=th],[data-p=f1],[data-p=nota]){display:none}   /* the thumbnail keeps the title, the dates, one line and the total */
.style-pick .mini .mb-mini-doc[data-estilo=block] .mb-td .mb-cifra{font-size:120px}
.style-pick .mini .mb-mini-doc[data-estilo=block] .mb-doc{padding-top:36px}
.style-pick .mini .mb-mini-doc[data-estilo="terminal"] .mb-doc{width:600px}
.mb-mini-doc[data-estilo="block"]{background:var(--hoja)}
.style-pick input{position:absolute;opacity:0;pointer-events:none}
@media (max-width:640px){.style-pick{grid-template-columns:1fr}.style-pick .mini{aspect-ratio:auto;padding:12px 0}.style-pick .mini .mb-mini-doc{zoom:.5}}
.app-receipts .style-pick{max-width:560px}
/* a receipt's lines on the New receipt form: item, detail, amount in one row; stacked on a phone */
.lines-form{display:grid;grid-template-columns:minmax(0,2fr) minmax(0,2fr) 120px;gap:8px;align-items:end;margin-top:8px}
.lines-form .field{margin:0}
@media (max-width:640px){.lines-form{grid-template-columns:1fr}}
.lines dd code{font-size:12.5px;overflow-wrap:anywhere}
