/* Meal Log's stylesheet, SCOPED to its own domain.
 *
 * GENERATED by tools/scope-food-css.py from Meal Log/web/styles.css - not a
 * verbatim lift. Re-run that script rather than hand-editing selectors here; its
 * header explains every rule applied. Hand-written adaptations to the merged
 * layout (the tab bar moving to the top, the full-height shell fitting beside the
 * app's own bottom bar) live in css/food-shell.css instead, so this file can be
 * regenerated without losing them.
 *
 * Meal Log's own comments are preserved verbatim below.
 */
/* Meal Log - one stylesheet, no framework. iOS-flavoured, light & dark.

   Inherited from Workout Log (web/styles.css), which is the family's identity
   rather than a starting point to improve on: the token block, both dark
   blocks and all ten accent palettes are copied across value for value, so a
   screen from one app and a screen from the other are the same object.

   What is not here is everything Workout Log has that this app has no idea
   about - the muscle map, the body map, the charts, the interval timer, the
   progress photos - and .toast.pr, its gold personal-best toast, which this
   app must never grow an equivalent of. A number somebody ate is not a score.

   Four things are fixed rather than inherited, each marked FIX where it lands:
   --line and --warn get defined (Workout Log references both and defines
   neither), there is a real :focus-visible ring (Workout Log has none at all),
   and the four radii already in use are given names. */
.dom-food {color-scheme: light; /* 5.0:1 on --surface. The old #898781 was shared with dark mode, where it
     lands at 4.9:1, but on a near-white surface it was 3.5:1 — under AA for
     everything it is used on, which is every hint, meta line and glyph
     button in the app. */
  --muted:        #6c6a65; --grid:         #e1e0d9; --axis:         #c3c2b7; /* Was #d9480f: 4.30:1 under white ink, which is the label on every primary
     button. Craig asked for it darker; 5.17:1 is what darker has to mean to
     be worth doing. tests/accent-test.js holds every palette to that line. */
  /* --accent: #c43f0b - now Panora's own (sleep.css), which lifts it in dark mode */ /* The fill colour used as small type is 5.03:1 on --surface but only 4.49:1
     on --plane, and accent type — every glyph button, the Timer pill, "+ Add
     set" — lands on both. This is 5.55:1 and 4.95:1. */
  /* --accent-text: #b83c08 - now Panora's own (sleep.css), which lifts it in dark mode */ /* The top of .btn.primary's gradient. White sits across the whole button,
     so the lighter end carries the same 4.5 floor as the fill; the old
     #ee5a0d was 3.44:1 and a11y-test skips gradients, so nothing caught it. */
  /* --accent-hi: #ca4c0b - now Panora's own (sleep.css), which lifts it in dark mode */ /* The icon's ground, which the splash card borrows so the two are one object.
     Deliberately NOT redefined in either dark block: the app icon on the home
     screen is ember whatever the phone's theme is, so the card that follows it
     has to be too. It still follows the chosen accent — every palette sets this
     pair once, in its light rule only.

     --icon-hi is the accent itself rather than something lighter, because the
     accents are picked to carry white ink at 4.5:1 and --icon-mark is near
     white; starting any lighter would put the tagline under the line. --icon-lo
     is the same hue at 70%, which is the corner-to-corner fall the icon has. */
  --icon-hi:      #c43f0b; /* the cream of the dumbbell in icons/ */
  --star:         #c07f00; /* 3.3:1 on --surface; gold was 2.1 */
  --danger:       #d03b3b; --good:         #006300; --radius:       14px; /* FIX: referenced by Workout Log with no fallback and defined nowhere, so
     two of its borders render unstyled. Same value as --grid because they are
     the same line: --hairline is translucent and stacks on whatever sits
     behind it; --line is the opaque one, for a control drawing its own edge. */
  --line:         #e1e0d9; /* FIX: existed only as the fallback inside var(--warn, #8a6508) at two call
     sites, which is a token in everything but name. Written down so the two
     cannot drift, and so it lightens in dark mode the way --danger, --good and
     --star already do. Amber, never red: this warns that the device is running
     out of room. Nothing in this app warns about what somebody ate. */
  --warn:         #8a6508; /* FIX: the four radii the family already used, written down (Mellow names
     them the same way). --radius stays as the name the inherited components
     were written against, and it is --r-md. */
  --r-lg:         20px; --r-md:         14px; --r-sm:         10px; --r-pill:       999px;}
@media (prefers-color-scheme: dark) {
:root:where(:not([data-theme="light"])) .dom-food {color-scheme: dark; --muted:        #969389; --grid:         #2c2c2a; --axis:         #383835; --star:         #eda100; /* bright is fine on a dark surface */
    --danger:       #e66767; --good:         #0ca30c; --line:         #2c2c2a; --warn:         #d9a63c; /* lightened for a dark surface, same as --star */;}
}
:root[data-theme="dark"] .dom-food {color-scheme: dark; --muted:        #969389; --grid:         #2c2c2a; --axis:         #383835; --star:         #eda100; --good:         #0ca30c; --line:         #2c2c2a; --warn:         #d9a63c; /* lightened for a dark surface, same as --star */;}
.dom-food * { box-sizing: border-box; }
.dom-food, .dom-food {
  margin: 0;
  height: 100%;
  overflow: hidden;
}
.dom-food {
  background: var(--plane);
  color: var(--text);
  font: 17px/1.35 system-ui, -apple-system, "Segoe UI", sans-serif;
  -webkit-font-smoothing: antialiased;
  -webkit-text-size-adjust: 100%;
  -webkit-tap-highlight-color: transparent;
  overscroll-behavior: none;
}
body.modal-open { overflow: hidden; }
.dom-food button, .dom-food input, .dom-food select, .dom-food textarea {
  font: inherit;
  color: inherit;
  font-family: inherit;
}
.dom-food button { background: none; border: 0; padding: 0; cursor: pointer; color: inherit; }
.dom-food button:disabled { opacity: 0.35; }/* FIX: the keyboard ring. Workout Log has no :focus-visible rule anywhere, so
   tabbing through it is invisible - it strips the tap highlight for touch and
   then gives nothing back to a keyboard or a switch control. One rule, on the
   accent, so it recolours with the theme and cannot be forgotten on a new
   component. :focus-visible and not :focus, so a thumb tap does not leave a
   ring sitting on the button afterwards. */
.dom-food a:focus-visible, .dom-food button:focus-visible, .dom-food input:focus-visible, .dom-food select:focus-visible, .dom-food textarea:focus-visible, .dom-food summary:focus-visible, .dom-food [tabindex]:focus-visible {
  outline: 2px solid var(--accent);
  outline-offset: 2px;
}/* Anything flush against an edge draws its ring inside itself instead, or the
   offset puts half of it outside the element's own clipping box. */
.dom-food .tab:focus-visible, .dom-food .list-btn:focus-visible, .dom-food .row-field.as-row:focus-visible, .dom-food .sheet-btn:focus-visible { outline-offset: -2px; }/* ---------- shell ---------- */
.dom-food #app {
  display: flex;
  flex-direction: column;
  height: calc(100vh / var(--tz, 1));
  height: calc(100dvh / var(--tz, 1));
}
.dom-food #main {
  flex: 1;
  min-height: 0;
  display: flex;
  flex-direction: column;
}/* One <section> per tab. All four sit in the DOM at once, with [hidden] on the
   three that are not showing - Workout Log swaps #main's innerHTML instead, and
   so has nothing like this. Each screen has to be the same flex column #main
   is, or the .scroll inside it has nothing to grow against and the page stops
   scrolling at its content's height. */
