/*
 * Chomp API documentation overhaul
 * ---------------------------------------------------------------------------
 * Load order matters: this file must be loaded AFTER the pinned Stoplight
 * Elements stylesheet (@stoplight/elements 9.0.29). It replaces the inline
 * overrides in views/public/api/docs/interactive.html.
 *
 * Design contract:
 * - Inter everywhere; JetBrains-style system mono stack for code.
 * - Slate is the working surface. Blue is the action color.
 * - Pink and violet appear only in the masthead accent/quick-start art.
 * - The reference is an opaque, light workspace, not a glass marketing card.
 * - Dark slate is reserved for code and response payloads.
 *
 * Round 2 (post-render review):
 * - Masthead title fits one line; the chips row and its styles are gone.
 * - The workspace band breaks out wider than the 80rem page column.
 * - The bundle's inverted Try It region is re-pinned to the light palette
 *   (see the .sl-inverted block in the round-2 section below).
 *
 * Round 3 (post-render review):
 * - One wide band: the page column itself is min(110rem, 100vw - 3rem),
 *   so the nav (separate scoped rule below), the masthead, and the
 *   console all share one width; the round-2 workspace breakout is gone.
 * - Masthead restructured: the hero card spans the full width and the
 *   quick-start panel is a horizontal strip under it (three step columns
 *   + a one-line base-URL bar), so no column pairing sets band height.
 * - Try It rail contrast pass + light portal menus (round-3 section).
 *
 * Round 4 (design pass, Peter's design grant):
 * - The masthead gains a brand-tinted atmosphere: a second radial glow,
 *   a deeper frame shadow, and a hairline gradient rule under the hero
 *   that ties it to the steps strip.
 * - Steps strip: step discs get a gradient face and a soft ring; each
 *   step column gets a hairline top accent, so the three columns read
 *   as one designed row rather than three loose items.
 * - Console frame: the toolbar and shell share one frame shadow; the
 *   toolbar gains the same faint brand tint as the hero card and a
 *   gradient mark chip.
 * - Micro-polish: brand selection color on the masthead and strip,
 *   page-level horizontal scrollbar, a slightly stronger focus ring,
 *   two layout-only rhythm tweaks (hero intro measure, panel spacing).
 * - Everything from rounds 1–3 is preserved; round 4 only adds.
 *
 * Round 5 (Peter's re-test of round 3, 2026-11-10 — 7 findings):
 * - The eyebrow line is gone (template) and its two rules are deleted;
 *   the masthead H1 renders in title case via text-transform.
 * - The nav rule is REPLACED: the header is centered on the viewport at
 *   the band's width with square ends — full-bleed, this page only.
 * - The console flattens to one surface per panel: the bundle's inner
 *   panel fill is neutralized, and bordered boxes nested inside panels
 *   (the Security scheme description box is the named instance) lose
 *   their border, margin, and padding.
 * - Parameter rows lose their colon cells and tighten to two columns.
 * - Responses becomes one header bar: title and status tabs share one
 *   continuous underline; the active tab is a filled chip.
 * - The PathCrumbs bar and the schema description get real vertical
 *   rhythm (0.75rem spaces below each).
 * - The Send button is white-on-blue in every state — the round-3 color
 *   pins are re-asserted at winning specificity.
 * - Portal menus: the round-3 child combinator is replaced with a
 *   descendant one — the main menu list is a grandchild of the popover
 *   (mosaic's MenuList wraps it in a VStack), so the light system never
 *   reached it. Main menu and submenus now share one treatment.
 * - Round 4 folds in whole; the only conflict (its panel spacing note)
 *   resolves in round 5's favor — panel spacing itself is unchanged.
 */

.chomp-docs-page {
  --chomp-blue: #3b82f6;
  --chomp-blue-dark: #2563eb;
  --chomp-blue-darker: #1d4ed8;
  --chomp-pink: #ec4899;
  --chomp-violet: #8b5cf6;
  --chomp-slate-50: #f8fafc;
  --chomp-slate-100: #f1f5f9;
  --chomp-slate-200: #e2e8f0;
  --chomp-slate-300: #cbd5e1;
  --chomp-slate-400: #94a3b8;
  --chomp-slate-500: #64748b;
  --chomp-slate-600: #475569;
  --chomp-slate-700: #334155;
  --chomp-slate-900: #0f172a;
  --chomp-slate-950: #020617;
  --chomp-docs-shadow: 0 24px 60px -32px rgb(15 23 42 / 0.28);
  --chomp-docs-radius: 1.5rem;
  /* Round 4: atmosphere tokens for the masthead and console frame. */
  --chomp-docs-hero-glow-blue: rgb(59 130 246 / 0.14);
  --chomp-docs-hero-glow-pink: rgb(236 72 153 / 0.1);
  --chomp-docs-frame-shadow: 0 30px 70px -34px rgb(15 23 42 / 0.3);
  width: min(110rem, calc(100vw - 3rem));
  max-width: none;
  margin-right: auto;
  margin-left: auto;
  padding: 8rem 0 6rem;
  color: var(--chomp-slate-700);
  font-family: "Inter", system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
}

/* Round 5 — REPLACED (finding 3: full-bleed nav). Round 3's rule only
 * lifted the pill's max-width cap; Peter's 2026-11-10 re-test shows the
 * header still rendering as a centered pill at ~85% of the viewport
 * width while the page band spans ~95% — the cap lifted, the pill
 * framing stayed. This rule replaces it (same selector, same count:
 * 1 → 1). The header is positioned against the viewport at exactly the
 * band's width — min(110rem, 100vw - 3rem), the .chomp-docs-page value
 * above — centered with left: 50% + translateX(-50%), which holds
 * regardless of the template's own mx-auto centering, and the pill's
 * fully rounded ends are squared to a 1rem radius so the bar reads as
 * a bar spanning the band, not a pill stretched across it.
 * Caveats, stated plainly: the header markup is INFERRED — the round-1
 * prep established a fixed nav pairing max-w-7xl with mx-auto at
 * views/template-api-v2.html lines 177–180, and the re-test screenshot
 * confirms the rounded caps render on the nav bar element itself. If
 * an ancestor of the nav establishes a containing block (a transform or
 * filter on a wrapper), left: 50% centers on that ancestor instead of
 * the viewport, and if the pill radius ever moves to a child wrapper,
 * the radius override misses it. The shared template stays untouched;
 * every other page keeps the pill, because no other page loads this
 * stylesheet. */
body > header nav.rounded-full {
  width: min(110rem, calc(100vw - 3rem));
  max-width: none;
  /* Round 7: Peter's round-6 verdict — the bar spans the band but
   * must keep the SAME styling as every other page's nav: the pill.
   * Round 6's hero-card radius (1.75rem) override is REMOVED; the
   * capsule value the template's rounded-full compiles to is
   * restored explicitly so the wide bar keeps capsule ends. */
  border-radius: 9999px;
}

/* The fixed header itself carries p-4 (1rem on every side), which
 * INSETS the nav by 1rem on each side of the band. Zeroing its
 * horizontal padding on this page lets the nav span the band edge to
 * edge; the vertical padding is untouched, so the bar keeps its
 * clearance above the page. */
body > header.fixed {
  padding-right: 0;
  padding-left: 0;
}

/* --------------------------------------------------------------------------
 * Masthead
 * ------------------------------------------------------------------------ */

/* Round 3: the masthead is a vertical stack — hero card, then the
 * quick-start strip. No grid columns pair the two blocks, so neither
 * block's height can stretch, shrink, or strand the other; each band is
 * exactly as tall as its own content. */
.chomp-docs-masthead {
  position: relative;
  display: flex;
  flex-direction: column;
  gap: 1.25rem;
  margin-bottom: 1.25rem;
}

/* Round 4: a hairline gradient rule under the masthead, centered and
 * narrower than the band — the visual hand-off from the masthead to
 * the console. Blue-to-violet echoing the hero card's left edge; it
 * sits in the existing margin, so no spacing changes. */
.chomp-docs-masthead::after {
  position: absolute;
  right: 12%;
  bottom: -1.25rem;
  left: 12%;
  height: 1px;
  background: linear-gradient(90deg, transparent, var(--chomp-blue), var(--chomp-violet), transparent);
  opacity: 0.35;
  content: "";
}