.dom-food .food-screen {
  flex: 1;
  min-height: 0;
  display: flex;
  flex-direction: column;
}/* display:flex beats the user agent's [hidden] rule, so a hidden screen would
   otherwise stack under the visible one. Stated here, once, rather than left
   for whoever notices four tabs rendering at the same time. */
.dom-food .food-screen[hidden] { display: none; }
.dom-food .page-head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 8px;
  padding: max(8px, env(safe-area-inset-top)) 12px 8px;
  padding-left: max(12px, env(safe-area-inset-left));
  padding-right: max(12px, env(safe-area-inset-right));
  background: var(--plane);
  border-bottom: 1px solid var(--hairline);
  /* Its own case of the sideways-drag bug that .scroll and .sheet-body carry
     notes about. A header row with a date pill and two glyph buttons really is
     wider than a 320px phone. body's overflow:hidden happens to catch it, but
     a header sitting outside .scroll should not depend on an ancestor for
     that - same as everywhere else, it clips its own overflow. */
  overflow-x: hidden;
}
.dom-food .page-head h1 {
  margin: 0;
  font-size: 26px;
  font-weight: 700;
  letter-spacing: -0.02em;
}
.dom-food .scroll {
  flex: 1;
  min-height: 0;
  overflow-y: auto;
  /* Stated, not left to the cascade. overflow-y:auto on its own computes the
     x axis to auto too, so anything a few pixels too wide anywhere in the app
     silently turns the page into a two-axis drag instead of showing up as a
     clipped edge somebody would notice. The page scrolls one way; a genuinely
     wide thing gets its own scroller. */
  overflow-x: hidden;
  -webkit-overflow-scrolling: touch;
  padding: 12px max(12px, env(safe-area-inset-left)) 24px max(12px, env(safe-area-inset-right));
}/* ---------- tab bar ---------- */
.dom-food .tabbar {
  display: flex;
  border-top: 1px solid var(--hairline);
  background: color-mix(in srgb, var(--surface) 92%, transparent);
  backdrop-filter: saturate(180%) blur(20px);
  -webkit-backdrop-filter: saturate(180%) blur(20px);
  padding-bottom: env(safe-area-inset-bottom);
}
.dom-food .tab {
  flex: 1;
  min-height: var(--tabbar-h);
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 3px;
  color: var(--muted);
  font-size: 10px;
  font-weight: 500;
  padding: 6px 2px;
}
.dom-food .tab svg {
  width: 24px;
  height: 24px;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.9;
  stroke-linecap: round;
  stroke-linejoin: round;
}
.dom-food .tab.active { color: var(--accent-text); }/* ---------- generic bits ---------- */
.dom-food .card {
  background: var(--surface);
  border-radius: var(--r-md);
  box-shadow: var(--shadow);
  padding: 12px;
  margin-bottom: 12px;
}
.dom-food .section-head {
  display: flex;
  align-items: baseline;
  justify-content: space-between;
  margin: 20px 4px 8px;
  font-size: 14px;
  font-weight: 600;
  text-transform: uppercase;
  letter-spacing: 0.05em;
  color: var(--muted);
}
.dom-food .section-note { text-transform: none; letter-spacing: 0; font-weight: 400; }
.dom-food .hint {
  margin: 8px 4px 16px;
  font-size: 15px;
  line-height: 1.45;
  color: var(--text-2);
}
.dom-food .hint.center { text-align: center; }
.dom-food .center { text-align: center; }/* The Today header, added 2026-08-26. The .page-head comment above already
   anticipated "a date pill and two glyph buttons" — this is that row.

   min-width:0 on the nav and the pill together are what let the date text
   ellipsis instead of pushing the arrows off a 320px screen. */
.dom-food .date-nav {
  display: flex;
  align-items: center;
  gap: 2px;
  min-width: 0;
}
.dom-food .date-pill {
  min-width: 0;
  min-height: 40px;
  padding: 0 8px;
  border-radius: 12px;
  font-size: 20px;
  font-weight: 700;
  letter-spacing: -0.02em;
  color: var(--text);
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
.dom-food .date-pill:active { background: var(--surface-2); }/* The forward arrow on today is DISABLED, not hidden: it keeps its place in
   the row, so paging back and forward does not make the header jump around
   under the thumb. The dimming comes from the shell's own `button:disabled`
   rule above rather than from a second number here. *//* The three ways in to logging, on Today. Three across rather than three
   stacked full-width buttons: this sits at the bottom of a screen whose job
   is the day, and 132px of stacked buttons would push the food off a phone.

   ⚠ minmax(0, 1fr), not 1fr. A grid track's default minimum is auto, so a
   long translated label ("Escanear código") would refuse to shrink and push
   the row wider than the screen instead of wrapping inside its own button. */
.dom-food .log-actions {
  display: grid;
  grid-template-columns: repeat(3, minmax(0, 1fr));
  gap: 8px;
  margin-bottom: 12px;
}
.dom-food .log-actions .btn {
  width: 100%;
  padding: 0 8px;
  font-size: 15px;
}/* One stat on the Today block: the number, then the reference beside it.
   ⚠ There is no bar, no track and no fill here on purpose, and there must
   never be one - see the long note on statsBlock() in js/app.js. The
   percentage is TEXT, it takes the same muted colour whatever it says, and it
   has no threshold at which anything changes. */
.dom-food .stat-val {
  display: inline-flex;
  align-items: baseline;
  gap: 8px;
  min-width: 0;
}
.dom-food .chip {
  padding: 5px 10px;
  border-radius: 14px;
  background: var(--surface);
  box-shadow: var(--shadow);
  font-size: 12px;
  color: var(--text-2);
}
.dom-food .chip b { color: var(--text); font-weight: 600; }/* ---------- buttons ---------- */
.dom-food .btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 6px;
  min-height: 44px;
  padding: 0 16px;
  border-radius: 12px;
  background: var(--surface);
  box-shadow: var(--shadow);
  font-size: 16px;
  font-weight: 600;
  color: var(--accent-text);
}
.dom-food .btn.primary { background: linear-gradient(180deg, var(--accent-hi), var(--accent-lo)); color: var(--accent-ink); }/* --danger marks an action that destroys something the person cannot get back
   - erase everything, delete this entry. It is never the colour of a number.
   Nothing goes red here because one amount turned out larger than another. */
.dom-food .btn.danger { color: var(--danger); }
.dom-food .btn.wide { display: flex; width: 100%; margin-bottom: 12px; }
/* A day marked "That’s everything today": a quiet line with a real Undo button (panel 2 retest:
   plain text with an Undo that did not look tappable). */
.dom-food .day-done { display: flex; align-items: center; justify-content: space-between; gap: 12px; margin: 0 0 12px; padding: 10px 6px 10px 16px; border: 1px solid var(--hairline); border-radius: var(--r-sm); color: var(--muted); font-size: 15px; }
/* "Turn off these check-ins" on a long fast's check-in (decision 0100). */
.fast-check .link-btn { min-height: 44px; padding: 0; border: 0; background: none; color: var(--accent-text); font: inherit; font-weight: 600; text-decoration: underline; cursor: pointer; }
.dom-food .day-done .link-btn { flex: none; min-height: 44px; padding: 0 12px; border: 0; background: none; color: var(--accent-text); font: inherit; font-weight: 600; cursor: pointer; }
.dom-food .btn.small { min-height: 36px; padding: 0 12px; font-size: 14px; border-radius: var(--r-sm); }
.dom-food .btn:active { transform: scale(0.985); }
.dom-food .icon-btn {
  width: 40px;
  height: 40px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  border-radius: 12px;
  font-size: 22px;
  line-height: 1;
  color: var(--accent-text);
}
.dom-food .icon-btn.small { width: 34px; height: 34px; font-size: 20px; }
.dom-food .icon-btn.placeholder { visibility: hidden; }
.dom-food .icon-btn:active { background: var(--surface-2); }/* A small control keeps the density it was drawn at and still gets a real hit
   box: the painted size stays put and the target grows past it. Vertical only
   - these sit in flex rows a few pixels apart, and widening them would let
   neighbours steal each other's taps. */
.dom-food .seg, .dom-food .fchip, .dom-food .linky { position: relative; }
.dom-food .seg::after, .dom-food .fchip::after, .dom-food .linky::after {
  content: '';
  position: absolute;
  top: -7px; right: 0; bottom: -7px; left: 0;
}
.dom-food .linky {
  display: block;
  width: 100%;
  margin: 10px 0 2px;
  padding: 6px 0;
  background: none;
  border: 0;
  color: var(--accent-text);
  font-size: 13.5px;
  text-align: center;
}
.dom-food .linky:active { opacity: .6; }/* ---------- list rows ---------- *//* ⚠⚠ THIS WAS `display: block` UNTIL 2026-08-26 AND IT IS WHY EVERY LIST IN
   THE APP READ AS CROWDED. Craig, from a real phone: "we need more space
   between items and their info. It's really crowded right now."

   Every .list-btn holds two spans - a name and its figure. Under `block` they
   are plain inline boxes, so they butt straight together with no separation
   at all and the browser renders them as one run of text:

       Flour tortilla306 kcal / 100 g
       9:41 PM1.89 L
       8:15 AM Omelette and hash browns 220 g780 kcal

   It reads as a density problem and is actually a missing layout. Flex with
   space-between puts the figure on the right where every .row-field in the app
   already puts it, and the gap guarantees separation even when a long name
   pushes the two together.

   ⚠ `align-items: baseline`, not center: the figure is a smaller font than the
   name, and centring two different type sizes leaves them visibly misaligned
   on a row that is meant to read as one line.
   ⚠ `min-width: 0` on the name, or a long food name refuses to shrink and
   shoves the figure off the right edge instead of ellipsing. */
.dom-food .list-btn {
  display: flex;
  align-items: baseline;
  justify-content: space-between;
  gap: 14px;
  width: 100%;
  text-align: left;
  min-height: 52px;
  padding: 14px 4px;
  font-size: 16px;
  color: var(--accent-text);
  border-bottom: 1px solid var(--hairline);
}
.dom-food .list-btn > :first-child { min-width: 0; }/* The figure never wraps to a second line and never shrinks to nothing - it is
   the shorter half and the half a glance is looking for. */
.dom-food .list-btn > :last-child { flex: none; }
.dom-food .card .list-btn:last-child { border-bottom: 0; }
.dom-food .list-btn.danger { color: var(--danger); }/* The fasting window. Fills toward the goal and stops - there is no "over"
   state and no colour change on approach or overshoot, because there is
   nothing here to fail. RECONCILIATION.md §S7: reversing "no fasting streaks"
   did not reverse "never shame or fear", and a bar that turns red is exactly
   the shape that line was written to rule out. *//* ⭐ A BUTTON SINCE 2026-08-27, not a div - it opens the fasting sheet.
   width:100% and display:block because the shell's button reset leaves it
   inline-block, which would shrink the bar to nothing. */
.dom-food .fast-window {
  display: block;
  position: relative;
  width: 100%;
  height: 8px;
  border-radius: 4px;
  background: var(--surface-2);
  overflow: hidden;
  margin: 10px 0 2px;
}/* An 8px bar is a 8px tap target, which is not one. The hit box grows
   vertically past the paint, the same trick .seg and .fchip already use, and
   only vertically - it has a full-width row to itself so there are no
   neighbours to steal taps from. */
.dom-food .fast-window::after {
  content: '';
  position: absolute;
  left: 0; right: 0;
  top: -18px; bottom: -18px;
}
.dom-food .fast-window-fill {
  height: 100%;
  background: var(--accent);
  border-radius: 4px;
  transition: width .3s ease;
}/* ⚠⚠ THE BENCHMARK TICKS, added 2026-08-26 at Craig's request. Read the note
   on FASTING.BENCHMARKS in js/const.js before touching any of this - these
   are the only physiological claims in the app and the framing is what keeps
   them honest.

   A tick is a HAIRLINE, not a milestone: no dot, no flag, no icon, and
   nothing appears or animates when the fill reaches one. It marks a place on
   a clock. `mix-blend-mode` is what lets one colour read against both the
   filled and unfilled halves of the bar without a second rule deciding which
   side a tick is on - and a plain colour is the fallback where it is not
   supported, which is legible either way. */
.dom-food .fast-mark {
  position: absolute;
  top: 0;
  width: 2px;
  height: 100%;
  margin-left: -1px;
  background: var(--plane);
  mix-blend-mode: normal;
}/* The legend. Wraps rather than scrolls, because three short labels on a
   375pt phone need two lines and a sideways scroller here would be a
   surface nobody would think to drag. */
.dom-food .fast-marks {
  display: flex;
  flex-wrap: wrap;
  gap: 4px 14px;
  margin: 6px 4px 0;
  font-size: 13px;
  line-height: 1.5;
  color: var(--muted);
}/* ⚠ WEIGHT AND TEXT COLOUR, NEVER AN ACCENT OR A TICK MARK. A marker the
   elapsed time has passed is a fact worth being able to see at a glance;
   making it the accent colour would make it a reward, and this app does not
   hand those out for not eating. */
.dom-food .fast-mark-on {
  color: var(--text);
  font-weight: 600;
}/* ---------- the fasting ring ----------

   ⚠⚠ IT IS A CLOCK FACE, NOT A SCOREBOARD, and every rule here exists to keep
   it one. Read the note on openFastSheet() in js/app.js before changing any
   of it. No colour changes as it fills. Nothing animates when a benchmark is
   passed. There is no "complete" state, no glow, no pulse - past the goal the
   arc simply stops, exactly as the bar on Today does. A ring is the
   close-your-rings shape and this app does not hand out rewards for not
   eating (RECONCILIATION §S7 reversed "no fasting streaks" and nothing else). */