.chomp-docs-masthead__main {
  position: relative;
  overflow: hidden;
  /* Round 3: tighter block padding — the card is one band of a stack now,
   * not half of a two-column hero, so the tall-card padding goes. */
  padding: clamp(1.75rem, 3vw, 2.5rem);
  border: 1px solid #dbe7f5;
  border-radius: calc(var(--chomp-docs-radius) + 0.25rem);
  /* Round 4: a second radial glow joins the violet one — brand blue from
   * the lower-left, pink washing the far corner — so the card has a
   * tinted atmosphere rather than one corner spot; both sit under the
   * linear wash and stay faint. Tokens only, no new raw values. */
  background:
    radial-gradient(circle at 88% -18%, rgb(139 92 246 / 0.16), transparent 34%),
    radial-gradient(circle at -12% 112%, var(--chomp-docs-hero-glow-blue), transparent 46%),
    radial-gradient(circle at 104% 108%, var(--chomp-docs-hero-glow-pink), transparent 42%),
    linear-gradient(135deg, #ffffff 0%, #f8fbff 58%, #fdf7ff 100%);
  /* Round 4: the hero frame shadow deepens to the frame token, so the
   * masthead and the console below share one depth language. */
  box-shadow: var(--chomp-docs-frame-shadow);
}

.chomp-docs-masthead__main::before {
  position: absolute;
  inset: 0 auto 0 0;
  width: 0.3125rem;
  background: linear-gradient(180deg, var(--chomp-blue), var(--chomp-violet), var(--chomp-pink));
  content: "";
}

/* Round 5: the eyebrow rules are deleted with the element itself
 * (finding 1 — Peter removed the line and its dot from the template;
 * the ::before rule below it carried the gradient dot he objected to).
 * Two rules removed, 2 → 0, deliberately. */

.chomp-docs-masthead h1 {
  margin: 0;
  color: var(--chomp-slate-900);
  /* Round 3: the hero is full-band now. At 110rem the 5.6vw term would
   * pin the size to the 4.6rem cap and "API documentation" fits one line
   * with room to spare (17 glyphs at ~0.52em average advance ≈ 67rem at
   * the cap, inside the ~103rem text column); at the old 80rem band the
   * round-2 clamp already fit, and the wider band only adds room. The
   * cap stays so the title never outgrows the card on very wide screens.
   * text-wrap: balance is removed: with wrapping designed out at desktop
   * widths, balance could re-break a one-line fit into two balanced
   * lines on engines that pre-wrap before measuring.
   * Round 5: text-transform: capitalize renders the title in title case
   * ("API Documentation") without touching the spec. Disclosure: the
   * staged template in fact hard-codes the string "API documentation"
   * in this H1 — the brief for this round directed the CSS treatment so
   * the spec stays untouched, and this selector is masthead-scoped, so
   * the treatment reaches this H1 and nothing else; the console's own
   * spec-driven headings render outside .chomp-docs-masthead. */
  font-size: clamp(2.6rem, 5.6vw, 4.6rem);
  font-weight: 800;
  letter-spacing: -0.055em;
  line-height: 0.96;
  text-transform: capitalize;
}

.chomp-docs-intro {
  /* Round 3: the hero is full-band now, so the intro may run wider than
   * the old half-card measure; 62rem keeps the line length readable.
   * Round 4: trimmed to 58rem — at the full 110rem band 62rem read as a
   * paragraph adrift; the tighter measure groups the title, intro,
   * and buttons into one block. Layout only, no type change. (Round 5:
   * the eyebrow that used to open that list is removed.) */
  max-width: 58rem;
  margin: 1.35rem 0 0;
  color: var(--chomp-slate-600);
  font-size: clamp(1rem, 1.5vw, 1.125rem);
  font-weight: 500;
  line-height: 1.75;
}

.chomp-docs-actions {
  display: flex;
  flex-wrap: wrap;
  gap: 0.75rem;
  margin-top: 1.75rem;
}

.chomp-docs-button {
  display: inline-flex;
  min-height: 2.9rem;
  align-items: center;
  justify-content: center;
  gap: 0.55rem;
  padding: 0.72rem 1.1rem;
  border: 1px solid transparent;
  border-radius: 9999px;
  font-size: 0.9rem;
  font-weight: 750;
  line-height: 1;
  text-decoration: none;
  transition: background-color 160ms ease, border-color 160ms ease, color 160ms ease, box-shadow 160ms ease;
}

.chomp-docs-button--primary {
  background: var(--chomp-blue);
  box-shadow: 0 12px 24px -14px rgb(37 99 235 / 0.75);
  color: #ffffff;
}

.chomp-docs-button--primary:hover {
  background: var(--chomp-blue-dark);
  color: #ffffff;
  /* Round 4: the primary lifts on hover — the shadow deepens and widens
   * (no transform, so nothing shifts layout). */
  box-shadow: 0 16px 30px -14px rgb(37 99 235 / 0.85);
}

.chomp-docs-button--secondary {
  border-color: var(--chomp-slate-300);
  background: #ffffff;
  color: var(--chomp-slate-700);
}

.chomp-docs-button--secondary:hover {
  border-color: #93c5fd;
  background: #eff6ff;
  color: var(--chomp-blue-darker);
  /* Round 4: a whisper of shadow so both hero buttons respond on hover,
   * the secondary staying the quieter of the two. */
  box-shadow: 0 8px 18px -12px rgb(37 99 235 / 0.45);
}

.chomp-docs-version-switcher {
  display: inline-flex;
  gap: 0.25rem;
  margin-top: 1.5rem;
  padding: 0.25rem;
  border: 1px solid var(--chomp-slate-200);
  border-radius: 9999px;
  background: rgb(255 255 255 / 0.9);
}

.chomp-docs-version-switcher a {
  padding: 0.48rem 0.9rem;
  border-radius: 9999px;
  color: var(--chomp-slate-600);
  font-size: 0.85rem;
  font-weight: 750;
  line-height: 1;
  text-decoration: none;
}

.chomp-docs-version-switcher a:hover {
  color: var(--chomp-slate-900);
}

.chomp-docs-version-switcher a[aria-current="page"] {
  background: var(--chomp-slate-900);
  color: #ffffff;
}

/* --------------------------------------------------------------------------
 * Quick-start panel
 * ------------------------------------------------------------------------ */

/* Round 3: the panel is a horizontal strip under the hero, not a side
 * column. Same dark treatment, one band: a top bar (Start here + base
 * URL), the three steps as columns, and the sign-in note as a one-line
 * footer. Its height is its content's height — nothing pairs with it. */
.chomp-docs-quickstart {
  display: flex;
  min-width: 0;
  flex-direction: column;
  padding: clamp(1.35rem, 2.5vw, 1.75rem);
  overflow: hidden;
  border: 1px solid #1e293b;
  border-radius: calc(var(--chomp-docs-radius) + 0.25rem);
  background:
    radial-gradient(circle at 100% 0%, rgb(59 130 246 / 0.34), transparent 38%),
    linear-gradient(150deg, #162033 0%, var(--chomp-slate-900) 58%, #1e1b4b 100%);
  box-shadow: 0 18px 44px -30px rgb(2 6 23 / 0.75);
  color: #e2e8f0;
}

.chomp-docs-quickstart__bar {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: space-between;
  gap: 0.6rem 1.5rem;
  margin-bottom: 1.25rem;
}

.chomp-docs-quickstart__heading {
  display: flex;
  align-items: center;
  gap: 1rem;
}

.chomp-docs-quickstart__heading strong {
  color: #ffffff;
  font-size: 0.78rem;
  font-weight: 800;
  letter-spacing: 0.13em;
  text-transform: uppercase;
}

.chomp-docs-quickstart__live {
  display: inline-flex;
  align-items: center;
  gap: 0.42rem;
  color: #bfdbfe;
  font-size: 0.75rem;
  font-weight: 700;
  white-space: nowrap;
}

.chomp-docs-quickstart__live::before {
  width: 0.5rem;
  height: 0.5rem;
  border-radius: 9999px;
  background: #34d399;
  box-shadow: 0 0 0 0.25rem rgb(52 211 153 / 0.15);
  content: "";
}

/* Round 3: three steps as columns inside the strip (the responsive
 * rules below stack them under 1100px). */
.chomp-docs-steps {
  display: grid;
  grid-template-columns: repeat(3, minmax(0, 1fr));
  gap: 1.15rem 2rem;
  margin: 0;
  padding: 0;
  list-style: none;
}

.chomp-docs-steps li {
  display: grid;
  grid-template-columns: 2.2rem minmax(0, 1fr);
  gap: 0.85rem;
  align-items: start;
  /* Round 4: each step column carries a short hairline accent above it,
   * so the three columns read as one designed row. Padding makes room
   * for the line without moving the text. */
  padding-top: 0.55rem;
  border-top: 1px solid rgb(147 197 253 / 0.25);
}

.chomp-docs-steps__number {
  display: inline-flex;
  width: 2.2rem;
  height: 2.2rem;
  align-items: center;
  justify-content: center;
  border: 1px solid rgb(147 197 253 / 0.42);
  border-radius: 9999px;
  /* Round 4: the disc face goes from flat tint to a blue-to-violet
   * wash, with a soft outer ring — the numbers read as designed
   * markers, echoing the hero's gradient edge. */
  background: linear-gradient(135deg, rgb(59 130 246 / 0.32), rgb(139 92 246 / 0.22));
  box-shadow: 0 0 0 0.22rem rgb(59 130 246 / 0.1);
  color: #bfdbfe;
  font-size: 0.82rem;
  font-weight: 800;
}

.chomp-docs-steps strong {
  display: block;
  margin: 0.12rem 0 0.28rem;
  color: #ffffff;
  font-size: 0.98rem;
  font-weight: 750;
  line-height: 1.3;
}

.chomp-docs-steps p {
  margin: 0;
  color: #b6c2d2;
  font-size: 0.9rem;
  line-height: 1.55;
}

/* Round 3: the base URL is a compact one-line row in the strip's top
 * bar (it was a full-width block under the steps, and its
 * overflow-wrap: anywhere let it break mid-token — the 3:46 PM
 * screenshot shows it wrapping as ".../api/v/2"). Deliberate treatment:
 * white-space: nowrap + min-width: 0 + overflow hidden with an ellipsis
 * on the code element — truncation-safe by design: on a viewport too
 * narrow for the whole URL the tail clips with an ellipsis instead of
 * breaking the token; at desktop widths the full URL always fits (the
 * row is ~16rem of mono at 0.78rem inside a 110rem band). */
.chomp-docs-base-url {
  display: flex;
  min-width: 0;
  align-items: baseline;
  gap: 0.6rem;
  margin: 0;
  padding: 0.5rem 0.8rem;
  border: 1px solid rgb(148 163 184 / 0.28);
  border-radius: 0.9rem;
  background: rgb(255 255 255 / 0.07);
  color: #dbeafe;
  font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
  font-size: 0.78rem;
  line-height: 1.4;
  white-space: nowrap;
}

.chomp-docs-base-url span {
  flex: none;
  color: #93c5fd;
  font-family: "Inter", system-ui, sans-serif;
  font-size: 0.68rem;
  font-weight: 800;
  letter-spacing: 0.16em;
  text-transform: uppercase;
}

.chomp-docs-base-url code {
  min-width: 0;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
}

/* Round 3: the note is a one-line footer of the strip (icon chip + a
 * single paragraph with the strong lead inline — the template markup
 * changed to match), separated from the steps by a hairline. */
.chomp-docs-auth-state {
  display: flex;
  gap: 0.8rem;
  align-items: center;
  margin-top: 1.25rem;
  padding-top: 1rem;
  border-top: 1px solid rgb(148 163 184 / 0.22);
}

.chomp-docs-auth-state i {
  display: inline-flex;
  width: 2rem;
  height: 2rem;
  flex: 0 0 auto;
  align-items: center;
  justify-content: center;
  border-radius: 9999px;
  background: rgb(236 72 153 / 0.16);
  color: #f9a8d4;
}

.chomp-docs-auth-state strong {
  color: #ffffff;
  font-weight: 750;
}

.chomp-docs-auth-state p {
  margin: 0;
  color: #aebdd1;
  font-size: 0.88rem;
  line-height: 1.5;
}

/* Launch-window addition (change list Change 7): the quick-start
 * panel's AI-assistant route. Rendered only once /api/guides/
 * is live; the rules are inert until the markup exists. */
.chomp-docs-ai-route {
  margin-top: 1.4rem;
  padding-top: 1.4rem;
  border-top: 1px solid rgb(148 163 184 / 0.22);
}

.chomp-docs-ai-route strong {
  display: block;
  color: #ffffff;
  font-size: 0.92rem;
  font-weight: 750;
}

.chomp-docs-ai-route p {
  margin: 0.2rem 0 0;
  color: #aebdd1;
  font-size: 0.85rem;
  line-height: 1.5;
}

.chomp-docs-ai-route__links {
  display: flex;
  flex-wrap: wrap;
  gap: 0.45rem;
  align-items: baseline;
}

.chomp-docs-ai-route__links a {
  color: #bfdbfe;
  font-weight: 650;
  text-decoration: none;
}

.chomp-docs-ai-route__links a:hover {
  color: #dbeafe;
  text-decoration: underline;
  text-underline-offset: 0.22em;
}

/* --------------------------------------------------------------------------
 * Workspace toolbar and shell
 * ------------------------------------------------------------------------ */

/* Round 3: the round-2 breakout (left: 50% + translateX(-50%) widening
 * this block out of an 80rem column) is gone. The page container itself
 * is now the 110rem band (see .chomp-docs-page), so the workspace is a
 * plain full-width block of the column — same rendered width the
 * transform produced, without the positioning machinery. */
.chomp-docs-workspace {
  width: 100%;
  min-width: 0;
}

.chomp-docs-toolbar {
  display: flex;
  min-height: 4.5rem;
  align-items: center;
  justify-content: space-between;
  gap: 1rem;
  padding: 0.85rem 1rem 0.85rem 1.25rem;
  border: 1px solid var(--chomp-slate-200);
  border-bottom: 0;
  border-radius: var(--chomp-docs-radius) var(--chomp-docs-radius) 0 0;
  /* Round 4: the toolbar takes the hero card's faint brand wash, so the
   * console frame reads as part of the same surface family. */
  background: linear-gradient(120deg, #ffffff 0%, #f8fbff 60%, #fdf7ff 130%);
  /* Round 4: the top half of the console frame shadow (the shell rule
   * below carries the same token for the rest); the two halves join at
   * the toolbar/shell seam. */
  box-shadow: var(--chomp-docs-frame-shadow);
}

.chomp-docs-toolbar__identity {
  display: flex;
  min-width: 0;
  align-items: center;
  gap: 0.85rem;
}

.chomp-docs-toolbar__mark {
  display: inline-flex;
  width: 2.65rem;
  height: 2.65rem;
  flex: 0 0 auto;
  align-items: center;
  justify-content: center;
  border-radius: 0.85rem;
  /* Round 4: the mark chip takes a blue tint gradient instead of the
   * flat tint — same family as the step discs. */
  background: linear-gradient(135deg, #eff6ff, #e0eaff);
  color: var(--chomp-blue-dark);
}

.chomp-docs-toolbar strong {
  display: block;
  color: var(--chomp-slate-900);
  font-size: 0.98rem;
  font-weight: 800;
  line-height: 1.25;
}

.chomp-docs-toolbar__identity p {
  margin: 0.15rem 0 0;
  color: var(--chomp-slate-500);
  font-size: 0.84rem;
  line-height: 1.4;
}

.chomp-docs-toolbar__meta {
  display: inline-flex;
  flex: 0 0 auto;
  flex-wrap: wrap;
  align-items: center;
  justify-content: flex-end;
  gap: 0.5rem 0.75rem;
  color: var(--chomp-slate-500);
  font-size: 0.8rem;
  font-weight: 650;
}

.chomp-docs-toolbar__meta a {
  color: var(--chomp-blue-darker);
  font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;
  font-size: 0.78rem;
  text-decoration: none;
}

.chomp-docs-toolbar__meta a:hover {
  text-decoration: underline;
  text-underline-offset: 0.2em;
}

.chomp-docs-shell {
  overflow: hidden;
  border: 1px solid var(--chomp-slate-200);
  border-radius: 0 0 var(--chomp-docs-radius) var(--chomp-docs-radius);
  background: #ffffff;
  /* Round 4: the frame token (see the toolbar rule) — one defined
   * frame for the whole console. */
  box-shadow: var(--chomp-docs-frame-shadow);
}

/* --------------------------------------------------------------------------
 * Stoplight Elements theme bridge — Elements 9.0.29 variable names
 * ------------------------------------------------------------------------ */

.chomp-docs-console {
  background: #ffffff;
  color: var(--chomp-slate-700);
  font-family: "Inter", system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
  isolation: isolate;
}

.chomp-docs-console elements-api {
  display: block;
  min-height: 44rem;
  background: #ffffff;

  --font-ui: "Inter", system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
  --font-mono: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", monospace;
  --font-code: var(--font-mono);

  --color-canvas: #ffffff;
  --color-canvas-50: #f8fafc;
  --color-canvas-100: #f1f5f9;
  --color-canvas-200: #e2e8f0;
  --color-canvas-300: #cbd5e1;
  --color-canvas-400: #94a3b8;
  --color-canvas-500: #64748b;
  --color-canvas-dark: #0f172a;
  --color-canvas-pure: #020617;
  --color-canvas-tint: #eff6ff;
  --color-canvas-dialog: #ffffff;

  --color-text: #334155;
  --color-text-heading: #0f172a;
  --color-text-paragraph: #475569;
  --color-text-muted: #64748b;
  --color-text-light: #94a3b8;
  --color-text-disabled: #94a3b8;
  --color-text-link: #1d4ed8;
  --color-text-code: #1d4ed8;

  --color-border: #cbd5e1;
  --color-border-light: #e2e8f0;
  --color-border-dark: #94a3b8;
  --color-border-input: #cbd5e1;
  --color-border-button: #cbd5e1;

  --color-primary: #3b82f6;
  --color-primary-light: #60a5fa;
  --color-primary-dark: #2563eb;
  --color-primary-darker: #1d4ed8;
  --color-primary-tint: #eff6ff;
  --color-text-primary: #1d4ed8;
  --color-on-primary: #ffffff;

  /* Semantic action/result colors stay conventional; only their tints and
   * text shades are pulled toward the slate/blue system. */
  --color-success: #059669;
  --color-success-light: #34d399;
  --color-success-dark: #047857;
  --color-success-darker: #065f46;
  --color-success-tint: #ecfdf5;
  --color-on-success: #ffffff;
  --color-text-success: #047857;

  --color-warning: #d97706;
  --color-warning-light: #fbbf24;
  --color-warning-dark: #b45309;
  --color-warning-darker: #92400e;
  --color-warning-tint: #fffbeb;
  --color-on-warning: #ffffff;
  --color-text-warning: #92400e;

  --color-danger: #e11d48;
  --color-danger-light: #fb7185;
  --color-danger-dark: #be123c;
  --color-danger-darker: #881337;
  --color-danger-tint: #fff1f2;
  --color-on-danger: #ffffff;
  --color-text-danger: #be123c;

  --color-code: #dbeafe;
  --color-on-code: #0f172a;

  --shadow-sm: 0 1px 2px rgb(15 23 42 / 0.06);
  --shadow-md: 0 8px 20px -12px rgb(15 23 42 / 0.24);
  --shadow-lg: 0 18px 38px -20px rgb(15 23 42 / 0.3);
  --shadow-xl: 0 24px 54px -24px rgb(15 23 42 / 0.34);
  --shadow-2xl: 0 32px 70px -28px rgb(15 23 42 / 0.4);
  --shadow-inner: inset 0 1px 2px rgb(15 23 42 / 0.06);

  /* Compatibility bridge for any late-rendered 8.x-style utility in a cached
   * fragment. Elements 9 uses the --color-canvas names above. */
  --color-bg-canvas: var(--color-canvas);
  --color-bg-canvas-100: var(--color-canvas-100);
  --color-bg-canvas-200: var(--color-canvas-200);
  --color-bg-canvas-dark: var(--color-canvas-dark);
  --border-color: var(--color-border);
}

/* Root scale: the bundle defaults .sl-elements to 13px and compresses schema
 * descriptions further. Documentation is the product here, so restore a
 * readable documentation scale without inflating the whole app. */
.chomp-docs-console .sl-elements {
  color: var(--chomp-slate-700);
  font-family: var(--font-ui);
  font-size: 15px;
  line-height: 1.55;
}

.chomp-docs-console .sl-elements ::selection {
  background: #bfdbfe;
  color: #172554;
}

.chomp-docs-console [id] {
  scroll-margin-top: 7.5rem;
}

.chomp-docs-console :is(h1, h2, h3, h4, h5, h6) {
  color: var(--chomp-slate-900);
  font-family: var(--font-ui);
  letter-spacing: -0.025em;
  text-wrap: balance;
}

.chomp-docs-console .sl-elements h1 {
  font-size: clamp(1.85rem, 3vw, 2.45rem);
  font-weight: 800;
  line-height: 1.08;
}

.chomp-docs-console .sl-elements h2 {
  font-size: clamp(1.4rem, 2.2vw, 1.75rem);
  font-weight: 780;
  line-height: 1.2;
}

.chomp-docs-console .sl-elements h3 {
  font-size: 1.18rem;
  font-weight: 750;
  line-height: 1.3;
}

.chomp-docs-console .sl-elements h4,
.chomp-docs-console .sl-elements h5,
.chomp-docs-console .sl-elements h6 {
  font-size: 0.98rem;
  font-weight: 750;
  line-height: 1.35;
}

.chomp-docs-console a {
  color: var(--chomp-blue-darker);
  text-decoration-color: rgb(59 130 246 / 0.45);
  text-underline-offset: 0.18em;
}

.chomp-docs-console a:hover {
  color: #1e40af;
  text-decoration-color: currentColor;
}

/* --------------------------------------------------------------------------
 * Sidebar / table of contents
 * ------------------------------------------------------------------------ */

.chomp-docs-console .ElementsTableOfContentsItem {
  display: block;
  margin: 0.125rem 0.55rem;
  padding: 0.58rem 0.75rem;
  border-radius: 0.75rem;
  color: var(--chomp-slate-600);
  font-size: 0.92rem;
  font-weight: 560;
  line-height: 1.35;
  transition: background-color 140ms ease, color 140ms ease, box-shadow 140ms ease;
}

.chomp-docs-console .ElementsTableOfContentsItem:hover {
  background: var(--chomp-slate-100);
  color: var(--chomp-slate-900);
  text-decoration: none;
}

.chomp-docs-console .ElementsTableOfContentsItem.active,
.chomp-docs-console .ElementsTableOfContentsItem[aria-current="page"],
.chomp-docs-console .ElementsTableOfContentsItem[aria-current="true"] {
  /* Round 10: strengthened — the blue-50 wash (#eff6ff) read as no
   * highlight at all against the slate sidebar (Peter's round-9
   * re-test). Blue-100 fill, a wider inset bar, and the darker
   * blue at full weight so the current endpoint/schema is obvious
   * at a glance. Round 11 (Peter's round-10 re-test: "still isn't
   * visible enough"): blue-200 fill, a blue-600 bar, blue-900
   * text — plus a nav-scoped twin in the round-11 section at
   * higher specificity, in case mosaic's runtime sheet is
   * outranking this rule rather than the values being weak. */
  background: #bfdbfe;
  box-shadow: inset 0.25rem 0 0 #2563eb;
  color: #1e3a8a;
  font-weight: 700;
}

.chomp-docs-console nav {
  scrollbar-color: var(--chomp-slate-300) transparent;
  scrollbar-width: thin;
}

/* --------------------------------------------------------------------------
 * Operations, panels, and section rhythm
 * ------------------------------------------------------------------------ */

.chomp-docs-console .HttpOperation {
  max-width: none;
  scroll-margin-top: 7.5rem;
}

.chomp-docs-console .HttpOperation__Parameters {
  min-width: 0;
}

.chomp-docs-console .sl-panel {
  overflow: hidden;
  border: 1px solid var(--chomp-slate-200);
  border-radius: 1.05rem;
  background: #ffffff;
  box-shadow: 0 1px 2px rgb(15 23 42 / 0.05);
  /* Round 4: layout-only — a touch more air between stacked panels so
   * sections breathe; nothing about the panel's frame or fill changes. */
  margin-bottom: 0.4rem;
}

.chomp-docs-console .sl-panel__titlebar,
.chomp-docs-console .sl-panel__header {
  min-height: 2.85rem;
  border-bottom: 1px solid var(--chomp-slate-200);
  background: var(--chomp-slate-50);
  color: var(--chomp-slate-700);
  font-size: 0.84rem;
  font-weight: 750;
  letter-spacing: 0.01em;
  text-transform: none;
}

.chomp-docs-console .ServerInfo .sl-panel__titlebar > div {
  min-height: 2.85rem;
}

.chomp-docs-console .TryItPanel {
  min-width: 0;
  background: #ffffff;
}

/* The bundle caps this region at 162px. The branded-search operation has a
 * long filter vocabulary, so give the working area real height and keep the
 * scroll local to the parameter list. */
.chomp-docs-console .OperationParametersContent {
  max-height: min(62vh, 34rem);
  overflow: auto;
  padding-right: 0.25rem;
  scrollbar-color: var(--chomp-slate-300) transparent;
  scrollbar-width: thin;
}

.chomp-docs-console .TextRequestBody {
  max-height: 28rem;
}

/* Parameter names in the current bundle are squeezed into a 120px first
 * column. Long filter names need a stable, readable grid.
 * Round 5 (finding 5): the grid drops its middle column. Every parameter
 * row in the bundle is a three-child triplet — label, a bare Text ":"
 * separator, control (elements-core ParameterEditor, AuthTokenInput,
 * FileUploadParameterEditor) — and the round-5 section below hides the
 * middle cell. A two-column grid keeps label/control alignment across
 * every row, and the row gap tightens 0.7rem → 0.5rem. */
.chomp-docs-console .ParameterGrid {
  grid-template-columns: minmax(9rem, 13rem) minmax(0, 1fr);
  row-gap: 0.5rem;
  /* Round 8: this rule carried `margin-bottom: 1.25rem;
   * padding: 0.35rem 0 0.5rem` — horizontal padding ZERO at
   * specificity (0,2,0), beating the bundle's sl-p-4 (0,1,0) on
   * the Auth and Parameters grids. That is why the sidebar
   * labels and inputs sat on the container's edge through
   * rounds 5–7 (the panel-content padding rules never applied
   * here: on an operation page the grids ARE the panel bodies,
   * sitting directly in the content wrapper — the live DOM
   * dump's census found only three .sl-panel__content elements,
   * none of them a Try It grid). The bottom margin plus bottom
   * padding also stacked into the white strip Peter saw below
   * the rows, before the panel's rounded border. The grid now
   * carries the same 1rem inset as every other panel body and
   * no bottom margin; columns and row-gap are unchanged. */
  margin-bottom: 0;
  padding: 1rem;
  /* Round 9: column-gap — the grid never had one, so a full
   * label column touched the control column (Peter's round-8
   * screenshot, measured: the user_id subtext's first line ends
   * ~3px from the input box). Every label now gets a real
   * gutter before its control. */
  column-gap: 1rem;
}

/* --------------------------------------------------------------------------
 * Forms and the Try It console
 * ------------------------------------------------------------------------ */

.chomp-docs-console label {
  color: var(--chomp-slate-700);
  font-size: 0.875rem;
  font-weight: 650;
  line-height: 1.4;
}

.chomp-docs-console input:not([type="checkbox"]):not([type="radio"]):not([type="file"]),
.chomp-docs-console select,
.chomp-docs-console textarea {
  width: 100%;
  min-height: 2.85rem;
  border: 1px solid var(--chomp-slate-300);
  border-radius: 0.8rem;
  background: #ffffff;
  box-shadow: 0 1px 2px rgb(15 23 42 / 0.04);
  color: var(--chomp-slate-900);
  font: inherit;
  font-size: 0.92rem;
  line-height: 1.45;
  outline: none;
  transition: border-color 140ms ease, box-shadow 140ms ease, background-color 140ms ease;
}

.chomp-docs-console input:not([type="checkbox"]):not([type="radio"]):not([type="file"]),
.chomp-docs-console textarea {
  padding: 0.68rem 0.85rem;
}

.chomp-docs-console select {
  padding: 0.68rem 2.6rem 0.68rem 0.85rem;
  background-image:
    linear-gradient(45deg, transparent 50%, var(--chomp-slate-500) 50%),
    linear-gradient(135deg, var(--chomp-slate-500) 50%, transparent 50%);
  background-position:
    calc(100% - 1.15rem) 50%,
    calc(100% - 0.82rem) 50%;
  background-repeat: no-repeat;
  background-size: 0.34rem 0.34rem;
}

.chomp-docs-console textarea {
  min-height: 7rem;
  resize: vertical;
}

.chomp-docs-console input::placeholder,
.chomp-docs-console textarea::placeholder {
  color: var(--chomp-slate-400);
}

.chomp-docs-console input:not([type="checkbox"]):not([type="radio"]):not([type="file"]):hover,
.chomp-docs-console select:hover,
.chomp-docs-console textarea:hover {
  border-color: var(--chomp-slate-400);
}

.chomp-docs-console input:not([type="checkbox"]):not([type="radio"]):not([type="file"]):focus,
.chomp-docs-console select:focus,
.chomp-docs-console textarea:focus {
  border-color: var(--chomp-blue);
  box-shadow: 0 0 0 0.25rem rgb(59 130 246 / 0.14);
}

.chomp-docs-console input:disabled,
.chomp-docs-console select:disabled,
.chomp-docs-console textarea:disabled {
  border-color: var(--chomp-slate-200);
  background: var(--chomp-slate-50);
  color: var(--chomp-slate-400);
  cursor: not-allowed;
}

.chomp-docs-console input[type="checkbox"],
.chomp-docs-console input[type="radio"] {
  width: 1rem;
  height: 1rem;
  flex: 0 0 auto;
  accent-color: var(--chomp-blue);
}

.chomp-docs-console .Checkbox {
  max-width: none;
}

.chomp-docs-console .TextForCheckBox {
  padding: 0 0 0 0.55rem;
}

/* --------------------------------------------------------------------------
 * Buttons and tabs
 * ------------------------------------------------------------------------ */

.chomp-docs-console button {
  font: inherit;
  letter-spacing: -0.01em;
}

.chomp-docs-console .sl-button {
  min-height: 2.75rem;
  padding: 0.65rem 1.05rem;
  border-radius: 0.8rem;
  box-shadow: none;
  font-size: 0.9rem;
  font-weight: 720;
  line-height: 1.15;
  transition: background-color 140ms ease, border-color 140ms ease, color 140ms ease, box-shadow 140ms ease;
}

.chomp-docs-console .sl-button:hover {
  box-shadow: none;
  transform: none;
}

.chomp-docs-console button[class*="sl-bg-primary"] {
  background: var(--chomp-blue);
  box-shadow: 0 10px 20px -14px rgb(37 99 235 / 0.8);
  color: #ffffff;
}

.chomp-docs-console button[class*="sl-bg-primary"]:hover {
  background: var(--chomp-blue-dark);
}

.chomp-docs-console button[class*="sl-bg-canvas"] {
  border: 1px solid var(--chomp-slate-300);
  background: #ffffff;
  color: var(--chomp-slate-700);
}

.chomp-docs-console button[class*="sl-bg-canvas"]:hover {
  border-color: #93c5fd;
  background: #eff6ff;
  color: var(--chomp-blue-darker);
}

.chomp-docs-console [role="tablist"] {
  gap: 0.25rem;
  border-bottom: 1px solid var(--chomp-slate-200);
  scrollbar-width: thin;
}

.chomp-docs-console [role="tab"] {
  padding: 0.7rem 0.9rem;
  border-radius: 0.7rem 0.7rem 0 0;
  color: var(--chomp-slate-500);
  font-size: 0.88rem;
  font-weight: 680;
}

.chomp-docs-console [role="tab"]:hover {
  background: var(--chomp-slate-50);
  color: var(--chomp-slate-900);
}

.chomp-docs-console [role="tab"][aria-selected="true"] {
  background: #eff6ff;
  box-shadow: inset 0 -0.125rem 0 var(--chomp-blue);
  color: var(--chomp-blue-darker);
}

/* --------------------------------------------------------------------------
 * Markdown, schema, tables, and code
 * ------------------------------------------------------------------------ */

.chomp-docs-console .sl-markdown-viewer,
.chomp-docs-console .sl-markdown {
  color: var(--chomp-slate-600);
  font-size: 1rem;
  line-height: 1.75;
}

/* The bundle specifically reduces markdown paragraphs inside schema and
 * parameter descriptions to 12px. Those descriptions carry the meaning of
 * the API contract, so they return to the documentation scale. */
.chomp-docs-console .HttpOperation .JsonSchemaViewer .sl-markdown-viewer p,
.chomp-docs-console .HttpOperation__Parameters .sl-markdown-viewer p,
.chomp-docs-console .Model .JsonSchemaViewer .sl-markdown-viewer p,
.chomp-docs-console .HttpOperation .JsonSchemaViewer .sl-markdown p,
.chomp-docs-console .HttpOperation__Parameters .sl-markdown p,
.chomp-docs-console .Model .JsonSchemaViewer .sl-markdown p {
  font-size: 0.92rem;
  line-height: 1.65;
}

.chomp-docs-console .sl-markdown-viewer > * + *,
.chomp-docs-console .sl-markdown > * + * {
  margin-top: 1em;
}

.chomp-docs-console .sl-markdown-viewer ul,
.chomp-docs-console .sl-markdown ul,
.chomp-docs-console .sl-markdown-viewer ol,
.chomp-docs-console .sl-markdown ol {
  list-style: none;
}

.chomp-docs-console .sl-markdown-viewer ul > li,
.chomp-docs-console .sl-markdown ul > li,
.chomp-docs-console .sl-markdown-viewer ol > li,
.chomp-docs-console .sl-markdown ol > li {
  padding-left: 1.55em;
}

.chomp-docs-console .sl-markdown-viewer ol,
.chomp-docs-console .sl-markdown ol {
  counter-reset: chomp-docs-list;
}

.chomp-docs-console .sl-markdown-viewer ol > li,
.chomp-docs-console .sl-markdown ol > li {
  counter-increment: chomp-docs-list;
}

.chomp-docs-console .sl-markdown-viewer ol > li::marker,
.chomp-docs-console .sl-markdown ol > li::marker,
.chomp-docs-console .sl-markdown-viewer ul > li::marker,
.chomp-docs-console .sl-markdown ul > li::marker {
  content: none;
}

.chomp-docs-console .sl-markdown-viewer ol > li::before,
.chomp-docs-console .sl-markdown ol > li::before {
  content: counter(chomp-docs-list) ".";
  left: 0;
}

.chomp-docs-console .sl-markdown-viewer ul:not(.contains-task-list) > li::before,
.chomp-docs-console .sl-markdown ul:not(.contains-task-list) > li::before {
  left: 0.55em;
}

.chomp-docs-console .sl-markdown-viewer li + li,
.chomp-docs-console .sl-markdown li + li {
  margin-top: 0.35em;
}

.chomp-docs-console .sl-markdown-viewer blockquote,
.chomp-docs-console .sl-markdown blockquote {
  margin-left: 0;
  padding: 0.25rem 0 0.25rem 1rem;
  border-left: 0.25rem solid var(--chomp-blue);
  background: linear-gradient(90deg, #eff6ff, transparent 72%);
  color: var(--chomp-slate-700);
}

.chomp-docs-console .sl-markdown-viewer hr,
.chomp-docs-console .sl-markdown hr {
  border: 0;
  border-top: 1px solid var(--chomp-slate-200);
}

.chomp-docs-console .JsonSchemaViewer {
  font-size: 0.925rem;
  line-height: 1.65;
}

.chomp-docs-console .Model {
  --fs-code: 0.82rem;
}

.chomp-docs-console table {
  width: 100%;
  border-collapse: separate;
  border-spacing: 0;
  color: var(--chomp-slate-700);
  font-size: 0.925rem;
  line-height: 1.55;
}

.chomp-docs-console thead {
  background: var(--chomp-slate-50);
}

.chomp-docs-console th {
  padding: 0.75rem 0.9rem;
  border-bottom: 1px solid var(--chomp-slate-200);
  color: var(--chomp-slate-600);
  font-size: 0.72rem;
  font-weight: 780;
  letter-spacing: 0.07em;
  text-align: left;
  text-transform: uppercase;
  vertical-align: bottom;
}

.chomp-docs-console td {
  padding: 0.8rem 0.9rem;
  border-top: 1px solid var(--chomp-slate-200);
  vertical-align: top;
}

.chomp-docs-console tbody tr {
  transition: background-color 120ms ease;
}

.chomp-docs-console tbody tr:hover {
  background: var(--chomp-slate-50);
}

.chomp-docs-console code,
.chomp-docs-console kbd,
.chomp-docs-console samp {
  font-family: var(--font-mono);
}

.chomp-docs-console :not(pre) > code {
  padding: 0.14rem 0.36rem;
  border: 1px solid #bfdbfe;
  border-radius: 0.42rem;
  background: #eff6ff;
  color: var(--chomp-blue-darker);
  font-size: 0.86em;
  overflow-wrap: anywhere;
}

.chomp-docs-console pre {
  max-width: 100%;
  overflow: auto;
  border: 1px solid #1e293b;
  border-radius: 1rem;
  background: var(--chomp-slate-900);
  box-shadow: inset 0 1px 0 rgb(255 255 255 / 0.04);
  color: #e2e8f0;
  font-family: var(--font-mono);
  font-size: 0.86rem;
  line-height: 1.65;
  tab-size: 2;
}

.chomp-docs-console pre code {
  border: 0;
  background: transparent;
  color: inherit;
  font-size: inherit;
}

.chomp-docs-console .sl-bg-canvas-dark,
.chomp-docs-console .sl-bg-canvas-pure {
  color: #e2e8f0;
}

/* Prism-style token hooks used by code renderers in the Elements bundle.
 * They are harmless when a given response view uses different spans. */
.chomp-docs-console .token.property,
.chomp-docs-console .token.attr-name {
  color: #93c5fd;
}

.chomp-docs-console .token.string,
.chomp-docs-console .token.attr-value {
  color: #86efac;
}

.chomp-docs-console .token.number,
.chomp-docs-console .token.boolean {
  color: #fdba74;
}

.chomp-docs-console .token.operator,
.chomp-docs-console .token.keyword {
  color: #f0abfc;
}

.chomp-docs-console .token.punctuation {
  color: #94a3b8;
}

/* --------------------------------------------------------------------------
 * Round 2 — console internals diagnosed from the bundle sources
 * (@stoplight/elements-core, @stoplight/mosaic, @stoplight/mosaic-code-viewer,
 * @stoplight/json-schema-viewer, all 9.0.29 / 1.53.5 / 4.16.3)
 * ------------------------------------------------------------------------ */

/* (c)+(d) Try It contrast and double framing. Elements-core wraps the whole
 * Try It region in mosaic's InvertTheme (TryItWithRequestSamples renders
 * InvertTheme > Box > TryIt), which stamps .sl-inverted on the wrapper.
 * Mosaic's theme engine generates a stylesheet at runtime that redefines
 * every --color-* variable under .sl-inverted with the inverted palette:
 * its canvas ramp collapses to near-black slate and its text ramp flips
 * light-on-dark. That runtime block is what paints the Auth/Parameters
 * panels dark, and the labels inside inherit the inverted text variables
 * while the global input rule above keeps the input pills white — dark
 * label text on a dark panel. No static rule of ours caused it, and the
 * bridge on elements-api cannot reach it (the inverted values are scoped
 * to .sl-inverted itself). Re-pinning the same variables to the light
 * palette inside the console outranks the generated block:
 * .chomp-docs-console elements-api .sl-inverted is (0,2,1) against the
 * generated [data-theme="light"] .sl-inverted at (0,2,0). With the fills
 * light, the panels keep exactly one frame — the .sl-panel border and
 * radius above; the Panel content wrapper paints a flat canvas-100 with
 * no border or radius of its own in the bundle, so nothing is left to
 * double-frame. The trade is deliberate: the bundle intends Try It as a
 * dark console; this page is a light workspace. */
.chomp-docs-console elements-api .sl-inverted {
  --color-canvas: #ffffff;
  --color-canvas-50: #f8fafc;
  --color-canvas-100: #f1f5f9;
  --color-canvas-200: #e2e8f0;
  --color-canvas-300: #cbd5e1;
  --color-canvas-400: #94a3b8;
  --color-canvas-500: #64748b;
  --color-canvas-dark: #0f172a;
  --color-canvas-pure: #ffffff;
  --color-canvas-tint: #eff6ff;
  --color-canvas-dialog: #ffffff;

  --color-text: #334155;
  --color-text-heading: #0f172a;
  --color-text-paragraph: #475569;
  --color-text-muted: #64748b;
  --color-text-light: #94a3b8;
  --color-text-disabled: #94a3b8;
  --color-text-link: #1d4ed8;
  --color-text-code: #1d4ed8;

  --color-border: #cbd5e1;
  --color-border-light: #e2e8f0;
  --color-border-dark: #94a3b8;
  --color-border-input: #cbd5e1;
  --color-border-button: #cbd5e1;

  --color-primary: #3b82f6;
  --color-primary-light: #60a5fa;
  --color-primary-dark: #2563eb;
  --color-primary-darker: #1d4ed8;
  --color-primary-tint: #eff6ff;
  --color-text-primary: #1d4ed8;
  --color-on-primary: #ffffff;

  --color-success: #059669;
  --color-success-light: #34d399;
  --color-success-dark: #047857;
  --color-success-darker: #065f46;
  --color-success-tint: #ecfdf5;
  --color-on-success: #ffffff;
  --color-text-success: #047857;

  --color-warning: #d97706;
  --color-warning-light: #fbbf24;
  --color-warning-dark: #b45309;
  --color-warning-darker: #92400e;
  --color-warning-tint: #fffbeb;
  --color-on-warning: #ffffff;
  --color-text-warning: #92400e;

  --color-danger: #e11d48;
  --color-danger-light: #fb7185;
  --color-danger-dark: #be123c;
  --color-danger-darker: #881337;
  --color-danger-tint: #fff1f2;
  --color-on-danger: #ffffff;
  --color-text-danger: #be123c;

  --color-code: #dbeafe;
  --color-on-code: #0f172a;
}

/* Belt and braces for the inverted region: anything that inherits its
 * text color inside a parameter grid takes the readable slate directly. */
.chomp-docs-console .sl-inverted .ParameterGrid,
.chomp-docs-console .sl-inverted label {
  color: var(--chomp-slate-700);
}

/* (e) Blue section headings. Elements-core's SectionTitle renders mosaic's
 * LinkHeading, which puts the heading text inside an anchor
 * (.sl-link-heading__link, color: "current" in the component). The bundle
 * stylesheet defines no color for that class — only the hover opacity of
 * its link icon — so the generic anchor rule above
 * (.chomp-docs-console a, #1d4ed8) wins and paints "Request"/"Responses"
 * blue. Operation titles use a plain Heading with no anchor, which is why
 * they already render slate. Pin the link heading to inherit so the
 * :is(h1..h6) slate rule governs it like every other heading. */
.chomp-docs-console .sl-link-heading__link,
.chomp-docs-console .sl-link-heading__link:hover {
  color: inherit;
}

/* (g) The near-black "responses / 200" strip is the schema viewer's
 * PathCrumbs bar (json-schema-viewer: a sticky mono HStack with
 * bg: "canvas-pure" and parentCrumbs ['responses', <code>]). Stock
 * Elements defines --color-canvas-pure as #fff; the theme bridge above
 * remapped it to #020617, which is what painted the bar black. Restyle
 * just that bar, inside the schema viewer only, to a light breadcrumb
 * strip; its own border-bottom already separates it from the schema. */
.chomp-docs-console .JsonSchemaViewer .sl-bg-canvas-pure {
  background: var(--chomp-slate-50);
  color: var(--chomp-slate-500);
}

/* (h) Code block overflow. mosaic-code-viewer's CodeContainer root is the
 * <pre> itself (overflow hidden on both axes) and the actual scrolling
 * element inside it is .sl-code-viewer__scroller (overflow auto, inline
 * max-height). The generic pre rule above sets overflow: auto on the root
 * and on the nested Prism <pre>, stacking extra scroll containers whose
 * scrollbars land outside the panel's rounded clip. Inside panels, only
 * the scroller scrolls; the .sl-panel rule's overflow: hidden and radius
 * then clip the dark block cleanly. Markdown <pre> blocks live outside
 * panels and keep the generic rule. */
.chomp-docs-console .sl-panel {
  min-width: 0;
}

.chomp-docs-console .sl-panel pre {
  overflow: hidden;
}

.chomp-docs-console .sl-code-viewer__scroller {
  max-width: 100%;
  overflow: auto;
  scrollbar-color: var(--chomp-slate-500) transparent;
  scrollbar-width: thin;
}

/* The code viewer's dark block, pinned here instead of in the generic
 * pre rule above: that rule sets background slate-900 on EVERY pre in the
 * console — including the code viewer's own root <pre> — so code blocks
 * keep their intended dark surface even inside .sl-inverted scopes, whose
 * mosaic surfaces (panel titlebars, panel content) are light after the
 * round-2 re-pin. prism-react-renderer paints the code text inside this
 * block; the token rules below govern its palette. */
.chomp-docs-console .sl-code-viewer {
  background: var(--chomp-slate-900);
  color: #e2e8f0;
}

/* --------------------------------------------------------------------------
 * Round 3 — Try It rail contrast, code tokens, portal menus
 * (diagnosed from @stoplight/elements-core 9.0.29, @stoplight/mosaic
 * 1.53.5, @stoplight/mosaic-code-viewer 1.53.5 sources)
 * ------------------------------------------------------------------------ */

/* (a) The faded label-row colons. AuthTokenInput (and the basic/digest
 * auth rows) render the separator as a bare mosaic Text element with no
 * color prop — <Text mx={3}>":"</Text> — so the colon takes the scope's
 * --color-text. Inside Try It's .sl-inverted scope, mosaic's runtime
 * theme block defines that variable for the inverted palette (in the
 * pinned bundle's static copy: text lightness 86% — near-white), while
 * the round-2 re-pin above sets the LABELED rows' container color
 * directly (.sl-inverted .ParameterGrid { color: slate-700 }) without
 * touching the variable. The colon therefore still resolves near-white
 * on the now-light panel whenever an ancestor does not hand it the
 * container color. Pin the grid's inherited text color AND the colon's
 * own variable consumer to the readable slate, scoped to the grid. */
.chomp-docs-console .ParameterGrid {
  color: var(--chomp-slate-700);
}

.chomp-docs-console .ParameterGrid .sl-text-body {
  color: var(--chomp-slate-700);
}

/* (b) Washed-out Try It inputs. The auth and parameter fields are mosaic
 * inputs with appearance "minimal": the variant map gives them a
 * transparent background and a transparent border (borderColor only turns
 * "input" on hover and "primary" on focus), so they read as bare text on
 * the panel. The generic input rule above already paints them white with
 * a slate-300 border; these rules make the treatment explicit for the
 * Try It grids and raise the floor the brief sets: entered text at
 * slate-900, placeholders at slate-500 (the generic rule used slate-400).
 * Disabled inputs (the Send flow locks fields while a request runs) keep
 * the generic disabled treatment. */
.chomp-docs-console .ParameterGrid input:not([type="checkbox"]):not([type="radio"]):not([type="file"]) {
  border: 1px solid var(--chomp-slate-300);
  background: #ffffff;
  color: var(--chomp-slate-900);
}

.chomp-docs-console .ParameterGrid input::placeholder {
  color: var(--chomp-slate-500);
  opacity: 1;
}

.chomp-docs-console input::placeholder,
.chomp-docs-console textarea::placeholder {
  color: var(--chomp-slate-500);
}

/* (c) The "Send API Request" button. Elements-core renders it as a
 * mosaic Button with appearance "primary", whose variant map paints
 * bg "primary" and — while the button carries its disabled attribute
 * (no request sent yet, or a request in flight) — bg "canvas-100" with
 * color "body" at 70% opacity. That disabled state is the washed
 * pale-blue button in the screenshots: our bridge pins canvas-100 to
 * #f1f5f9 and the class hook button[class*="sl-bg-primary"] never matches
 * a disabled render (its class is sl-bg-canvas-100). Pin the primary
 * action to Chomp's brand blue — the same blue as the page's own primary
 * ("Get an API key", --chomp-blue #3b82f6, which is also the console's
 * --color-primary) — in every state, enabled or disabled, so the one
 * action the console exists for always reads as the primary action.
 * Opacity is forced back to 1: mosaic's 0.7 disabled fade over a light
 * panel is the other half of the wash. */
.chomp-docs-console button[class*="sl-bg-primary"],
.chomp-docs-console button[class*="sl-bg-primary"]:disabled {
  background: var(--chomp-blue);
  box-shadow: 0 10px 20px -14px rgb(37 99 235 / 0.8);
  color: #ffffff;
  opacity: 1;
}

.chomp-docs-console button[class*="sl-bg-primary"]:hover:not(:disabled) {
  background: var(--chomp-blue-dark);
}

/* The disabled primary is the ONLY button that renders sl-bg-canvas-100
 * in the Try It rail (mosaic's default appearance uses canvas-100 only
 * as an :active tint, never as a resting class). If a future bundle
 * build emits the primary's disabled state without the sl-bg-primary
 * hook above, this catches the resting state too — scoped to buttons so
 * it cannot touch panels or code surfaces that share the class. */
.chomp-docs-console button.sl-bg-canvas-100:disabled {
  background: var(--chomp-blue);
  color: #ffffff;
  opacity: 1;
}

/* (e) Ghost icon buttons. Mosaic's CopyButton is a Button with
 * appearance "minimal": color "muted" (our bridge: slate-500), a
 * transparent background, and no resting border — on the pale panel
 * titlebar it reads as a watermark. The same minimal appearance drives
 * the Request Sample language trigger and the panel collapse chevrons.
 * Give every minimal button in the console a visible slate-600 icon,
 * slate-700 on hover over a slate-100 wash; the language trigger keeps
 * its text label legible at the same strength. */
.chomp-docs-console button[class*="sl-text-muted"] {
  color: var(--chomp-slate-600);
}

.chomp-docs-console button[class*="sl-text-muted"]:hover {
  background: var(--chomp-slate-100);
  color: var(--chomp-slate-700);
}

/* (d) Code token colors. mosaic-code-viewer's useCodeTheme() picks its
 * prism-react-renderer theme from the theme store: inside an inverted
 * scope it returns the GitHub LIGHT theme whenever the store's
 * invertedColorValues.light flag is set — and the round-2 re-pin makes
 * this page's inverted scope light, so the Try It samples render with
 * the light theme's palette (strings #032f62, properties #005cc5, plain
 * text #393a34) while the .sl-code-viewer rule above keeps the block
 * itself dark slate-900. The dim blue-on-black curl sample in the
 * screenshots is exactly that pairing. prism-react-renderer writes token
 * colors as INLINE styles on the token spans, so stylesheet rules can
 * only win with !important; that is what the flag is doing here, and it
 * is scoped to .sl-code-viewer so nothing outside a code block is
 * affected. The palette is the bundle's own dark theme (Night Owl
 * lineage — the theme the viewer uses on genuinely dark surfaces),
 * lifted to the values the generic .token rules above already use, so
 * markdown blocks and viewer blocks read the same. Response JSON blocks
 * render through the same code viewer and get the same treatment. */
.chomp-docs-console .sl-code-viewer .token.string,
.chomp-docs-console .sl-code-viewer .token.attr-value,
.chomp-docs-console .sl-code-viewer .token.url,
.chomp-docs-console .sl-code-viewer .token.regex {
  color: #86efac !important;
}

.chomp-docs-console .sl-code-viewer .token.property,
.chomp-docs-console .sl-code-viewer .token.attr-name {
  color: #93c5fd !important;
}

.chomp-docs-console .sl-code-viewer .token.number,
.chomp-docs-console .sl-code-viewer .token.boolean,
.chomp-docs-console .sl-code-viewer .token.constant,
.chomp-docs-console .sl-code-viewer .token.symbol {
  color: #fdba74 !important;
}

.chomp-docs-console .sl-code-viewer .token.keyword,
.chomp-docs-console .sl-code-viewer .token.operator,
.chomp-docs-console .sl-code-viewer .token.atrule,
.chomp-docs-console .sl-code-viewer .token.entity {
  color: #f0abfc !important;
}

.chomp-docs-console .sl-code-viewer .token.comment {
  color: #94a3b8 !important;
}

.chomp-docs-console .sl-code-viewer .token.punctuation {
  color: #cbd5e1 !important;
}

/* (f) Portal menus. Mosaic menus (Menu > Popover, appearance "minimal")
 * render through a react-aria portal at body level — outside
 * .chomp-docs-console and outside elements-api — so no console-scoped
 * rule can reach them; the round-2 re-pin never applied. The menu list
 * (MenuNodes, class .sl-menu) paints its own surface INLINE:
 * background: var(--color-canvas-pure) in light mode, resolved at body
 * level where the page's bridge never redefined the variable — so the
 * bundle default applies, and the bundle ships TWO definitions of it:
 * #fff on :root and a near-black value (#0c1018 in the inverted block,
 * #090c11/#111722 in the dark theme) — whichever block wins the cascade
 * at body level decides the menu. The 3:46 PM screenshot shows the dark
 * value winning on this page. Stock mosaic gives the menu no background
 * utility class, no max-height, and no text color of its own (items
 * inherit), which is also why the language menu renders unbounded and
 * tall: ~20 language/library rows at full height.
 * The rules below are body-level by necessity and are scoped to the
 * menu's own classes (.sl-popover > .sl-menu is the exact portal shape
 * Menu renders). They force the light surface with !important because
 * the stock background is an inline style, and they bound the height
 * with an internal scroll. SHARED-CLASS DISCLOSURE: .sl-menu is used by
 * every mosaic Menu on the page (the language menu, the version Select
 * in the Try It servers row, response-example menus); all of them are
 * Elements chrome on a light workspace, so the light treatment is
 * correct for each — no narrower hook exists, because the portal strips
 * the trigger's context (the language menu carries only
 * aria-label="Request Sample Language" on the Menu wrapper, which does
 * not survive onto the portaled list element). Item hover/focus in the
 * bundle paints background var(--color-primary) with on-primary text;
 * at body level --color-primary is the bundle's #19abff unless a
 * console ancestor redefined it, so the hover text color is pinned
 * explicitly. */
/* Round 5: the three child-combinator rules that stood here are
 * REPLACED by the descendant-combinator block in the round-5 section
 * (see finding 7 there): mosaic's MenuList wraps the main menu's
 * .sl-menu in a VStack, so `> .sl-menu` reached only submenus.
 * Declarations and intent carry over unchanged; the selector form is
 * the fix. */

/* --------------------------------------------------------------------------
 * Focus, scrolling, and motion
 * ------------------------------------------------------------------------ */

.chomp-docs-page a:focus-visible,
.chomp-docs-page button:focus-visible,
.chomp-docs-console a:focus-visible,
.chomp-docs-console button:focus-visible,
.chomp-docs-console input:focus-visible,
.chomp-docs-console select:focus-visible,
.chomp-docs-console textarea:focus-visible,
.chomp-docs-console [tabindex]:focus-visible {
  /* Round 4: the ring alpha rises slightly — the same ring, a touch
   * more present against the light workspace. */
  outline: 0.1875rem solid rgb(59 130 246 / 0.5);
  outline-offset: 0.15rem;
}

/* Round 4: links inside the console body get the same focus treatment
 * as the chrome links above (the rule above covers .chomp-docs-page
 * links; console body links live under .sl-elements). */
.chomp-docs-console .sl-elements a:focus-visible {
  outline: 0.1875rem solid rgb(59 130 246 / 0.5);
  outline-offset: 0.15rem;
}

.chomp-docs-console *::-webkit-scrollbar {
  width: 0.625rem;
  height: 0.625rem;
}

.chomp-docs-console *::-webkit-scrollbar-thumb {
  border: 0.1875rem solid transparent;
  border-radius: 9999px;
  background: var(--chomp-slate-300);
  background-clip: padding-box;
}

.chomp-docs-console *::-webkit-scrollbar-track {
  background: transparent;
}

@media (prefers-reduced-motion: reduce) {
  .chomp-docs-page *,
  .chomp-docs-console * {
    scroll-behavior: auto !important;
    transition-duration: 0.01ms !important;
  }
}

/* --------------------------------------------------------------------------
 * Responsive behavior
 * ------------------------------------------------------------------------ */

/* Round 3: the 640px and 1024px padding rules are gone. The page width
 * now comes from the min(110rem, 100vw − 3rem) column itself, and the
 * gutter lives in the template's px-4 / sm:px-6 / lg:px-10 utilities —
 * the old rules overrode those utilities (same specificity, later in
 * the file) and pinned horizontal padding at 2.5rem, which would have
 * eaten into the band and broken the nav alignment. */
@media (max-width: 1100px) {
  /* Round 3: the masthead is a stack, so nothing to un-grid; the strip's
   * three step columns become one column. */
  .chomp-docs-steps {
    grid-template-columns: 1fr;
  }

  .chomp-docs-auth-state {
    margin-top: 1.25rem;
  }
}

@media (max-width: 767px) {
  .chomp-docs-page {
    --chomp-docs-radius: 1.15rem;
  }

  .chomp-docs-masthead__main {
    padding: 1.6rem 1.35rem;
  }

  .chomp-docs-masthead h1 {
    font-size: clamp(2.45rem, 13vw, 3.4rem);
  }

  .chomp-docs-intro {
    line-height: 1.65;
  }

  .chomp-docs-actions,
  .chomp-docs-button {
    width: 100%;
  }

  .chomp-docs-version-switcher {
    display: flex;
    width: 100%;
  }

  .chomp-docs-version-switcher a {
    flex: 1 1 0;
    text-align: center;
  }

  .chomp-docs-quickstart {
    padding: 1.45rem;
  }

  .chomp-docs-toolbar {
    align-items: flex-start;
    flex-direction: column;
    padding: 1rem;
  }

  .chomp-docs-toolbar__meta {
    justify-content: flex-start;
    padding-left: 3.5rem;
  }

  .chomp-docs-console .sl-elements {
    font-size: 14px;
  }

  .chomp-docs-console elements-api {
    min-height: 38rem;
  }

  .chomp-docs-console .ParameterGrid {
    grid-template-columns: 1fr;
    row-gap: 0.45rem;
  }

  .chomp-docs-console .OperationParametersContent {
    max-height: 70vh;
  }

  .chomp-docs-console table {
    min-width: 38rem;
  }
}

@media print {
  .chomp-docs-quickstart,
  .chomp-docs-toolbar {
    display: none;
  }

  .chomp-docs-shell {
    box-shadow: none;
  }
}

/* --------------------------------------------------------------------------
 * Round 4 — page-level micro-polish (additive; nothing above changes)
 * ------------------------------------------------------------------------ */

/* Round 4: the masthead and the steps strip take the brand selection
 * color, matching the console's existing selection rule, so text
 * selection feels consistent across the whole page. Scoped to our own
 * chrome — the console keeps its own rule. */
.chomp-docs-masthead ::selection,
.chomp-docs-quickstart ::selection {
  background: #bfdbfe;
  color: #172554;
}

/* Round 4: the page's own horizontal scrollbar gets the console's
 * treatment (same size, same thumb). This stylesheet loads only on the
 * docs page, so the rule cannot leak to other pages. */
html {
  scrollbar-color: var(--chomp-slate-300) transparent;
  scrollbar-width: thin;
}

::-webkit-scrollbar {
  width: 0.625rem;
  height: 0.625rem;
}

::-webkit-scrollbar-thumb {
  border: 0.1875rem solid transparent;
  border-radius: 9999px;
  background: var(--chomp-slate-300);
  background-clip: padding-box;
}

::-webkit-scrollbar-track {
  background: transparent;
}

/* --------------------------------------------------------------------------
 * Round 5 — Peter's re-test of round 3 (2026-11-10): one flat console,
 * consolidated Responses header, crumbs rhythm, Send button colors,
 * one menu system
 * (diagnosed from @stoplight/elements-core 9.0.29, @stoplight/mosaic
 * 1.53.5, @stoplight/json-schema-viewer 4.16.3 sources; ground truth =
 * Peter's eight re-test screenshots of 2026-11-10)
 * ------------------------------------------------------------------------ */

/* (4a) One surface per panel — the white band. Mosaic's Panel renders
 * TWO surfaces: the root .sl-panel box, and an inner
 * .sl-panel__content-wrapper that carries the panel's background —
 * bg canvas-100 whenever the panel is neither minimal nor outlined
 * (mosaic Panel: bg: isMinimal || isOutlined ? undefined : "canvas-100").
 * Rounds 1–2 painted the OUTER box white (.sl-panel above) and never
 * touched the wrapper, so every panel is our white surface outside and
 * the bundle's gray surface inside. In the advanced-search screenshot
 * the gray ends and a white band sits INSIDE the frame below the last
 * fully visible row: the bundle's surface ends, ours keeps going to the
 * frame's edge. The wrapper's exact height on that operation is set by
 * the capped parameter scroller (the .OperationParametersContent rule
 * above caps it at min(62vh, 34rem), which is also why the last row
 * clips mid-height in that screenshot), so the two surfaces disagree
 * about where the panel ends. Collapse to ONE surface: the wrapper
 * paints nothing, the panel's own white surface is the only fill, and
 * there is no second surface left to end early. The titlebar keeps its
 * slate-50 treatment — it already sits on the panel's own surface.
 * Panel spacing is untouched: round 4's 0.4rem margin-bottom on
 * .sl-panel stays exactly as it was (the one round-4/round-5 overlap;
 * round 5's panel work is internal fill, not outer spacing). */
/* The Try It rail's panel bodies are mosaic Panel.Content elements,
 * which mosaic sets at p: 4 — 1rem of padding on every side — and at
 * their shallowest (all seven utilities !important) the layout
 * preflight in the compiled bundle resets that padding to 0, leaving
 * the Auth row and every parameter row flush on the panel's left
 * border (Peter's round-5 rail screenshot). Restore real padding on
 * every Panel.Content in console scope — the whole rail family at
 * once: Auth, Parameters, Send holder, request body, server
 * variables, form data. The samples/response bodies (round-6 section)
 * override their own padding back to 0 so the dark code surface keeps
 * spanning its panel edge to edge; the PathCrumbs content keeps its
 * padding via the same :not exclusion as this rule's pre/code-viewer
 * exclusions below. */
.chomp-docs-console .sl-panel__content {
  padding: 1rem;
}

/* Round 6 (finding 5b): the Security accordion panel carried TWO
 * visible border systems at once — our .sl-panel border (all four
 * sides) and the bundle's outlined treatment on the same element
 * (borderT on the content-wrapper + the titlebar's borderColor),
 * because SubSectionPanel passes appearance="outlined" and mosaic
 * signals it with generated border classes while ALSO emitting
 * sl-outline-none. Exactly one border now reads per side: the panel's
 * own border (side and top), the titlebar's bottom border (the
 * separator) — and the wrapper's generated top border is removed so
/* The wrapper's generated top border is removed so the titlebar
 * doesn't double-rule its own bottom edge. (Round 5's transparency
 * declaration for this selector stays in its own rule below — the two
 * rules merge in the cascade.) */
.chomp-docs-console .sl-panel__content-wrapper {
  border-top: 0;
}

/* (4b) The box in the box — Security. Elements-core's Request column
 * renders SecuritySchemes → SecurityPanel → mosaic Panel
 * ("Security: API Key") → elements-core's OWN PanelContent component
 * (not mosaic's Panel.Content): each scheme maps to a mosaic Box with
 * border: true — mosaic emits .sl-border (1px width) + .sl-border-solid
 * + .sl-border-input (border-color: var(--color-border-input)) — plus
 * m: 2 and p: 2. That box is the gray bordered box inside the gray
 * bordered panel in Peter's Security screenshot: the description text,
 * the api_key chip, and the "Example: ?api_key=…" line sit in a second
 * framed container on the panel's surface.
 * The scheme box carries no class or data-test of its own, so the hook
 * is structural: direct children of a panel's content wrapper inside
 * the console. Exclusions keep the rule off real controls and code:
 * .sl-button also renders border: true (it carries .sl-form-group-border)
 * and the code viewer's root is a <pre> — both are :not()-ed out, as
 * are tables. Nested PANELS (the HttpService-level SecurityScheme
 * renders a mosaic Panel inside the outer Security panel — a
 * panel-in-panel, data-test "security-row") are NOT matched by the
 * child selector and are flattened by the next rule instead. */
.chomp-docs-console .sl-panel__content-wrapper > *:not(.sl-button):not(pre):not(.sl-code-viewer):not(table) {
  border: 0;
  /* Round 7: margin/padding zeroing REMOVED from this rule. Its
   * direct-child target IS .sl-panel__content (the wrapper's only
   * child), and the four :not()s inflate its specificity to (0,6,0),
   * so the padding: 0 silently beat round 6's (0,2,0) padding
   * restore on EVERY panel body — Peter's round-6 re-test: sidebar
   * panels still flush on their borders. The border: 0 stays (it is
   * harmless on the content element). The scheme box this rule was
   * written for sits one level deeper, inside the content; round 7
   * reaches it with a correctly-scoped rule in the round-7 section
   * below, written against Peter's live DOM dump. The code-viewer
   * contents, which relied on this zeroing for their edge-to-edge
   * dark surface, get an explicit padding: 0 there instead. */
}

/* (4b, cont.) Panel-in-panel flattening. Two source-proven instances:
 * HttpService's SecurityScheme — a mosaic Panel nested inside the outer
 * SecuritySchemes panel (its titlebar paints canvas-300) — and
 * ServerInfo's ServerUrl rows, each a full mosaic Panel inside the
 * "API Base URL" panel (data-test "server-row"). A nested panel loses
 * its border, radius, and shadow and sits directly on the outer panel's
 * surface; its titlebar keeps a hairline separator so the row still
 * reads as a row. This is also the rule that keeps any future nested
 * panel the bundle adds from re-creating the double frame. */
.chomp-docs-console .sl-panel .sl-panel {
  border: 0;
  border-radius: 0;
  box-shadow: none;
}

.chomp-docs-console .sl-panel .sl-panel > .sl-panel__titlebar {
  background: transparent;
  border-bottom: 1px solid var(--chomp-slate-200);
}

/* Census note (in ROUND5-NOTES.md): the remaining bordered-in-panel
 * pattern in the bundle is elements-core's OptionalMessage — a mosaic
 * Callout with appearance "outline", rendered above the Request
 * column's security panels and inside the HttpService Security panel.
 * It is an intentional callout (a message, not a container), so it is
 * left as designed and NOT flattened here. The dark code block inside
 * response panels is likewise a single intentional code surface, not a
 * gray-on-gray container. */

/* (5) The floating colons. Every parameter row the bundle renders is a
 * Fragment of exactly three grid children — label, a bare mosaic
 * Text { mx: 3 } containing ":", then the control (elements-core
 * ParameterEditor ~82,977; AuthTokenInput ~63,175;
 * FileUploadParameterEditor ~74,588; the Try It auth row wraps the same
 * triplet in a Panel.Content carrying the ParameterGrid class). The
 * middle cells sat in the grid's old 1.25rem middle column, floating
 * between label and input. Rows are uniform triplets, so the middle
 * child of each triplet is the separator: hide it. The FormData
 * optional-checkbox row's middle cell is an empty div — hiding it is
 * harmless. The grid itself is now two columns (see the ParameterGrid
 * rule above), so label and control alignment holds across rows.
 * The round-3 colon COLOR pins (.ParameterGrid color, .sl-text-body)
 * stay in place above — the cells they targeted no longer render, and
 * the pins still govern any other grid text. */
.chomp-docs-console .ParameterGrid > :nth-child(3n + 2) {
  display: none;
}

/* (4c) Responses = ONE header bar. Elements-core's Responses renders a
 * VStack Tabs (appearance "pill") whose first row is mosaic's
 * SectionTitle: a Flex holding the title (a Box rendered as
 * LinkHeading, py: 1) and a second Flex (alignSelf: center, flexGrow: 1)
 * holding the compact TabList — title and tabs already share one row in
 * the source, and Peter's screenshot confirms they render on one row.
 * What reads as "floating" is that the row has no shared bar treatment:
 * round 2's tablist border-bottom spans only under the tabs, and the
 * active tab's pale fill + inset underline floats inside the row.
 * The fix makes the row one bar: the heading box takes the same
 * slate-200 bottom border as the tablist, and the tablist stretches
 * (flex: 1 1 auto) so a single continuous rule runs under title +
 * tabs. REPLACED: the round-2 [role="tablist"] rule's detached
 * underline treatment (1 rule → 1 rule, declarations changed) and the
 * [aria-selected="true"] marker — the floating inset underline is
 * replaced with a FILLED CHIP (brand blue bg, white text), chosen over
 * accent-text-plus-underline because the underline is exactly what
 * Peter called floating. [role="tab"] padding/hover rules above are
 * unchanged. The SectionTitle title is not a .sl-panel__titlebar, and
 * the only border-less LinkHeading box in the console is this one —
 * the mosaic LinkHeading component itself carries class
 * .sl-link-heading, so the heading half of the bar is hooked on it. */
/* (5a) Section headings — the rule spans the COLUMN. Mosaic's
 * LinkHeading is a Box rendered as the semantic heading (h2 for
 * SectionTitle, h3 for SectionSubtitle); its width is its content, so
 * round 5's bottom border on .sl-link-heading drew a rule only under
 * the heading TEXT (Peter's screenshot: "Request" and "Query
 * Parameters" underlined to text width). The fix makes the heading
 * block itself full-width — display: block + width: 100% — with the
 * rule as border-bottom on the full-width box plus a small
 * padding-bottom, so the rule runs the whole content column under
 * every console section heading at once: SectionTitle "Request",
 * "Responses", "Callbacks" and SectionSubtitle "Path Parameters",
 * "Query Parameters", "Headers", "Cookies", "Body" (the
 * elements-core census). Heading text, size, and the round-2 color
 * fix (on the inner __link) are untouched.
 * RESPONSES INTERACTION: in the Responses row this REPLACES round
 * 5's heading border — but the round-6 row rule (section (4)) now
 * owns the Responses bar's single border, so the heading inside a
 * tablist-bearing row yields its border to the row via the :has
 * scope in the last rule of this block: exactly one border draws on
 * that shared bottom edge, never two. */
.chomp-docs-console .sl-link-heading {
  display: block;
  width: 100%;
  padding-bottom: 0.35rem;
  border-bottom: 1px solid var(--chomp-slate-200);
}

.chomp-docs-console :has(> .sl-link-heading):has(> * > [role="tablist"]) > .sl-link-heading {
  border-bottom: 0;
  padding-bottom: 0;
}

.chomp-docs-console [role="tablist"] {
  flex: 1 1 auto;
}

.chomp-docs-console [role="tab"][aria-selected="true"] {
  background: var(--chomp-blue);
  box-shadow: none;
  color: #ffffff;
}

/* (4d) Crumbs rhythm. The "responses / 200" bar is json-schema-viewer's
 * PathCrumbs: a sticky mono HStack (h: "md", mt: -8, borderB: true,
 * bg: "canvas-pure") rendered when the viewer receives parentCrumbs —
 * elements-core passes ['responses', <code>] for response schemas. The
 * mt: -8 (-2rem) pulls the bar up against whatever precedes it, and in
 * Peter's screenshot the bar sits flush on the schema's description
 * text ("Root object containing an array of branded food items…"),
 * which the viewer renders as a Box with data-test
 * "property-description". The sticky offset is the viewer's own
 * positioning — fighting it would break the stick — so the rhythm is
 * set below the bar instead: 0.75rem (12px) of space under the crumbs
 * bar before the description, and 0.75rem under the description before
 * the schema tree. The round-2 crumbs rule above (same selector) gains
 * the margin; the description rule is new. */
.chomp-docs-console .JsonSchemaViewer .sl-bg-canvas-pure {
  margin-bottom: 0.75rem;
}

.chomp-docs-console .JsonSchemaViewer [data-test="property-description"] {
  margin-bottom: 0.75rem;
}

/* (6) Send button — white on blue in EVERY state. What paints what,
 * from source: elements-core's TryIt renders the button inside
 * Panel.Content.SendButtonHolder as a mosaic Button, appearance
 * "primary". Mosaic's variant map (variants$6) for primary: resting
 * color "on-primary" (white), bg "primary"; DISABLED color "body",
 * bg "canvas-100", opacity 70. The Button implementation destructures
 * color OUT of the merged props and applies it as the rendered Box's
 * color prop — i.e. as generated utility classes on the button element
 * itself — while bg travels through the state-props path. Peter's
 * close-up (screenshot 7) is the settling datum: the disabled button
 * renders saturated blue with opacity 1 (round 3's bg and opacity pins
 * WON) but its text is dark blue (round 3's color: #fff declarations on
 * the same selectors LOST the color cascade to the bundle's generated
 * state rule). The fix re-asserts the color on the established hooks at
 * higher specificity — the full console scope chain plus the state
 * pseudo-classes — for both the disabled paint and hover, where the
 * variant map's hover bg (primary-dark) over inherited dark text was
 * the same clash. The button's label is a direct text node (no inner
 * span), so the element's own color is the whole fix. Named change:
 * the round-3 Send block's three hooks are EXTENDED with these color
 * pins (hook count 3 → 3, declarations added); the round-1/round-3
 * rules above are untouched and keep governing bg/opacity. */
.chomp-docs-console elements-api button[class*="sl-bg-primary"]:disabled,
.chomp-docs-console elements-api button.sl-bg-canvas-100:disabled {
  color: #ffffff;
}

.chomp-docs-console elements-api button[class*="sl-bg-primary"]:hover:not(:disabled) {
  color: #ffffff;
}

/* (7) Portal menus — ONE system, and the combinator fix. Why round 3
 * painted the submenu but never the main list: mosaic's Menu renders
 * Popover > MenuList, and MenuList WRAPS MenuNodes (class .sl-menu) in
 * a VStack — in the main menu, .sl-menu is a GRANDCHILD of .sl-popover,
 * so round 3's child combinator (body .sl-popover > .sl-menu) never
 * matched it. SubmenuItem, by contrast, renders its own Popover with
 * MenuNodes DIRECTLY inside — the child combinator matched the submenu
 * (class .sl-menu.sl-menu--submenu) and painted it light. That is the
 * whole inconsistency Peter screenshotted: near-black main list, light
 * submenu, blue highlight.
 * What paints the main list dark: MenuNodes renders the root list with
 * an INLINE background of var(--color-canvas-pure) when its theme reads
 * dark (isDark from useThemeIsDark — React context follows the
 * component tree into the console's inverted subtree, not the portal's
 * body-level DOM position). Our bridge re-pins canvas-pure to #020617
 * on elements-api, and at body level no light value ever wins.
 * The fix: the portal block's combinator becomes DESCENDANT
 * (body .sl-popover .sl-menu) — REPLACED, named: the round-3 portal
 * block's 4 rules keep their declarations and counts (4 → 4); only the
 * selector form changes, so the established light system (white surface
 * with !important against the inline style, slate-200 border, 0.65rem
 * radius, max-height min(24rem, 70vh) + internal scroll, slate-700
 * items, brand-blue highlight with white text) now reaches BOTH lists.
 * Two additions inside the same system: (i) rows in the
 * --submenu-active / --focused states that are NOT pointer-hovered get
 * the same blue highlight the submenu already uses, so a parent row
 * like "Node" — whose submenu is open beside it — never renders as
 * pale-gray text on a white block (its exact paint chain in Peter's
 * screenshot has one link I could not isolate from source; see
 * ROUND5-NOTES.md LIMITS); (ii) disabled rows are raised to a slate-500
 * floor — mosaic dims disabled title wrappers to opacity .5, which
 * over the light surface would drop below legible.
 * Census — every .sl-menu portal in the console gets this one system:
 * the Request Samples language menu + its library submenus
 * (elements-core RequestSamples), the Try It auth security-schemes
 * menu (TryItAuth), the servers menu (ServersDropdown, in the Send
 * holder and the server row), the response/mock menus (MockingButton,
 * TryItResponse's ResponseMenu), and the Body panel's OneOfMenu.
 * NOT this family: mosaic Select popovers (the Body/Response
 * content-type select, parameter example selects) render a ListBox,
 * not a Menu — different component, not source-read this round; see
 * LIMITS in the notes. */
body .sl-popover .sl-menu {
  max-height: min(24rem, 70vh);
  overflow-y: auto;
  border: 1px solid var(--chomp-slate-200, #e2e8f0);
  border-radius: 0.65rem;
  background: #ffffff !important;
  box-shadow: 0 18px 38px -18px rgb(15 23 42 / 0.35);
  color: var(--chomp-slate-700, #334155);
}

body .sl-popover .sl-menu .sl-menu-item {
  color: var(--chomp-slate-700, #334155);
}

body .sl-popover .sl-menu .sl-menu-item:not(.sl-menu-item--disabled):hover,
body .sl-popover .sl-menu .sl-menu-item--focused {
  background: var(--chomp-blue, #3b82f6);
  color: #ffffff;
}

body .sl-popover .sl-menu .sl-menu-item--submenu-active {
  background: var(--chomp-blue, #3b82f6);
  color: #ffffff;
}

body .sl-popover .sl-menu .sl-menu-item--disabled {
  color: var(--chomp-slate-500, #64748b);
}

/* ==========================================================================
 * ROUND 6 — repair round on Peter's round-5 re-test (2026-11-10).
 * Five findings: nav (block replaced in place above), Try It padding +
 * user_id subtext, right-rail code panels, Responses rule alignment,
 * section-heading rules + Security double border (in place above).
 * ======================================================================== */

/* (2b) user_id subtext in the Try It grid. Elements exposes NO parameter
 * descriptions anywhere in the grid DOM, but the label IS a native
 * <label aria-hidden="true" htmlFor="<id>"> whose text is the parameter
 * name verbatim — so an attribute-substring selector on the exact name
 * pins the row without any positional guessing.
 * ROUND 7 CORRECTION (live DOM dump, 2026-11-10): the round-6 hook
 * label[for$="user_id"] matched NOTHING — the rendered `for` is a
 * generated id, "id_user_id_<random>" (dumped: id_user_id_7nCcVmRa),
 * which CONTAINS the name but does not END with it; and the note's
 * placement premise was wrong CSS — a ::after on a grid ITEM is not
 * itself a grid item, so grid-column could never give it its own
 * row. The corrected hook is label[for*="user_id"] (contains), and
 * the note renders as a plain block UNDER the name inside the label
 * cell, wrapping at the label column's width; the row grows to fit
 * it, which is the callout Peter asked for. Content: one short line;
 * the full MAU
 * explanation already renders in the main column's Query Parameters
 * section from the spec description and is deliberately NOT duplicated
 * here. The label itself is aria-hidden in the bundle; the note is
 * decorative-identical (the control's aria-label carries the name), so
 * pointer-events: none and no ARIA role. If a future bundle renames the
 * label or the parameter, this rule silently no-ops — the main-column
 * description remains the record. */
.chomp-docs-console .ParameterGrid > label[for*="user_id"] {
  align-self: start;
}

.chomp-docs-console .ParameterGrid > label[for*="user_id"]::after {
  content: "Premium subscribers only — required for MAU usage tracking.";
  display: block;
  /* Round 9: capped measure. Uncapped, the note's single-line
   * max-content can stretch a content-sized label track (and
   * even in a capped track its longest line ran to the track's
   * edge — Peter: "the subtext has no padding"). 12rem keeps
   * the note inside the label column's own measure, and the
   * grid's new column-gap guarantees the gutter after it. */
  max-width: 12rem;
  margin-top: 0.25rem;
  color: var(--chomp-slate-500);
  font-size: 0.72rem;
  font-weight: 500;
  line-height: 1.35;
  pointer-events: none;
}

/* Round 9 — the clipped select (Peter's round-8 re-test: the
 * `limit` select's placeholder runs off the panel's right edge,
 * its box shifted right of the text inputs with no right border
 * or chevron visible). Mosaic's Select trigger sizes to its
 * widest option; inside the grid's flex control cell, neither
 * the cell nor the trigger would shrink below that content
 * width, so the panel's overflow clip took the excess off the
 * right side. The shrink kit: control cells (every row's third
 * child — the triplet structure is dumped fact) may shrink,
 * and every form control inside a grid is capped at its cell.
 * The trigger's own classes were not in the DOM dump; the kit
 * targets the cell + the standard control hooks, which is
 * where the overflow is generated. */
.chomp-docs-console .ParameterGrid > :nth-child(3n) {
  min-width: 0;
}

.chomp-docs-console .ParameterGrid :is(input, select, button, [aria-haspopup="listbox"]) {
  min-width: 0;
  max-width: 100%;
}

/* (3) Right-rail code panels (Request Sample / Response Example) — ONE
 * radius system. Census of the rounded layers, from source:
 *   L1 the panel chrome — our .sl-panel rule: 1px slate-200 border,
 *      1.05rem radius, overflow hidden (rounds 1–2; SURVIVES — it is
 *      the one frame).
 *   L2 the titlebar — mosaic PanelTitlebar with appearance "default"
 *      (RequestSamples / TryItResponse pass no appearance) paints
 *      bg canvas-200 with NO radius of its own; its SQUARE top corners
 *      sit on the panel's rounded clip, which is what reads as a
 *      rounded header inside a rounded panel. It now takes the panel's
 *      own radius on its top corners only, so header and frame share
 *      one corner; its bottom stays square against the body.
 *   L3 the header controls — the titlebar's Menu trigger renders as a
 *      DEFAULT mosaic Button (bordered box: sl-form-group-border), and
 *      CopyButton is appearance "minimal" (borderless) but carries the
 *      bundle's radius + padding box. Both lose their box frames on
 *      these two panels: no border, no radius, transparent at rest,
 *      slate-100 wash on hover — clearly interactive, not boxed. The
 *      scoping attribute (aria-label "Request Sample Language" on the
 *      Menu; the CopyButton is the titlebar's rightComponent) plus the
 *      Panel.Content sibling hook keep this off every other panel's
 *      titlebar controls (Auth's schemes menu keeps the established
 *      treatment).
 *   L4 the code body — Panel.Content p: 0 > CodeViewer (the dark
 *      surface, deliberate since round 2 — KEPT). Its container is
 *      square-cornered; the rounded read came from L1's clip stacking
 *      with L2/L3. With the header squared into the frame and the
 *      controls ghosted, body + header read as one joined panel; the
 *      body also takes the panel radius on its BOTTOM corners so the
 *      dark surface itself closes the frame instead of being clipped
 *      into it.
 * The hook: .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer)
 * selects exactly the panels whose body is a code viewer — Request
 * Sample and Response Example (and the response-side TryItResponse
 * panel) — and nothing else in the console. */
.chomp-docs-console .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer) > .sl-panel__titlebar {
  border-radius: 1.05rem 1.05rem 0 0;
}

.chomp-docs-console .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer) > .sl-panel__content-wrapper .sl-code-viewer {
  border-radius: 0 0 1.05rem 1.05rem;
}

.chomp-docs-console .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer) .sl-panel__titlebar button {
  border: 0;
  border-radius: 0;
  background: transparent;
  box-shadow: none;
}

.chomp-docs-console .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer) .sl-panel__titlebar button:hover {
  background: var(--chomp-slate-100);
}

/* (4) Responses header — the rule lives on the ROW. Round 5 put a
 * bottom border on the heading box AND kept round 2's on the tablist,
 * but the two boxes are different heights inside the SectionTitle flex
 * row (heading: py 1 around an h2 line box; tablist wrapper:
 * alignSelf center), so the two rules rendered at two heights and the
 * active chip — a child of the tablist, painted from its own top —
 * overhung the tablist's rule. Restructure per the robust
 * construction: the SectionTitle ROW ITSELF (the direct parent of
 * .sl-link-heading — the only SectionTitle in the console whose tablist
 * is a sibling; verified against elements-core: "Request"/"Callbacks"
 * SectionTitles carry no tablist) carries the single border-bottom;
 * heading box and tablist carry NONE (round 5's heading rule is
 * REMOVED in place below this section — see the survivals table —
 * and round 2's tablist border, already replaced by round 5's flex
 * rule, stays borderless). The row's two children are cross-axis
 * centered (align-items: center) so title and tabs share one vertical
 * center against the row's bottom edge, and the tablist wrapper's
 * alignSelf: center is overridden to stretch so the tabs' row fills
 * the row height — the chip then sits INSIDE the row with its fill
 * clear of the rule (chosen over a -1px overlap: the chip reads as a
 * selected pill above the rule, never crossing it). Chip treatment
 * itself (filled brand blue, white text) is unchanged from round 5. */
/* ROUND 7 CORRECTION (live DOM dump, 2026-11-10): the round-6 row
 * selector above demanded the tablist as a DIRECT child of the row;
 * the dump shows the row's children are the h2 and a flex wrapper
 * (sl-flex-grow sl-self-center sl-py-1), with the tablist inside the
 * wrapper — the round-6 rules matched nothing. Dumped geometry:
 * heading bottom = row bottom = 1922.6; tablist bottom = 1918.6 —
 * the wrapper's sl-py-1 bottom padding is exactly the 4px gap Peter
 * flagged. Corrected selectors (:has(> * > [role="tablist"])), and
 * the wrapper now stretches the row's full height with its bottom
 * padding removed and the tablist end-aligned, so the chip's bottom
 * edge lands ON the row's rule — one line, tabs ending at it. */
.chomp-docs-console :has(> .sl-link-heading):has(> * > [role="tablist"]) {
  border-bottom: 1px solid var(--chomp-slate-200);
  align-items: center;
}

.chomp-docs-console :has(> .sl-link-heading) > :has(> [role="tablist"]) {
  align-self: stretch;
  align-items: flex-end;
  padding-bottom: 0;
}

/* ==========================================================================
 * ROUND 7 — repair round on Peter's round-6 re-test (2026-11-10).
 * Passed in round 6: code panels, heading rules. Failed: nav pill,
 * sidebar padding, user_id subtext, Responses alignment, Security
 * inner borders. Nav + padding fixes are in place above (nav rule;
 * flatten rule). This section carries the rest. The user_id,
 * Responses, and Security hooks in this section are written against
 * Peter's LIVE DOM dump (collected 2026-11-10, chat) — not bundle
 * source inference; rounds 5–6 missed exactly where source and DOM
 * diverged.
 * ======================================================================== */

/* (7a) Code-viewer panel contents keep padding: 0 EXPLICITLY. Through
 * round 6 they rendered at 0 only because the round-5 flatten rule
 * zeroed every panel content (see that rule's round-7 note); with
 * the zeroing removed, the samples/response bodies would gain the
 * restored 1rem and the dark surface would stop spanning its panel.
 * Peter's round-6 verdict: code panels look better — no regression.
 * Specificity (0,4,0) via the :has argument beats the (0,2,0)
 * padding restore on exactly the code panels. */
.chomp-docs-console .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer) .sl-panel__content {
  padding: 0;
}

/* (7b) Security scheme box — the "panel inside the collapsible
 * panel." Live DOM dump (2026-11-10): inside the Security panel's
 * content sits ONE scheme box, a plain div carrying exactly
 * sl-m-2 + sl-p-2 + sl-border, computed borders 1px on all four
 * sides — the duplicate frame Peter flagged in rounds 5, 6, and 7's
 * re-test. (The only other bordered elements the dump found inside
 * the panel are the inline <code> chips, which keep their border —
 * that is the code-chip treatment, not a frame.) Round 5's flatten
 * rule aimed at this box but targeted the content WRAPPER's
 * children — one level too high; the box is a descendant of the
 * panel CONTENT. Flattened here by its dumped class signature:
 * no border, no margin, no padding — its text sits directly on the
 * panel surface, inset by the content's restored 1rem padding.
 * The signature (margin + padding + border utilities on one plain
 * div inside a panel content) is distinctive in this console; if a
 * future bundle re-classes the box, the rule no-ops and the panel
 * border alone remains. */
.chomp-docs-console .sl-panel__content div.sl-border.sl-p-2.sl-m-2 {
  border: 0;
  margin: 0;
  padding: 0;
}

/* ==========================================================================
 * ROUND 8 — Peter's round-7 re-test (2026-11-10): the sidebar grids.
 * One declaration-level fix, in place at the ParameterGrid layout
 * rule above (see its Round 8 comment): padding 1rem, margin-bottom
 * 0. Everything else in this file is byte-identical to round 7.
 * ======================================================================== */

/* ==========================================================================
 * ROUND 9 — Peter's round-8 re-test (2026-11-10): two nits in the
 * sidebar grids. Column-gap + the subtext's capped measure are in
 * place at the grid rule and the user_id rule above; the select
 * shrink kit sits with the user_id rules in the round-6 section.
 * Everything else is byte-identical to round 8.
 * ======================================================================== */

/* ==========================================================================
 * ROUND 10 — Peter's round-9 re-test (2026-11-10): the docs work and
 * requests work; what remained was plan visibility, the sidebar
 * (Try It rail) geometry, and example quality. The spec half of this
 * round (user_id reordered first on all four endpoints, plan
 * callouts, real examples from live v2 responses) ships in
 * openapi.yml; this section is the CSS half.
 *
 * (a) The rail grids. The main-column grids have ~870px to work
 * with; the Try It rail is capped at 500px by the two-column
 * layout, so the shared label track (minmax(9rem, 13rem)) left the
 * control column ~200px — Peter: "these inputs are still really
 * small and clipped on the sidebars". The bundle's own grid caps
 * the label at 120px. Rail-scoped: the label track drops to
 * minmax(6.75rem, 8.75rem), handing the controls ~280px. The
 * hook is the dumped TryItPanel ancestor — the main-column grids
 * are not inside it and keep the wide track.
 * ======================================================================== */
.chomp-docs-console .TryItPanel .ParameterGrid {
  grid-template-columns: minmax(6.75rem, 8.75rem) minmax(0, 1fr);
}

/* (b) The response status line. Dumped 2026-11-10: the status is a
 * plain div.sl-mb-3.sl-text-green inside the panel content. Nothing
 * paints it — the bundle ships no .sl-text-green rule (the color
 * comes from mosaic's runtime theme sheet, which our re-pins
 * bypass), so it inherited the console's slate-700 at the root
 * 15px scale and read as a stray headline above the code viewer
 * (Peter: "the status code looks strange"). Painted directly:
 * smaller, semibold, and green again for 2xx; the red/amber
 * siblings follow mosaic's naming pattern for error statuses. */
.chomp-docs-console .sl-mb-3.sl-text-green,
.chomp-docs-console .sl-mb-3.sl-text-red,
.chomp-docs-console .sl-mb-3.sl-text-amber {
  font-size: 0.85rem;
  font-weight: 650;
  letter-spacing: 0.01em;
}

.chomp-docs-console .sl-mb-3.sl-text-green {
  color: #16a34a;
}

.chomp-docs-console .sl-mb-3.sl-text-red {
  color: #dc2626;
}

.chomp-docs-console .sl-mb-3.sl-text-amber {
  color: #d97706;
}

/* (c) user_id, color-coded. The spec reorder puts the parameter
 * first in every grid; this makes the row read as the premium row
 * it is: a violet PREMIUM pill before the name, the note recolored
 * to match, and the control cell washed violet with the control's
 * border picked up. The pill is decorative — the premium fact is
 * stated in the main column's parameter description. */
.chomp-docs-console .ParameterGrid > label[for*="user_id"]::before {
  content: "PREMIUM";
  display: inline-block;
  margin-right: 0.45rem;
  padding: 0.1rem 0.42rem;
  border-radius: 9999px;
  background: #7c3aed;
  color: #ffffff;
  font-size: 0.6rem;
  font-weight: 700;
  letter-spacing: 0.06em;
  vertical-align: 0.14em;
  pointer-events: none;
}

.chomp-docs-console .ParameterGrid > label[for*="user_id"]::after {
  color: #6d28d9;
  font-weight: 600;
}

.chomp-docs-console .ParameterGrid > label[for*="user_id"] + * + * {
  background: #f5f3ff;
  border-radius: 1rem;
  padding: 0.3rem;
  margin: -0.3rem;
}

.chomp-docs-console .ParameterGrid > label[for*="user_id"] + * + * :is(input, select, button, [aria-haspopup="listbox"]) {
  border-color: #a78bfa;
}

/* (d) Plan-availability callouts. The three restricted endpoints
 * now lead their spec description with a markdown blockquote; the
 * operation description renders it inside the HttpOperation's
 * markdown viewer. Styled as a callout: blue wash, a solid left
 * bar, the quote's own paragraph spacing removed. Blockquotes
 * appear nowhere else in an operation today, so the treatment is
 * unambiguous; the overview (outside .HttpOperation) is untouched. */
.chomp-docs-console .HttpOperation .sl-markdown-viewer blockquote,
.chomp-docs-console .HttpOperation .sl-markdown blockquote {
  margin: 0 0 1rem;
  padding: 0.7rem 1rem;
  border: 0;
  border-left: 0.25rem solid var(--chomp-blue);
  border-radius: 0 0.75rem 0.75rem 0;
  background: #eff6ff;
  color: var(--chomp-slate-700);
}

.chomp-docs-console .HttpOperation .sl-markdown-viewer blockquote p,
.chomp-docs-console .HttpOperation .sl-markdown blockquote p {
  margin: 0;
}

/* ==========================================================================
 * ROUND 11 — Peter's round-10 re-test (2026-11-10): five findings.
 * The hooks in this section are written against Peter's live DOM
 * dump of 2026-11-11 (chat): the Show-all toggle is an
 * A.sl-link.sl-cursor-pointer inside the JsonSchemaViewer's
 * markdown descriptions; the required badge is a
 * SPAN.sl-ml-2.sl-text-warning beside the parameter name; the rail
 * Response panel's content computes padding 0px because it is a
 * code-viewer panel (round 7a zeroed those contents on purpose).
 * The spec half of this round (endpoint summary renames for the
 * sidebar) ships in openapi.yml.
 * ======================================================================== */

/* (a) Sidebar active item, nav-scoped twin. The in-place rule at
 * the sidebar section carries the strengthened values (blue-200
 * fill, blue-600 bar, blue-900 text, weight 700) at specificity
 * (0,3,0). This twin repeats them one element deeper — (0,3,1) —
 * so if mosaic's runtime theme sheet is what outranked the rule
 * on Peter's display, the twin outranks it back; if the values
 * alone were the problem, the twin is a harmless duplicate. */
.chomp-docs-console nav .ElementsTableOfContentsItem.active,
.chomp-docs-console nav .ElementsTableOfContentsItem[aria-current="page"],
.chomp-docs-console nav .ElementsTableOfContentsItem[aria-current="true"] {
  background: #bfdbfe;
  box-shadow: inset 0.25rem 0 0 #2563eb;
  color: #1e3a8a;
  font-weight: 700;
}

/* (b) "Show all..." must read as a link. Dumped: the toggle is an
 * anchor (A.sl-link.sl-cursor-pointer) rendered inside a parameter
 * description's markdown in the schema viewer — but nothing paints
 * it as one, so it read as plain text (Peter: "needs to seem more
 * clickable. blue link?"). Blue, underlined. The selector reaches
 * every description link in the schema viewer; those are all real
 * links, so the treatment is correct wherever it lands. */
.chomp-docs-console .JsonSchemaViewer a.sl-link {
  color: #2563eb;
  text-decoration: underline;
  text-underline-offset: 0.15em;
}

/* (c) Required parameters, color-coded. Peter's round-10 ask sits
 * next to round 10's user_id coding: the required set gets the
 * same treatment in orange. Three surfaces:
 *  - the rail labels for the three required parameters (their
 *    generated control ids carry the parameter name: id_code_ on
 *    barcode lookup, id_name_ on search by name, id_find_ on
 *    ingredient search — the same hook family as user_id, and no
 *    other parameter's id contains those strings);
 *  - the main-column parameter NAME on rows that carry the
 *    required badge (dumped badge: SPAN.sl-text-warning inside the
 *    row; the name is the row's mono semibold element);
 *  - the badge itself, painted to match and set bold, since the
 *    bundle ships no reliable color for it. */
.chomp-docs-console .ParameterGrid > label[for*="id_code_"],
.chomp-docs-console .ParameterGrid > label[for*="id_name_"],
.chomp-docs-console .ParameterGrid > label[for*="id_find_"] {
  color: #c2410c;
}

.chomp-docs-console .JsonSchemaViewer .sl-py-2:has(.sl-text-warning) .sl-font-mono.sl-font-semibold {
  color: #c2410c;
}

.chomp-docs-console .JsonSchemaViewer span.sl-text-warning {
  color: #c2410c;
  font-weight: 700;
}

/* (d) The rail status line's inset. The Response panel is a
 * code-viewer panel, whose content round 7a deliberately keeps at
 * padding 0 so the dark code surface spans edge to edge — but the
 * status line lives in that same content, above the code viewer,
 * so it sat flush on the panel's top and left edges (Peter: "the
 * padding is off — it hugs the top and left"; the 2026-11-11 dump
 * computes the content's padding at 0px). The code surface keeps
 * its zero; the status line carries its own inset. The scope is
 * the same :has hook as 7a, so the main column's Response Example
 * status — same panel family, same zero — gets the identical
 * inset. */
.chomp-docs-console .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer) .sl-mb-3.sl-text-green,
.chomp-docs-console .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer) .sl-mb-3.sl-text-red,
.chomp-docs-console .sl-panel:has(> .sl-panel__content-wrapper .sl-code-viewer) .sl-mb-3.sl-text-amber {
  padding: 0.85rem 1rem 0.15rem;
}

/* ==========================================================================
 * ROUND 12 — Peter's round-11 re-test add-ons (2026-11-11): the
 * plan callout and the schema property examples. Hooks from his
 * second live dump the same morning. The spec half (the three
 * largest property examples trimmed to single entries) ships in
 * openapi.yml.
 * ======================================================================== */

/* (a) One callout, not two. The dump names the stack: the
 * blockquote itself (class sl-callout) carries this sheet's round
 * 10 treatment — light blue wash, slate text — but mosaic's
 * Callout component renders an inner card as its direct child
 * (a stack div with sl-bg-canvas-pure and a 2px primary border)
 * whose computed background is rgb(2, 6, 23), near-black, with
 * slate-200 text inherited from it. The result read as a dark
 * alert box floating inside the light callout. The card is
 * neutralized — transparent background, no border, slate-700
 * text — so the icon and the words sit directly on the wash and
 * the callout is a single light box, as round 10 intended. */
.chomp-docs-console .HttpOperation blockquote.sl-callout > div.sl-bg-canvas-pure {
  background: transparent;
  border: 0;
  color: var(--chomp-slate-700);
}

/* (b) Property examples: a size bump. The dump puts the example
 * value in a flex-wrap container inside the muted example line,
 * computed at 11px against the viewer's 14.8px — part of why the
 * flattened JSON read as a wall. The container takes 0.8125rem
 * (13px) with looser leading. Best-effort by construction: if the
 * value's own child element sets its size, inheritance stops
 * there and the round's spec trims carry the readability win on
 * their own (diet_flags 629 -> 317 chars, diet_labels 558 ->
 * 175, packaging_photos 313 -> 213). */
.chomp-docs-console .JsonSchemaViewer .sl-text-muted .sl-flex-wrap {
  font-size: 0.8125rem;
  line-height: 1.5;
}

/* (c) The selected sidebar item — no rule here, on purpose.
 * Peter's probe (2026-11-11) showed the library marks NO item
 * active in this embed: 7 table-of-contents items, zero .active,
 * zero aria-current, the open endpoint's anchor computing a
 * transparent background. That is why the strengthened treatments
 * of rounds 10–11 changed nothing — their selectors had no
 * target. The marker now comes from a small script in the docs
 * template (views/public/api/docs/interactive.html) that adds
 * .active + aria-current to the item whose href equals the
 * current hash; the round 10/11 rules above (blue-200 fill,
 * inset bar, blue-900, weight 700) are the treatment it lands
 * on. */

/* ==========================================================================
 * ROUND 13 — Peter's round-12 re-test (2026-11-11): the active
 * sidebar item showed two boxes — this sheet's blue-200 fill on
 * the anchor, and a pale box inside it. Same stacking disease as
 * the round-12 callout: now that the template script applies
 * .active, mosaic's own active treatment fires on the item's
 * inner content and paints it pale, inside the anchor's fill.
 * One box is the design: descendant backgrounds inside the
 * active item are neutralized, so the anchor's blue-200 pill,
 * inset bar, and bold blue-900 text are the whole treatment.
 * Nothing inside a table-of-contents item needs a background
 * of its own (the icon is an SVG fill; the labels are text).
 * ======================================================================== */
.chomp-docs-console .ElementsTableOfContentsItem.active *,
.chomp-docs-console .ElementsTableOfContentsItem[aria-current="page"] *,
.chomp-docs-console .ElementsTableOfContentsItem[aria-current="true"] *,
.chomp-docs-console nav .ElementsTableOfContentsItem.active *,
.chomp-docs-console nav .ElementsTableOfContentsItem[aria-current="page"] *,
.chomp-docs-console nav .ElementsTableOfContentsItem[aria-current="true"] * {
  background: transparent;
}

/* ==========================================================================
 * ROUND 14 — the schema pages in the tablet band (Peter,
 * 2026-11-11: "any way to make the docs look better/work better
 * on mobile screens?"). His screenshot + dump at a 1001px
 * viewport name the mechanism exactly: the Model page's content
 * column is 405px wide after the 299px sidebar and the page
 * chrome, and its description-plus-Example row never stacks —
 * the Example rail (sl-w-2/5 + sl-ml-16, the same rail classes
 * as the operation pages) takes 162px plus a 64px margin, and
 * the description is left wrapping at 179px. The library's own
 * stacking breakpoints sit at 975px and below, so the broken
 * band is 976px up to the width where the description recovers
 * (~1250px, derived from the dumped widths: description =
 * 0.6 x content - 64px). In that band the row stacks: rail
 * full-width below the description, margin converted from left
 * to top. Desktop above 1250px is untouched, and below 975px
 * this agrees with the library's own stacking. The operation
 * pages are NOT stacked here — their rail was designed down to
 * ~200px controls in round 10 and degrades gracefully in this
 * band; the Model row is the one that breaks.
 * ======================================================================== */
@media (max-width: 1250px) {
  .chomp-docs-console .Model > .sl-flex:has(> .sl-w-2\/5) {
    flex-direction: column;
  }

  .chomp-docs-console .Model > .sl-flex:has(> .sl-w-2\/5) > * {
    width: 100%;
    max-width: 100%;
  }

  .chomp-docs-console .Model > .sl-flex > .sl-w-2\/5.sl-ml-16 {
    margin-left: 0;
    margin-top: 1.5rem;
  }
}

/* ==========================================================================
 * ROUND 15 — the collapsible endpoint sidebar (Peter, 2026-11-11:
 * "any way we can make the left endpoint sidebar panel collapse
 * on smaller screens? hamburger menu or something?"). Round 14
 * fixed the 976–1250px band; below it the crush persists for a
 * different reason: the library stacks the CONTENT at its 975px
 * breakpoint but still renders the table of contents as a fixed
 * 299px column (measured in Peter's 500px probe), leaving a
 * phone ~200px of content. First impressions arrive on phones —
 * the column has to go.
 *
 * Mechanism: the template script (round 15, in interactive.html)
 * tags the TOC column with .chomp-toc-column and flags the
 * workspace .chomp-toc-ready; the toolbar carries an Endpoints
 * toggle button. Inside the max-width: 975px media query below,
 * the tagged column is display:none by default (content takes
 * the full width) and becomes a fixed drawer when the workspace
 * carries .chomp-toc-open (the script toggles it, and closes it
 * on any hash navigation — i.e. whenever an endpoint is picked).
 * The toggle only appears when the column was actually tagged,
 * so a tagging miss degrades to today's behavior, never to a
 * dead button. Desktop is untouched: the toggle is display:none
 * outside the media query, and no rule here applies above 975px.
 * ======================================================================== */
.chomp-docs-toc-toggle {
  display: none;
}

@media (max-width: 975px) {
  .chomp-docs-workspace.chomp-toc-ready .chomp-docs-toc-toggle {
    display: inline-flex;
    align-items: center;
    gap: 0.5rem;
    padding: 0.5rem 0.8rem;
    border: 1px solid var(--chomp-slate-200, #e2e8f0);
    border-radius: 0.75rem;
    background: #fff;
    color: var(--chomp-slate-700);
    font: inherit;
    font-size: 0.9rem;
    font-weight: 600;
    cursor: pointer;
  }

  .chomp-docs-workspace.chomp-toc-open .chomp-docs-toc-toggle {
    position: relative;
    z-index: 50;
  }

  .chomp-docs-console .chomp-toc-column {
    display: none;
  }

  .chomp-docs-workspace.chomp-toc-open .chomp-docs-console .chomp-toc-column {
    display: block;
    position: fixed;
    top: 0;
    bottom: 0;
    left: 0;
    z-index: 40;
    width: min(320px, 85vw);
    overflow-y: auto;
    background: #f8fafc;
    box-shadow: 0 20px 40px rgba(15, 23, 42, 0.25);
  }
}

/* ==========================================================================
 * ROUND 16 — the toggle becomes a floating button, and the
 * drawer gets a backdrop (Peter, 2026-11-11, on round 15's
 * re-test screenshots: "can we make endpoints menu a bit more
 * noticeable? It's easy to miss and scroll past. also when
 * opened it overlays very poorly and the endpoints button is
 * still visible through the sidebar panel"). Both observations
 * are accurate: the ghost pill in the toolbar read as decoration
 * and vanished on scroll, and round 15 deliberately kept the
 * toggle clickable above the drawer (z-index 50), which painted
 * it floating over the drawer's middle.
 *
 * The toggle is now a floating action button at max-width
 * 975px: fixed bottom-right, brand blue, always on screen —
 * it cannot be scrolled past. When the drawer opens, a dimmed
 * backdrop (z-index 30) covers the page INCLUDING the button
 * (z-index 20), so nothing shows through; round 15's z-lift is
 * explicitly superseded below. Closing is by backdrop tap, by
 * picking an endpoint (hashchange, in the script), from the
 * toggle, or from the close button the script places inside
 * the drawer. The drawer also gains top padding so its list
 * starts below the site's floating header pill instead of
 * sliding under it.
 * ======================================================================== */
.chomp-docs-toc-backdrop,
.chomp-toc-close {
  display: none;
}

@media (max-width: 975px) {
  .chomp-docs-workspace.chomp-toc-ready .chomp-docs-toc-toggle {
    position: fixed;
    right: 1rem;
    bottom: calc(1rem + env(safe-area-inset-bottom));
    z-index: 20;
    padding: 0.7rem 1.1rem;
    border: 0;
    border-radius: 999px;
    background: #2563eb;
    color: #fff;
    box-shadow: 0 10px 25px rgba(15, 23, 42, 0.35);
    font-size: 0.95rem;
  }

  /* Supersedes round 15's z-lift: open or closed, the button
     stays under the backdrop and never paints over the drawer. */
  .chomp-docs-workspace.chomp-toc-open .chomp-docs-toc-toggle {
    position: fixed;
    z-index: 20;
  }

  /* Round 17: the backdrop element now lives inside the console
     (the template script appends it under the layout root, next
     to the column). The console carries isolation: isolate from
     the original overhaul, so the drawer's z-index competes only
     inside the console — a page-level backdrop painted over the
     whole console unit, drawer included (Peter's round-16
     screenshot: the dim covered the open sidebar too). Inside
     the same context, z-index 30 sits under the column's 40 and
     over the content, which is the intent. */
  .chomp-docs-workspace.chomp-toc-open .chomp-docs-console .chomp-docs-toc-backdrop {
    display: block;
    position: fixed;
    inset: 0;
    z-index: 30;
    background: rgba(15, 23, 42, 0.45);
  }

  /* The floating button must not linger over the dim while the
     drawer is open, whatever the stacking order does. */
  .chomp-docs-workspace.chomp-toc-open .chomp-docs-toc-toggle {
    visibility: hidden;
  }

  .chomp-docs-workspace.chomp-toc-open .chomp-docs-console .chomp-toc-column {
    padding-top: 5.5rem;
  }

  .chomp-docs-console .chomp-toc-column .chomp-toc-close {
    display: flex;
    position: absolute;
    top: 6rem;
    right: 0.75rem;
    z-index: 5;
    width: 2.25rem;
    height: 2.25rem;
    align-items: center;
    justify-content: center;
    padding: 0;
    border: 1px solid #e2e8f0;
    border-radius: 999px;
    background: #fff;
    color: #475569;
    box-shadow: 0 4px 12px rgba(15, 23, 42, 0.12);
    cursor: pointer;
  }
}

/* ==========================================================================
 * ROUND 18 — one surface, no mid-panel attribution, no straddle
 * (Peter, 2026-11-11, on the round-17 screenshot: the dim is
 * fixed, but the open panel mixes two shades of gray, its inner
 * border stops halfway down, "powered by Stoplight" sits in the
 * middle of the panel, the close button straddles the panel
 * edge over the title, and the panel butts against the site's
 * top navigation). The mechanics behind each: the column paints
 * slate-50 (#f8fafc, round 15) full-height while the inner
 * sidebar box paints canvas-100 over only the content height —
 * two near-identical shades meeting at the attribution, which
 * also carries the box's right border, so the border dies there
 * too. The close button, hung at the title's height from round
 * 16, lands on the panel edge because the title runs under it.
 *
 * Fixes, all inside the small-screen drawer state:
 * - The drawer starts below the site's floating header pill
 *   (top: 5.5rem, replacing round 15's top: 0 and round 16's
 *   compensating padding-top) with a rounded top-right corner.
 * - One surface: the column paints slate-100 (#f1f5f9) and the
 *   inner box and its stack child go transparent with their
 *   border colors cleared, so no second shade and no border
 *   that stops mid-panel.
 * - The attribution wrapper (tagged by the script as
 *   .chomp-toc-attribution) is display:none in the drawer.
 *   Desktop keeps it, at the sidebar's foot, where it was.
 * - The in-drawer close button is retired (its creation is
 *   removed from the script; the round-16 rules for it are
 *   inert). Closing is the backdrop tap or picking an
 *   endpoint — the standard drawer patterns, with nothing
 *   straddling the panel edge.
 * ======================================================================== */
@media (max-width: 975px) {
  .chomp-docs-workspace.chomp-toc-open .chomp-docs-console .chomp-toc-column {
    top: 5.5rem;
    padding-top: 0;
    border-top-right-radius: 1rem;
    background: #f1f5f9;
  }

  .chomp-docs-workspace.chomp-toc-open .chomp-docs-console .chomp-toc-column .sl-bg-canvas-100,
  .chomp-docs-workspace.chomp-toc-open .chomp-docs-console .chomp-toc-column .sl-bg-canvas-100 > * {
    background: transparent;
    border-color: transparent;
  }

  .chomp-docs-console .chomp-toc-column .chomp-toc-attribution {
    display: none;
  }
}

/* ==========================================================================
 * ROUND 19 — button to the left, a close bar in the drawer, and
 * the attribution off everywhere (Peter, 2026-11-11, on the
 * round-18 screenshot — "now we're getting somewhere"): move
 * the floating Endpoints button to the left side, the same
 * side the drawer opens from, and put the way back out at the
 * bottom of the drawer, roughly where the button sits on the
 * screen — a Close bar pinned across the drawer's foot (the
 * script creates it inside the column at tagging time; the
 * column gains bottom padding in the open state so the last
 * list items scroll clear of it). And remove the "powered by
 * Stoplight" attribution on ALL screen sizes, not just the
 * drawer — the global rule below supersedes round 18's
 * drawer-scoped one (which stays, harmlessly redundant).
 * ======================================================================== */
.chomp-toc-closebar {
  display: none;
}

.chomp-docs-console .chomp-toc-column .chomp-toc-attribution {
  display: none;
}

@media (max-width: 975px) {
  .chomp-docs-workspace.chomp-toc-ready .chomp-docs-toc-toggle {
    left: 1rem;
    right: auto;
  }

  .chomp-docs-workspace.chomp-toc-open .chomp-docs-console .chomp-toc-column {
    padding-bottom: 4.25rem;
  }

  .chomp-docs-workspace.chomp-toc-open .chomp-docs-console .chomp-toc-column .chomp-toc-closebar {
    display: flex;
    position: absolute;
    left: 0;
    right: 0;
    bottom: 0;
    z-index: 6;
    align-items: center;
    justify-content: center;
    gap: 0.5rem;
    padding: 0.9rem 1rem calc(0.9rem + env(safe-area-inset-bottom));
    border: 0;
    border-top: 1px solid #e2e8f0;
    background: #f8fafc;
    color: var(--chomp-slate-700);
    font: inherit;
    font-size: 0.95rem;
    font-weight: 600;
    cursor: pointer;
  }
}

/* ==========================================================================
 * ROUND 20 — the endpoint pages stack on phones too (Peter,
 * 2026-11-11, screenshot of Barcode lookup at phone width:
 * "on mobile screens I see the params and responses sidebar on
 * the right side all mangled and cut off too"). Round 14 stacked
 * the schema pages' row in the tablet band on the working
 * assumption that the library stacks the ENDPOINT layout itself
 * below 975px. It does not — not in this embed: the operation
 * page keeps its desktop row (description column beside the
 * Try It rail, sl-w-2/5 + sl-ml-16), so at phone width the rail
 * panels' fixed-width contents overflow the ~200px rail and the
 * shell clips them at the viewport edge: Auth and Parameters
 * panels cut mid-field, the Send button truncated, the Request
 * Sample panel sliced.
 *
 * Same treatment as the schema row, in the phone band (max-width
 * 975px, aligned with the drawer breakpoint): the operation
 * row — the flex child of .HttpOperation that contains the
 * rail — goes column; the main column and the rail go full
 * width; the rail's left margin converts to a top margin. The
 * 976–1250px band keeps the side-by-side layout deliberately:
 * there the rail is ~250px and its controls were designed down
 * to ~200px in round 10. CSS only; no template change.
 * ======================================================================== */
@media (max-width: 975px) {
  .chomp-docs-console .HttpOperation > .sl-flex:has(.sl-w-2\/5) {
    flex-direction: column;
  }

  .chomp-docs-console .HttpOperation .sl-w-3\/5,
  .chomp-docs-console .HttpOperation .sl-w-2\/5.sl-ml-16 {
    width: 100%;
    max-width: 100%;
  }

  .chomp-docs-console .HttpOperation .sl-w-2\/5.sl-ml-16 {
    margin-left: 0;
    margin-top: 1.5rem;
  }
}

/* ==========================================================================
 * ROUND 21 — the stacked main column was zero-width (Peter's
 * round-20 re-test screenshots + his DOM dump at 641px, both
 * 2026-11-11). Round 20's stacking worked — the dump shows the
 * operation row at flex-direction: column and the rail at the
 * full 363px content width — but the main column measures
 * w 0: it carries sl-flex-1 + sl-w-0, the classic flex-child
 * pattern where flex-1 supplies the size along the row's main
 * axis and the width token is 0. Flip the axis (round 20) and
 * flex-1 governs height instead, while the explicit width: 0
 * defeats the cross-axis stretch — the description and the
 * Responses section render at zero width, their text spilling
 * at min-content (the one-word-per-line columns in his shots).
 * The fix is one declaration in the same band: the row's
 * sl-w-0 child takes width: 100% when stacked.
 * ======================================================================== */
@media (max-width: 975px) {
  .chomp-docs-console .HttpOperation > .sl-flex > .sl-w-0 {
    width: 100%;
  }
}