.dom-food .ring-wrap {
  position: relative;
  width: 220px;
  max-width: calc(68vw / var(--tz, 1));
  margin: 4px auto 0;
}
.dom-food .ring { display: block; width: 100%; height: auto; }
.dom-food .ring-track {
  fill: none;
  stroke: var(--surface-2);
  stroke-width: 9;
}
.dom-food .ring-fill {
  fill: none;
  stroke: var(--accent);
  stroke-width: 9;
  stroke-linecap: round;
  /* -90deg so the arc starts at twelve o'clock: SVG angles begin east and a
     clock begins north. */
  transform: rotate(-90deg);
  transform-origin: 50% 50%;
  transition: stroke-dashoffset .4s ease;
}/* Same hairline as the ticks on the bar, and for the same reason: a marker is
   a place on a clock, not a milestone. No dot, no flag, no icon. */
.dom-food .ring-tick {
  stroke: var(--plane);
  stroke-width: 2;
}
.dom-food .ring-mid {
  position: absolute;
  inset: 0;
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 2px;
  pointer-events: none;
}/* Hours large, minutes beside them, units smaller still. Same string as
   everywhere else - "13h 24m" - just set so the number you read at a glance
   is the big one. Baseline-aligned so the units sit on the numbers' feet
   rather than floating beside their middles. *//* ⚠ NOT display:flex. Flex blockifies its children, which turned this into
   "13
h
24
m" for innerText - identical on screen, a different string to
   every reader of the page. Inline spans share a baseline for free, which is
   the only thing flex was providing here. */
.dom-food .ring-num {
  display: block;
  line-height: 1;
  white-space: nowrap;
}
.dom-food .ring-num .n { font-size: 40px; font-weight: 700; letter-spacing: -0.03em; }
.dom-food .ring-num .m { font-size: 26px; font-weight: 700; letter-spacing: -0.02em; }
.dom-food .ring-num .u { font-size: 15px; font-weight: 600; color: var(--text-2); }
.dom-food .ring-mid span { font-size: 14px; color: var(--text-2); }/* The marker most recently passed. ⚠ It is set in MUTED text at 12px, not in
   the accent and not larger - it is a caption on a clock, not a badge. *//* Sits under the ring rather than inside it - see fastRemainingLine(). */
.dom-food .ring-stage {
  display: inline-block;
  margin-top: 2px;
  font-size: 13px;
  color: var(--muted);
}/* A tick the elapsed time has passed. Wider, not coloured - the same rule the
   legend under the bar follows. */
.dom-food .ring-tick.on { stroke-width: 3; }/* ⚠⚠ THE ONLY MOVEMENT IN THE WHOLE FEATURE, AND IT IS DELIBERATELY DULL.
   The arc sweeps to its value once, when the sheet opens. That is it. There
   is no pulse that quickens near the goal, no flash when a marker is passed
   and no celebration at the end - movement that responds to progress is a
   scoreboard telling you how you are doing, and this is a clock.

   `.live` exists so a running fast can be told apart from a finished one if
   that is ever wanted; it carries no animation today, on purpose. */
.dom-food .ring-wrap {
  display: block;
  border: 0;
  background: none;
  padding: 0;
}
.dom-food .ring-wrap:active .ring-num { opacity: 0.75; }/* ⚠ REQUIRED, NOT POLITE. Someone who has asked their phone to stop animating
   things has usually asked for a reason - vestibular trouble, migraine - and
   a sweeping arc is exactly the kind of motion that setting exists for. The
   value still lands; it simply lands immediately. */
@media (prefers-reduced-motion: reduce) {
.dom-food .ring-fill { transition: none; }
}/* The hours you can pick with one tap, revealed by tapping the ring. */
.dom-food .goal-chips {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  margin: 12px 0 4px;
}
.dom-food .goal-chips[hidden] { display: none; }/* The big number at the top of the water page. Same job as the ring's middle
   - one figure, read at a glance - without pretending water has a shape to
   fill. ⚠ There is no ring here and there must not be one: a ring implies a
   target, and water has none. */
.dom-food .big-figure {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 2px;
  margin: 6px 0 14px;
}
.dom-food .big-figure b { font-size: 38px; font-weight: 700; letter-spacing: -0.03em; }
.dom-food .big-figure span { font-size: 14px; color: var(--text-2); }/* One-tap amounts. Shortcuts for typing, never portions of a target. */
.dom-food .quick-row {
  display: grid;
  grid-template-columns: repeat(4, minmax(0, 1fr));
  gap: 8px;
  margin-bottom: 14px;
}
.dom-food .quick-row .btn { width: 100%; padding: 0 4px; font-size: 14px; }/* Extend and End side by side. End is the primary because it is the one
   somebody opened this sheet to do; Extend is the quieter of the two and
   deliberately not styled as the safer choice, because neither is safer. */
.dom-food .fast-actions {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 8px;
  margin: 14px 0 12px;
}
.dom-food .fast-actions .btn { width: 100%; }/* Wraps rather than overhangs. A label beside a three-way segmented control
   does not fit on a 375pt phone - an SE, a mini, or any phone with Display
   Zoom turned on - and .scroll sets overflow-y:auto, which by the cascade
   makes the x axis auto as well. So ten pixels of overhang did not clip: it
   made the whole Settings screen pannable sideways as well as up, which reads
   as the page sliding around under your thumb in every direction at once.
   Wrapping puts the control on its own line, at full width, labels intact. */
.dom-food .row-field {
  display: flex;
  align-items: center;
  justify-content: space-between;
  flex-wrap: wrap;
  gap: 14px;
  /* Loosened 2026-08-26 with .list-btn above, same complaint: 46/6 packed the
     day's figures into a block you had to slow down to read. The two row types
     sit directly above and below each other on Today, so they have to share a
     rhythm - change one and the other follows. */
  min-height: 52px;
  padding: 9px 4px;
  border-bottom: 1px solid var(--hairline);
  font-size: 16px;
}
.dom-food .card .row-field:last-child { border-bottom: 0; }/* A settings row that is a button rather than a setting. Same rhythm as the
   rows around it, so it reads as part of the list and not bolted on. */
.dom-food .row-field.as-row {
  width: 100%;
  border-left: 0; border-right: 0; border-top: 0;
  background: none;
  color: var(--text);
  font-size: 16px;
  text-align: left;
}
.dom-food .row-field.as-row:active { background: var(--surface-2); }
.dom-food .row-go { color: var(--muted); font-size: 20px; line-height: 1; }/* An answer row carries three things across a phone's width, and the answer is
   the one that varies - a food name can run to five words. So the label keeps
   only what it needs, the value takes the rest and wraps, and the row grows
   downward rather than squeezing either. */
.dom-food .ans-row { align-items: flex-start; gap: 12px; }
.dom-food .ans-row > span:first-child { flex: 0 0 auto; color: var(--muted); }
.dom-food .ans-val {
  flex: 1 1 auto;
  min-width: 0;
  text-align: right;
  overflow-wrap: anywhere;
}
.dom-food .ans-val.unset { color: var(--muted); font-style: italic; }/* The collapsed summary, which is three answers on one line rather than one
   answer per row - so it gets the smaller type a summary deserves and stops
   fighting the label for width. A summary that takes two lines is not
   summarising. */
.dom-food .ans-sum { font-size: 14px; color: var(--muted); }
.dom-food .ans-sum.unset { font-size: 15px; }/* ---------- form controls ---------- */
.dom-food .input {
  width: 100%;
  min-height: 44px;
  padding: 10px 12px;
  border: 1px solid var(--hairline);
  border-radius: 11px;
  background: var(--surface-2);
  color: var(--text);
  font-size: 17px;
  appearance: none;
  -webkit-appearance: none;
}/* An inset ring rather than the offset one the global :focus-visible rule
   draws: a text box inside a card has no room outside itself. This one fires
   on :focus, so it shows whether the box was tapped or tabbed into. */
.dom-food .input:focus { outline: 2px solid var(--accent); outline-offset: -1px; }
.dom-food .input.num { text-align: center; padding: 10px 4px; font-variant-numeric: tabular-nums; }
.dom-food .input.area { min-height: 62px; resize: vertical; line-height: 1.4; }
.dom-food .input.search { margin-bottom: 10px; background: var(--surface); }
.dom-food select.input { background-image: none; }
.dom-food .row-field .input { width: auto; max-width: 110px; }
.dom-food .row-field .input.num { width: 82px; }
/* Audit B24: the label takes the spare room, so a box and its unit sit together on the
   right, every row the same. */
.dom-food .row-field > span:first-child { flex: 1 1 auto; }
.dom-food .fast-span { display: block; font-size: 13px; color: var(--muted); margin-top: 1px; }
/* A row with no unit carries an invisible one, so its box lines up with the rows that say "g". */
.dom-food .unit-pad { visibility: hidden; }
.dom-food .field-block { display: block; margin-bottom: 14px; }
.dom-food .field-label {
  display: block;
  margin: 0 0 6px 2px;
  font-size: 13px;
  font-weight: 600;
  color: var(--text-2);
}/* The switch itself is well under 44px, but every one of them sits inside a
   46px .row-field label, so the row is the target. */
.dom-food .switch { width: 46px; height: 28px; accent-color: var(--accent); }
.dom-food .segmented {
  display: flex;
  gap: 2px;
  padding: 2px;
  margin: 10px max(12px, env(safe-area-inset-left));
  background: var(--surface-2);
  border-radius: var(--r-sm);
}
.dom-food .segmented.small { margin: 10px 0; }
.dom-food .segmented.inline { margin: 0; width: auto; }
.dom-food .seg {
  flex: 1;
  min-height: 32px;
  padding: 0 10px;
  border-radius: 8px;
  font-size: 14px;
  font-weight: 500;
  color: var(--text-2);
  white-space: nowrap;
}
.dom-food .seg.on {
  background: var(--surface);
  color: var(--text);
  font-weight: 600;
  box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12);
}
.dom-food .filter-chips {
  display: flex;
  gap: 6px;
  overflow-x: auto;
  margin: 0 -4px 12px;
  padding: 2px 4px 6px;
  scrollbar-width: none;
}
.dom-food .filter-chips::-webkit-scrollbar { display: none; }
.dom-food .filter-chips.wrap { flex-wrap: wrap; overflow-x: visible; }/* --r-pill rather than the 16px Workout Log wrote: a 32px-high chip clamps a
   999px radius to exactly 16px, so this is the same shape under the name that
   says what it is. Same for the 28px sub-chips below. */
.dom-food .fchip {
  flex: 0 0 auto;
  min-height: 32px;
  padding: 0 13px;
  border-radius: var(--r-pill);
  background: var(--surface);
  box-shadow: var(--shadow);
  font-size: 15px;
  color: var(--text-2);
}
.dom-food .fchip.on { background: linear-gradient(180deg, var(--accent-hi), var(--accent-lo)); color: var(--accent-ink); font-weight: 600; }
.dom-food .filter-chips.sub { margin-top: -2px; }
.dom-food .filter-chips.sub .fchip { min-height: 28px; padding: 0 11px; font-size: 13px; border-radius: var(--r-pill); }/* ---------- the standing notice ----------

   Carried over from Workout Log's "learn it before you load it" block, which
   sits above the instructions on the lifts that hurt people when they are
   guessed at. It is deliberately not a red warning box: the point is
   seriousness, not alarm, and nobody should be frightened off by the app that
   exists to help them. Meal Log's safety-floor notice takes this exact shape
   for the same reason - it says a true thing plainly, once, and then lets the
   person carry on.

   The surface is --surface-2 and not the accent wash: the wash is darker, and
   it dropped the accent-coloured tag to 4.31:1 in light mode. The accent edge
   and sitting above everything else are enough to mark it out. */
.dom-food .howto-serious {
  margin: 4px 0 2px;
  padding: 11px 13px;
  border-radius: 11px;
  border-left: 3px solid var(--accent);
  background: var(--surface-2);
  font-size: 15px;
  line-height: 1.45;
  color: var(--text);
}
.dom-food .howto-serious-tag {
  display: block;
  margin-bottom: 3px;
  font-size: 11px;
  font-weight: 700;
  text-transform: uppercase;
  letter-spacing: 0.07em;
  color: var(--accent-text);
}/* ---------- sheets ---------- */
.dom-food #sheet-host { position: fixed; inset: 0; pointer-events: none; z-index: 50; }
.dom-food .backdrop {
  position: absolute;
  inset: 0;
  background: rgba(0, 0, 0, 0.35);
  opacity: 0;
  transition: opacity 0.22s ease;
  pointer-events: auto;
}
.dom-food .backdrop.in { opacity: 1; }
.dom-food .backdrop.closing { opacity: 0; }
/* A sheet takes the focus when it opens, for screen readers and keyboards (expert round 4);
   it needs no ring of its own, as the boxes and buttons inside have theirs. */
.sheet:focus { outline: none; }
.dom-food .sheet {
  position: absolute;
  left: 0;
  right: 0;
  bottom: 0;
  max-height: calc(92dvh / var(--tz, 1));
  display: flex;
  flex-direction: column;
  background: var(--plane);
  border-radius: 18px 18px 0 0;
  box-shadow: 0 -6px 30px rgba(0, 0, 0, 0.24);
  transform: translateY(100%);
  transition: transform 0.26s cubic-bezier(0.32, 0.72, 0, 1);
  pointer-events: auto;
}
.dom-food .sheet.in { transform: translateY(0); }
.dom-food .sheet.closing { transform: translateY(100%); }
.dom-food .sheet.tall { height: calc(92dvh / var(--tz, 1)); }
.dom-food .sheet-grip {
  width: 38px;
  height: 5px;
  margin: 7px auto 0;
  border-radius: 3px;
  background: var(--axis);
  flex: 0 0 auto;
}/* The grip and the header strip are the drag handle for dismissing a sheet.
   pan-x lets a horizontal chip row inside a header still scroll; what is given
   up is vertical scrolling started in that strip, which is the point. */
.dom-food .sheet-grip, .dom-food .sheet-head { touch-action: pan-x; }/* A grip you can actually pull deserves a target bigger than five pixels. */
.dom-food .sheet-grip::after {
  content: '';
  display: block;
  height: 18px;
  margin: -7px -40px -6px;
}
.dom-food .sheet-head {
  display: grid;
  grid-template-columns: 1fr auto 1fr;
  align-items: center;
  gap: 8px;
  padding: 8px 10px;
  border-bottom: 1px solid var(--hairline);
  flex: 0 0 auto;
}/* Two lines rather than an ellipsis. One nowrap line fits the short titles and
   cuts the long ones down to their first two words, which is the whole subject
   of the sheet gone. */
.dom-food .sheet-head h2 {
  margin: 0;
  font-size: 16px;
  font-weight: 600;
  text-align: center;
  line-height: 1.25;
  white-space: normal;
  overflow: hidden;
  display: -webkit-box;
  -webkit-box-orient: vertical;
  -webkit-line-clamp: 2;
  line-clamp: 2;
}
.dom-food .sheet-btn {
  min-height: 40px;
  padding: 0 8px;
  font-size: 16px;
  color: var(--accent-text);
  white-space: nowrap;
}
.dom-food .sheet-btn.ghost { text-align: left; }
.dom-food .sheet-btn.strong { text-align: right; font-weight: 650; }
.dom-food .sheet-btn.placeholder { visibility: hidden; }
.dom-food .sheet-body {
  flex: 1;
  min-height: 0;
  overflow-y: auto;
  /* Same reasoning as .scroll: overflow-y:auto alone computes overflow-x to
     auto too, and this is the one container behind every sheet in the app
     (ui.js openSheet), so anything a few pixels too wide inside any sheet
     turns that sheet into a sideways-draggable page instead of a clipped
     edge. */
  overflow-x: hidden;
  -webkit-overflow-scrolling: touch;
  padding: 14px 14px calc(20px + env(safe-area-inset-bottom));
}
.dom-food .sheet-text { margin: 4px 4px 18px; color: var(--text-2); font-size: 15px; line-height: 1.45; }
.dom-food .sheet-actions { display: flex; flex-direction: column; gap: 10px; }
.dom-food .sheet-actions .btn { width: 100%; }/* The action sheet: a short list of things you could do to whatever you were
   just looking at. */
.dom-food .action-list { display: flex; flex-direction: column; gap: 8px; }
.dom-food .action-row {
  display: flex;
  align-items: center;
  gap: 12px;
  width: 100%;
  min-height: 52px;
  padding: 0 14px;
  border-radius: 12px;
  background: var(--surface);
  box-shadow: var(--shadow);
  font-size: 16px;
  text-align: left;
}
.dom-food .action-row.danger { color: var(--danger); }
.dom-food .action-icon { font-size: 18px; width: 24px; text-align: center; }/* ---------- toast ----------

   Workout Log has a second toast, .toast.pr, gold and popping for a personal
   best. It is not here, and it must not be rebuilt: there is no number in this
   app that deserves a fanfare, and a celebration tier on an intake figure
   invents the target it then rewards you for hitting. One toast, at the same
   weight for every message, including the good ones. */
.dom-food .toast {
  position: fixed;
  left: 50%;
  bottom: calc(var(--tabbar-h) + 20px + env(safe-area-inset-bottom));
  transform: translate(-50%, 12px);
  max-width: calc(84vw / var(--tz, 1));
  padding: 10px 16px;
  border-radius: var(--r-lg);
  background: var(--text);
  color: var(--surface);
  font-size: 14px;
  text-align: center;
  opacity: 0;
  pointer-events: none;
  transition: opacity 0.2s ease, transform 0.2s ease;
  z-index: 60;
}
.dom-food .toast.show { opacity: 1; transform: translate(-50%, 0); }/* The undo toast carries a button, so it must accept taps (the plain toast is
   pointer-events: none) and lay its message and action out side by side. Every
   remove() in the store writes a tombstone rather than deleting, precisely so
   this button can exist. */
/* Only while it shows: faded out, it kept catching taps (deep check 2026-10-24). */
.dom-food .toast.has-undo.show {
  pointer-events: auto;
}
.dom-food .toast.has-undo {
  display: inline-flex;
  align-items: center;
  gap: 16px;
}
.dom-food .toast-undo {
  background: none;
  border: none;
  color: inherit;
  font: inherit;
  font-weight: 700;
  text-decoration: underline;
  padding: 2px 2px;
  cursor: pointer;
  flex: none;
}/* ---------- empty states ---------- */
.dom-food .empty { padding: 36px 12px; text-align: center; }
.dom-food .empty.lean { padding-top: 18px; }
.dom-food .empty-art { font-size: 44px; margin-bottom: 8px; }
.dom-food .empty h2 { margin: 0 0 4px; font-size: 20px; }
.dom-food .empty p { margin: 0 0 20px; color: var(--text-2); font-size: 16.5px; }
.dom-food .footer-note {
  margin: 28px 0 8px;
  text-align: center;
  font-size: 12px;
  color: var(--muted);
}/* ---------- settings ----------

   Storage: a bar so the ceiling is visible before somebody meets it, and a
   banner that stays up for as long as writes are failing. Both now read the
   real --warn token instead of the var(--warn, #8a6508) they had. */
.dom-food .store-bar {
  height: 6px;
  margin: 4px 12px 12px;
  border-radius: 3px;
  background: var(--surface-2);
  overflow: hidden;
}
.dom-food .store-fill { height: 100%; background: var(--accent); transition: width 0.3s ease; }
.dom-food .store-bar.hot .store-fill { background: var(--warn); }
.dom-food .muted-inline { color: var(--muted); font-weight: 400; font-size: 12.5px; }
.dom-food .hint.warn { color: var(--warn); }/* The write-failure banner, above the tab bar. A fixed gold in both themes:
   it is the same bad news whichever way the phone is dressed. */
.dom-food .save-warn {
  border-top: 1px solid var(--hairline);
  background: linear-gradient(180deg, #b8860b, #8a6508);
}
.dom-food .sw-inner {
  display: flex;
  align-items: center;
  gap: 10px;
  width: 100%;
  padding: 9px 14px;
  background: none;
  color: #fff;
  text-align: left;
}
.dom-food .sw-icon { font-size: 17px; flex: 0 0 auto; }
.dom-food .sw-text { display: flex; flex-direction: column; line-height: 1.25; }
.dom-food .sw-text b { font-size: 14px; }
.dom-food .sw-text span { font-size: 12.5px; opacity: 0.9; }/* ---------- trends ----------

   The chart classes and the two tokens they use are Workout Log's, verbatim
   (web/styles.css "charts"), so the two apps in the family draw the same chart
   in the same colours and a change to --grid or --axis moves both.

   ⚠ ONE COLOUR, AT ONE OPACITY, WHATEVER THE VALUE. There is deliberately no
   .bar.hot, no --warn anywhere in this block and no rule keyed to a height. A
   bar that turns amber when it gets tall is the sentence "that was too much"
   drawn instead of written, and it would slip past a copy review. If a later
   change wants a second bar colour, the answer is in CLAUDE.md and it is no. *//* The width cap, not a height cap. The SVG keeps its viewBox aspect ratio, so
   height follows width - which on a phone is the full card and on a desktop
   window would otherwise be a chart the height of the screen. 520 is about
   where a seven-column chart stops gaining anything from being wider. */
.dom-food .chart { position: relative; max-width: 520px; margin: 0 auto; }
.dom-food .chart svg { display: block; width: 100%; height: auto; overflow: visible; }
.dom-food .chart .grid { stroke: var(--grid); stroke-width: 1; }
.dom-food .chart .axis { stroke: var(--axis); stroke-width: 1; }
.dom-food .chart .axis-label { fill: var(--muted); font-size: 10px; font-variant-numeric: tabular-nums; }
.dom-food .chart .point-label {
  fill: var(--text-2);
  font-size: 11px;
  font-weight: 600;
  font-variant-numeric: tabular-nums;
}
.dom-food .chart .bar { fill: var(--accent); }
.dom-food .chart-card { padding: 14px 12px 10px; }
.dom-food .chart-head {
  display: flex;
  align-items: baseline;
  justify-content: space-between;
  gap: 10px;
  flex-wrap: wrap;
  margin-bottom: 2px;
}
.dom-food .chart-head h2 { margin: 0; font-size: 16px; font-weight: 600; }
.dom-food .chart-sub { font-size: 12px; color: var(--muted); font-variant-numeric: tabular-nums; }/* The timing bands. A track and a fill rather than a chart, because six
   horizontal rows read better on a phone than six more columns - and because
   the label has to be a clock range, which does not fit under a column. */
.dom-food .band-row { gap: 10px; }
.dom-food .band-time {
  flex: 0 0 auto;
  font-variant-numeric: tabular-nums;
  font-size: 13px;
  color: var(--text-2);
}
.dom-food .band-track {
  flex: 1 1 auto;
  height: 8px;
  border-radius: 4px;
  background: var(--surface-2);
  overflow: hidden;
}
.dom-food .band-fill { display: block; height: 100%; background: var(--accent); border-radius: 4px; }
.dom-food .band-val {
  flex: 0 0 auto;
  min-width: 34px;
  text-align: right;
  font-variant-numeric: tabular-nums;
  font-size: 13px;
  color: var(--muted);
}/* ---------- the Recovery Card ----------

   Big, monospaced, tabular and selectable, because the two things anybody does
   with it are read it aloud and copy it by hand. `user-select: all` makes one
   tap select the whole thing on the phones where the copy button is refused. */
.dom-food .reccard {
  margin: 0;
  padding: 14px 10px;
  text-align: center;
  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
  font-size: 17px;
  font-variant-numeric: tabular-nums;
  letter-spacing: 0.04em;
  line-height: 1.5;
  word-break: break-all;
  color: var(--text);
  user-select: all;
  -webkit-user-select: all;
}/* ---------- the weekly review ----------

   The invitation is the one card allowed above the day, so it is the one place
   the accent is used to say "this is an event". Still no icon, still no badge,
   still nothing that counts anything: a title, a sentence, and two equal
   answers. */
.dom-food .reflect-invite {
  display: flex;
  flex-direction: column;
  gap: 3px;
  padding: 14px;
  margin-bottom: 12px;
}
.dom-food .reflect-invite b { font-size: 16px; color: var(--accent-text); }
.dom-food .reflect-invite > span { color: var(--text-2); font-size: 14px; line-height: 1.45; }
.dom-food .reflect-invite .remind-actions { margin-top: 9px; }/* Section headings inside the sheet. Then, Now, Next - three of them, so they
   have to be legible at a glance without shouting. */
.dom-food .reflect-head {
  margin: 20px 4px 8px;
  font-size: 13px;
  font-weight: 650;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  color: var(--muted);
}
.dom-food .sheet-body .reflect-head:first-child { margin-top: 4px; }/* ---------- the React layer ----------

   Deliberately the quietest card in the app. No accent stripe, no icon, no
   heading, no border that marks it out as A Message - it is a sentence in the
   ordinary surface colour, at the ordinary text size, that happens to be
   sitting there. Anything that announced itself would be the app congratulating
   itself on teaching, which is the half of the design that is supposed to be
   invisible. */
.dom-food .react { padding: 13px 14px; }
.dom-food .react-text { margin: 0; color: var(--text-2); font-size: 14.5px; line-height: 1.5; }/* ---------- the export reminder ----------

   An ordinary card in the ordinary surface colour. Explicitly NOT .save-warn,
   which is the gold write-failure banner: this is not bad news, and dressing
   it as bad news is how a reminder becomes a nag. No icon, no accent stripe,
   no colour that says anything. */
.dom-food .remind { padding: 14px 14px 12px; }
.dom-food .remind-text { margin: 0 0 12px; color: var(--text-2); font-size: 14.5px; line-height: 1.45; }
.dom-food .remind-actions { display: flex; gap: 8px; justify-content: flex-end; flex-wrap: wrap; }/* ---------- accent palettes ---------- *//* Accent text goes darker than body text (#0b0b0b) rather than lighter, so
     an accented word reads as stronger instead of faded. */
@media (prefers-color-scheme: dark) {/* The inversion: near-white fill, near-black ink. */
}/* The inversion: near-white fill, near-black ink. *//* The accent picker: ten dots, each wearing the palette it selects. The
   swatch colour comes from the same data-accent rules the app uses, applied
   to the dot itself, so a swatch can never disagree with what it applies. */
.dom-food .accent-row { display: flex; gap: 2px; flex-wrap: wrap; margin: -7px -7px -7px 0; }/* 40px of tappable area around a 26px swatch: the colour is painted into
   the content box and the padding carries the hit target, so the dot looks
   small and behaves like every other control. */
.dom-food .accent-dot {
  width: 40px; height: 40px;
  padding: 7px;
  border-radius: 50%;
  border: 0;
  background: var(--accent);
  background-clip: content-box;
}
.dom-food .accent-dot.on {
  box-shadow: inset 0 0 0 2px var(--text-2);
}
.dom-food .accent-dot[data-accent-swatch="ember"] { background-color: #c43f0b; }
.dom-food .accent-dot[data-accent-swatch="ocean"] { background-color: #0b6ea8; }
.dom-food .accent-dot[data-accent-swatch="forest"] { background-color: #2a7a3f; }
.dom-food .accent-dot[data-accent-swatch="plum"] { background-color: #8a3d8f; }
.dom-food .accent-dot[data-accent-swatch="crimson"] { background-color: #c02b3f; }
.dom-food .accent-dot[data-accent-swatch="slate"] { background-color: #4a5b70; }
.dom-food .accent-dot[data-accent-swatch="gold"] { background-color: #8a6410; }
.dom-food .accent-dot[data-accent-swatch="teal"] { background-color: #0f7a75; }
.dom-food .accent-dot[data-accent-swatch="pink"] { background-color: #c3245f; }/* A near-black swatch on a near-white row needs no outline; the one in dark
   mode does, or a near-white dot floats with no edge. */
.dom-food .accent-dot[data-accent-swatch="black"] { background-color: #111111; }
@media (prefers-color-scheme: dark) {
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="ember"] { background-color: #f97b22; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="ocean"] { background-color: #3f6b91; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="forest"] { background-color: #4c7a5c; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="plum"] { background-color: #c176c6; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="crimson"] { background-color: #ef6274; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="slate"] { background-color: #8ea4bf; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="gold"] { background-color: #d9a63c; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="teal"] { background-color: #3fbdb4; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="pink"] { background-color: #f07aa6; }
html:where(:not([data-theme="light"])) .dom-food .accent-dot[data-accent-swatch="black"] { background-color: #f2f2ef; }
}
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="ember"] { background-color: #f97b22; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="ocean"] { background-color: #3f6b91; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="forest"] { background-color: #4c7a5c; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="plum"] { background-color: #c176c6; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="crimson"] { background-color: #ef6274; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="slate"] { background-color: #8ea4bf; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="gold"] { background-color: #d9a63c; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="teal"] { background-color: #3fbdb4; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="pink"] { background-color: #f07aa6; }
html[data-theme="dark"] .dom-food .accent-dot[data-accent-swatch="black"] { background-color: #f2f2ef; }/* ---------- motion ----------

   Deliberately almost nothing. An app somebody opens with a fork in the other
   hand should never make them wait, so every duration here is under a fifth of
   a second and all of it is switched off by the block at the end of the file. *//* Changing tabs. A cross-fade only when the view genuinely changed. */
@keyframes food-view-in { from { opacity: 0; } to { opacity: 1; } }
.dom-food #main.view-in { animation: food-view-in 0.14s ease-out; }/* Something arriving. Only ever on the row that was actually just added - a
   blanket rule would replay on every re-render, which is most keystrokes. */
@keyframes food-rise-in {
  from { opacity: 0; transform: translateY(6px); }
  to   { opacity: 1; transform: none; }
}
.dom-food .fresh { animation: food-rise-in 0.18s ease-out; }
@media (prefers-reduced-motion: reduce) {
.dom-food * { transition-duration: 0.01ms !important; animation-duration: 0.01ms !important; }
}/* ---------- the title card ----------

   Same construction as Workout Log's, so the two apps open the same way: an
   ember ground borrowed from the icon's own tokens, a mark that draws itself,
   and a name that rises after it. The ground is --icon-hi/--icon-lo rather than
   --accent, which is why it stays ember in dark mode and under every accent -
   the icon on the home screen is ember whatever the phone is set to, and the
   card that follows it has to be too.

   Dismissed by a CSS animation and not by script, so it still clears itself if
   the app fails to boot at all. A splash that outlives a crash is how a broken
   app looks like a hung one. *//* Been here in the last half hour: no card, no wait. *//* The handle, drawn downward - the direction a fork is picked up. *//* The head, set across it. *//* The tines, rising out of the head, outside pair first. *//* Full cream, not a dimmed one, and this is a correction rather than a
   preference. Workout Log carries the finding in its own stylesheet: at
   14.5px this counts as body text for the contrast rules, and cream at 88%
   over the accent lands between 4.02 and 4.40 across the ten palettes - under
   the 4.5 line the rest of the app is held to. This card was inheriting the
   look without the fix and sat at 0.85, which is worse than the value Workout
   Log rejected. The size and the weight already say it is secondary. *//* One word per beat, because the line is three beats. Same delays as Workout
   Log and Mellow, so the three cards keep time with each other. *//* Somebody who has asked for less movement gets the card without the
   choreography - it still appears, it just stops performing. */
@media (prefers-reduced-motion: reduce) {
}

/* Your usual foods (decision 0026). */
.dom-food .usual-invite{ display:grid; gap:4px; width:100%; text-align:left; padding:14px 16px; cursor:pointer; font:inherit; color:inherit; }
.dom-food .usual-invite-t{ font-weight:700; }
.dom-food .usual-head{ display:flex; justify-content:space-between; align-items:baseline; gap:10px; }
.dom-food .usual-add{ background:none; border:0; font:inherit; font-weight:600; color:var(--accent-text, var(--accent)); min-height:44px; cursor:pointer; }
.dom-food .usual-remove{ background:none; border:0; font-size:20px; line-height:1; width:44px; min-height:44px; color:inherit; opacity:.55; cursor:pointer; }
.dom-food .usual-review{ list-style:none; padding:0; margin:8px 0 0; display:grid; gap:6px; }
.dom-food .usual-pick, .usual-pick{ display:flex; gap:10px; align-items:center; justify-content:space-between; min-height:44px; }
.usual-pick input{ width:22px; height:22px; flex:none; accent-color:var(--accent); }
.usual-pick span:first-of-type{ flex:1; }
.usual-text{ width:100%; font:inherit; }

/* The goal form from one sentence (decision 0026). */
.goal-words{ display:grid; gap:8px; margin:0 0 14px; padding:0 0 14px; border-bottom:1px solid var(--edge-strong, rgba(0,0,0,.12)); }
.goal-words-text{ width:100%; font:inherit; }
.goal-fill{ justify-self:start; min-height:44px; }
.goal-words .hint:empty{ display:none; }

/* Saved things and restaurants (decision 0041). The pencil is drawn by CSS, like the star. */
.dom-food .saved-edit, .saved-edit{ background:none; border:0; width:44px; min-height:44px; color:inherit; opacity:.6; cursor:pointer; font-size:16px; }
.dom-food .saved-edit::before, .saved-edit::before{ content:'\270E'; }
.dom-food .saved-edit:focus-visible, .saved-edit:focus-visible{ outline:2px solid var(--accent); outline-offset:-4px; border-radius:8px; }
.dom-food .saved-sub, .saved-sub{ display:block; font-size:12.5px; opacity:.7; margin-top:1px; font-weight:400; }
.dom-food .saved-tag, .saved-tag{ font-size:10.5px; font-weight:800; letter-spacing:.04em; text-transform:uppercase; padding:2px 6px; border-radius:6px; background:rgba(127,127,127,.15); opacity:.85; margin-left:4px; vertical-align:2px; }
.dish-nums{ display:grid; grid-template-columns:repeat(4, minmax(0,1fr)); gap:8px; margin:0 0 6px; }
.dish-num{ display:grid; gap:4px; font-size:12px; font-weight:700; opacity:.85; }
.dish-num .input{ width:100%; text-align:center; }
.dish-actions{ display:flex; gap:8px; flex-wrap:wrap; margin-top:14px; }
.dish-actions .btn{ flex:1; min-height:44px; }
.dish-hist{ margin-top:10px; }
.dish-build{ background:none; border:0; padding:0; min-height:44px; font:inherit; font-weight:600; color:var(--accent-text, var(--accent)); cursor:pointer; }
