/* ===================================================================
   hostna OS — the indexable pages.

   /vps-hosting/, /shared-hosting/, the blog, contact, the legal set: every
   address that has to keep existing so the site can be found.

   These pages do not have a look of their own. They render the application's
   own chrome — .menubar, .stage, .win, .winbar, .lights, .scroll — so os.css
   dresses them exactly as it dresses the desktop, and a visitor arriving from
   a search result sees the same machine rather than a matching theme.

   That leaves this file one real job: os.css was written for an application
   that owns the viewport and never scrolls, and a document is taller than the
   screen and must. Everything below either undoes that assumption or styles
   the few components a page has and the desktop does not.
   =================================================================== */

/* ── 1. give the document its scrollbar back ────────────────────────
   os.css opens with `html,body{height:100%}` and `body{overflow:clip}` so the
   desktop can own the screen. On a document that is fatal: `clip` is not a
   scroll container at all, so everything past the first screenful becomes
   unreachable by scroll, by keyboard and by script — including, on the legal
   pages, the text someone came to read. */
html:has(body.hostna-os-page),
body.hostna-os-page {
  height: auto;
  min-height: 100%;
  overflow: visible;
}

/* overflow-x:CLIP, not hidden. `hidden` on either axis forces the other axis to
   compute to `auto`, which turns <body> into its own scroll container — and a
   scroll container that is height:auto never scrolls. Everything sticky inside
   it then resolves against that dead scrollport instead of the viewport, which
   is exactly why the menubar scrolled away and never came back. `clip` is the
   one value that pairs legally with `visible`, so the document keeps scrolling
   on the viewport and stray width still cannot produce a sideways scrollbar. */
body.hostna-os-page { overflow-x: clip; }

/* ── 2. the window grows with its content ───────────────────────────
   .stage is `position:absolute;inset:var(--bar-h) 0 0 0` in the app and .win
   is `height:100%;overflow:clip`. Both are right for one fixed screen and
   wrong for a page, so both return to normal flow. The menubar becomes sticky
   rather than absolute: it keeps its space, so there is no layout shift and no
   body padding to compensate with. */
/* Order matters here and got it wrong once: `inset` is the shorthand for all
   four offsets, so writing `inset:auto` AFTER `top:0` reset top back to auto,
   and a sticky box whose offsets are all auto behaves exactly like `relative`.
   The reset comes first now, the offset that does the work comes last. */
body.hostna-os-page .menubar {
  position: sticky;
  inset: auto;
  top: 0;
  z-index: 30;
}

/* RELATIVE, not static, and the z-index is load-bearing.
   os.css gives .stage `position:absolute; inset:var(--bar-h) 0 0 0; z-index:20`.
   Setting it to `static` returned it to flow but also made that z-index inert —
   z-index does nothing on a static box — and .win declares no position either,
   so nothing in the content's ancestry was a positioned box any more. The
   wallpaper .wall is `position:absolute; z-index:0` and a direct child of
   <body> (in the application it sits inside .desk), so it became the only
   positioned box over that content and painted on top of all of it: the h1,
   the lead, the hero art, the CTA and the whole document body were covered by
   an opaque gradient, unselectable, and every link under it unclickable.
   `relative` keeps the box in flow AND lets z-index apply. `inset:auto` must
   stay, because with `relative` the inherited inset would offset the box. */
body.hostna-os-page .stage {
  position: relative;
  inset: auto;
  z-index: 1;
  padding: 14px clamp(10px, 1.4vw, 18px) calc(var(--nav-h) + 26px);
}

/* The wallpaper stays where it belongs: behind everything, inert to the
   pointer so it can never swallow a click even if a stacking order changes,
   and FIXED rather than absolute.

   In the application .wall lives inside .desk, which is `position:fixed;
   overflow:clip` and contains it. A page has no .desk, so an absolute .wall at
   `inset:-10%` — with blobs deliberately hanging further past the edges — grew
   the document 188px wider than the viewport and produced a horizontal
   scrollbar on every page. Fixing it to the viewport removes it from the
   document's scroll extent entirely, and clipping it keeps the blobs inside;
   the content then scrolls over a stable backdrop, which is what the desktop
   does anyway. */
body.hostna-os-page .wall {
  position: fixed;
  inset: 0;
  overflow: clip;
  z-index: 0;
  pointer-events: none;
}

body.hostna-os-page .win,
body.hostna-os-page .os-win--doc {
  height: auto;
  min-height: calc(100dvh - var(--bar-h) - var(--nav-h) - 40px);
  overflow: visible;
  /* the app animates its window in; a document should not withhold its text
     until an animation has finished */
  animation: none;
}

/* The title bar keeps the blur; the window body does not. Blurring a
   page-length backdrop is a per-frame cost the desktop never paid, because its
   window was exactly one viewport tall. */
body.hostna-os-page .win {
  -webkit-backdrop-filter: none;
  backdrop-filter: none;
}
body.hostna-os-page .winbar {
  -webkit-backdrop-filter: blur(var(--blur)) saturate(170%);
  backdrop-filter: blur(var(--blur)) saturate(170%);
  border-radius: var(--r-win) var(--r-win) 0 0;
}

/* .scroll is the app's inner scroller. Here the document scrolls instead, so
   only its padding survives — keeping it would pin window.scrollY at 0 and
   strand the footer inside a box nobody can reach. */
body.hostna-os-page .scroll,
body.hostna-os-page .os-scroll--doc {
  height: auto;
  overflow: visible;
  overscroll-behavior: auto;
  padding: clamp(20px, 3vw, 40px) clamp(16px, 3vw, 44px) 30px;
}

/* ── 3. the hero band ───────────────────────────────────────────────
   Copy on the left, the family's 3D piece on the right — the shape the
   desktop opens with. These pages are the site's external links, so they have
   to be worth clicking: a search result that opens on a flat wall of text is a
   worse advertisement than one that opens on the machine being sold. */
body.hostna-os-page .os-hero {
  display: grid;
  grid-template-columns: minmax(0, 1.15fr) minmax(0, .85fr);
  align-items: center;
  gap: clamp(18px, 3vw, 44px);
  margin-bottom: clamp(20px, 3vw, 36px);
}
body.hostna-os-page .os-hero__copy h1 { margin: 8px 0 12px; }
body.hostna-os-page .os-hero__lead {
  font-size: 16px;
  line-height: 1.6;
  color: var(--ink-2);
  margin: 0 0 20px;
  max-width: 54ch;
}
body.hostna-os-page .os-hero__art {
  justify-self: center;
  width: 100%;
  max-width: 340px;
}
body.hostna-os-page .os-hero__art svg { width: 100%; height: auto; display: block; }

/* ── 4. the document card ───────────────────────────────────────────*/
body.hostna-os-page .os-doc {
  border-radius: var(--r-tile);
  padding: clamp(20px, 2.8vw, 34px);
  background: var(--sunk);
  border: 1px solid var(--stroke-2);
}

body.hostna-os-page .os-doc :where(ul, ol) {
  list-style: revert;
  padding-left: 1.4em;
  margin: 0 0 1em;
}
body.hostna-os-page .os-doc :where(h2) {
  font-size: clamp(20px, 2.1vw, 27px);
  line-height: 1.14;
  letter-spacing: -.026em;
  font-weight: 640;
  margin: 30px 0 12px;
}
body.hostna-os-page .os-doc :where(h2):first-child { margin-top: 0; }
body.hostna-os-page .os-doc :where(h3) {
  font-size: clamp(16px, 1.4vw, 19px);
  line-height: 1.25;
  font-weight: 620;
  margin: 22px 0 8px;
}
body.hostna-os-page .os-doc :where(p, li) {
  font-size: 14.5px;
  line-height: 1.62;
  color: var(--ink-2);
}
body.hostna-os-page .os-doc :where(p) { margin: 0 0 13px; }
body.hostna-os-page .os-doc :where(a) { color: var(--accent); text-underline-offset: 3px; }
body.hostna-os-page .os-doc :where(table) {
  width: 100%;
  border-collapse: collapse;
  margin: 16px 0;
  font-size: 13.5px;
}
body.hostna-os-page .os-doc :where(th, td) {
  padding: 9px 12px;
  border-bottom: 1px solid var(--stroke-2);
  text-align: left;
}
body.hostna-os-page .os-doc :where(img) { max-width: 100%; height: auto; border-radius: 14px; }
body.hostna-os-page .os-doc :where(pre) {
  overflow-x: auto;
  padding: 14px 16px;
  border-radius: 14px;
  background: var(--tile);
  border: 1px solid var(--stroke-2);
  font-size: 13px;
}

/* ── 5. the call to action ──────────────────────────────────────────
   The only route onward. Everything a visitor might want to do next —
   compare plans, configure a machine, order — happens in the application, so
   this points at the front page rather than at another document. */
body.hostna-os-page .os-cta {
  margin-top: 30px;
  padding: clamp(18px, 2.4vw, 28px);
  border-radius: var(--r-tile);
  background: var(--tile);
  border: 1px solid var(--stroke-2);
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 16px;
}
body.hostna-os-page .os-cta__copy { flex: 1 1 300px; min-width: 0; }
body.hostna-os-page .os-cta__copy h2 { margin: 0 0 6px; font-size: clamp(18px, 1.8vw, 23px); }
body.hostna-os-page .os-cta__copy p { margin: 0; font-size: 13.5px; color: var(--ink-3); }
body.hostna-os-page .os-cta__go {
  display: inline-flex;
  align-items: center;
  gap: 9px;
  height: 46px;
  padding: 0 22px;
  border-radius: 14px;
  background: linear-gradient(120deg, var(--btn), var(--btn-2));
  color: #fff;
  font-size: 15px;
  font-weight: 600;
  text-decoration: none;
  box-shadow: var(--shadow-pop);
  transition: transform .2s var(--ease), filter .2s;
}
body.hostna-os-page .os-cta__go:hover { transform: translateY(-2px); filter: brightness(1.06); }

/* ── 6. footer ──────────────────────────────────────────────────────
   The legal surface, which has to stay directly reachable from every page:
   § 5 DDG for the Impressum, § 312k BGB for the cancellation button. */
body.hostna-os-page .os-foot {
  margin-top: 26px;
  padding-top: 18px;
  border-top: 1px solid var(--stroke-2);
  font-size: 12.5px;
  color: var(--ink-3);
}
body.hostna-os-page .os-foot nav { display: flex; flex-wrap: wrap; gap: 8px 18px; }
body.hostna-os-page .os-foot a { color: var(--ink-3); text-decoration: none; }
body.hostna-os-page .os-foot a:hover { color: var(--ink); text-decoration: underline; }
body.hostna-os-page .os-foot__kuendigung { color: var(--ink-2); font-weight: 560; }
body.hostna-os-page .os-foot__nap { margin: 12px 0 0; }

/* ── 7. content components ──────────────────────────────────────────
   The pieces a service page is built from once its copy is read out of
   inc/catalog.php rather than out of post_content. */
body.hostna-os-page .os-lead {
  font-size: 16px;
  line-height: 1.55;
  color: var(--ink-2);
  margin: 0 0 20px;
}

body.hostna-os-page .os-stats {
  display: flex;
  flex-wrap: wrap;
  gap: 10px;
  list-style: none;
  padding: 0;
  margin: 0 0 24px;
}
body.hostna-os-page .os-stats li {
  display: flex;
  flex-direction: column;
  gap: 2px;
  padding: 10px 16px;
  border-radius: 14px;
  background: var(--tile);
  border: 1px solid var(--stroke-2);
}
body.hostna-os-page .os-stats b { font-size: 15px; color: var(--ink); }
body.hostna-os-page .os-stats span { font-size: 11.5px; color: var(--ink-3); }

body.hostna-os-page .os-cards {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(230px, 1fr));
  gap: 12px;
  list-style: none;
  padding: 0;
  margin: 0 0 8px;
}
body.hostna-os-page .os-cards li {
  padding: 16px 18px;
  border-radius: var(--r-tile);
  background: var(--tile);
  border: 1px solid var(--stroke-2);
}
body.hostna-os-page .os-cards b { display: block; margin-bottom: 5px; font-size: 14.5px; color: var(--ink); }
body.hostna-os-page .os-cards span { font-size: 13px; line-height: 1.5; color: var(--ink-3); }

body.hostna-os-page .os-plans th[scope="row"] { color: var(--ink); font-weight: 600; white-space: nowrap; }
body.hostna-os-page .os-plans thead th {
  font-size: 11px;
  text-transform: uppercase;
  letter-spacing: .1em;
  color: var(--ink-3);
  font-weight: 560;
}

body.hostna-os-page .os-faq {
  border-bottom: 1px solid var(--stroke-2);
  padding: 12px 0;
}
body.hostna-os-page .os-faq summary {
  cursor: pointer;
  font-size: 14.5px;
  font-weight: 560;
  color: var(--ink);
  list-style: none;
}
body.hostna-os-page .os-faq summary::-webkit-details-marker { display: none; }
body.hostna-os-page .os-faq summary::before {
  content: "+";
  display: inline-block;
  width: 1.1em;
  color: var(--ink-3);
}
body.hostna-os-page .os-faq[open] summary::before { content: "\2212"; }
body.hostna-os-page .os-faq p { margin: 8px 0 0 1.1em; font-size: 13.5px; }

/* A legal note is the paragraph a reader must not skim past. */
body.hostna-os-page .os-note {
  padding: 12px 15px;
  border-radius: 14px;
  background: var(--tile);
  border: 1px solid var(--stroke-2);
  border-left: 3px solid var(--accent);
}

body.hostna-os-page .os-doc :where(dl) { margin: 0 0 16px; }
body.hostna-os-page .os-doc :where(dt) { font-weight: 600; color: var(--ink); margin-top: 12px; }
body.hostna-os-page .os-doc :where(dd) { margin: 4px 0 0; color: var(--ink-2); font-size: 14.5px; line-height: 1.6; }

/* ── 8. the page dock ───────────────────────────────────────────────
   The application's dock, rebuilt as anchors. Same glass pill, same 40px
   targets, same lift on hover — the point is that it reads as the same piece
   of furniture, so moving from a search result into the desktop does not feel
   like leaving a site. */
body.hostna-os-page .os-pagedock {
  position: fixed;
  left: 50%;
  bottom: 12px;
  transform: translateX(-50%);
  z-index: 40;
  max-width: calc(100% - 20px);
  padding: 7px 9px;
  border-radius: 22px;
  background: linear-gradient(160deg, var(--glass-a), var(--glass-b));
  -webkit-backdrop-filter: blur(var(--blur)) saturate(180%);
  backdrop-filter: blur(var(--blur)) saturate(180%);
  border: 1px solid var(--stroke);
  box-shadow: var(--shadow-pop);
}

body.hostna-os-page .os-pagedock ul {
  display: flex;
  align-items: center;
  gap: 6px;
  margin: 0;
  padding: 0;
  list-style: none;
  overflow-x: auto;
  scrollbar-width: none;
}
body.hostna-os-page .os-pagedock ul::-webkit-scrollbar { display: none; }

body.hostna-os-page .os-pagedock__btn {
  position: relative;
  flex: 0 0 auto;
  display: grid;
  place-items: center;
  width: 40px;
  height: 40px;
  border-radius: 13px;
  color: var(--ink-2);
  text-decoration: none;
  transition: background .2s, color .2s, transform .2s var(--ease);
}
body.hostna-os-page .os-pagedock__btn svg {
  width: 18px;
  height: 18px;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.65;
  stroke-linecap: round;
  stroke-linejoin: round;
}
body.hostna-os-page .os-pagedock__btn:hover {
  background: var(--tile-2);
  color: var(--ink);
  transform: translateY(-3px);
}

body.hostna-os-page .os-pagedock__btn[data-os-label]::before {
  content: attr(data-os-label);
  position: absolute;
  left: 50%;
  top: -36px;
  transform: translateX(-50%) translateY(6px);
  padding: 5px 10px;
  border-radius: 9px;
  font-size: 11.5px;
  white-space: nowrap;
  color: var(--ink);
  background: linear-gradient(160deg, var(--glass-a), var(--glass-b));
  -webkit-backdrop-filter: blur(10px);
  backdrop-filter: blur(10px);
  border: 1px solid var(--stroke);
  box-shadow: var(--shadow-pop);
  opacity: 0;
  pointer-events: none;
  transition: opacity .2s var(--ease), transform .2s var(--ease);
}
body.hostna-os-page .os-pagedock__btn:hover::before,
body.hostna-os-page .os-pagedock__btn:focus-visible::before {
  opacity: 1;
  transform: translateX(-50%) translateY(0);
}

/* ── 8b. the document's own scrollbar ───────────────────────────────
   os-chrome.css takes the scrollbar off everything inside the window. On this
   surface the window does not scroll — the DOCUMENT does (see section 1), so
   the bar that is left belongs to the viewport, and a viewport scrollbar is
   taken from <html>. No rule scoped to <body> can reach it, which is why this
   one is here and written through :has(): it is the only way to say "the html
   element of a page that is one of ours" without a class the PHP would have to
   print. Same trade as os-chrome.css: the indicator goes, the scrolling does
   not. */
html:has(> body.hostna-os-page) {
  scrollbar-width: none;
  -ms-overflow-style: none;
}
html:has(> body.hostna-os-page)::-webkit-scrollbar {
  width: 0;
  height: 0;
  display: none;
}

/* ── 9. responsive ──────────────────────────────────────────────────*/
@media (max-width: 860px) {
  body.hostna-os-page .os-hero { grid-template-columns: 1fr; }
  body.hostna-os-page .os-hero__art { max-width: 240px; order: -1; }
}
@media (max-width: 700px) {
  /* The same window box the application draws — the tokens are declared in
     os-chrome.css, which both surfaces load. This restates the rule rather than
     leaving it to be inherited because os-page.css is enqueued last and its own
     `body.hostna-os-page .stage` would otherwise win the tie with a stale
     literal in it. Same specificity, same value: the tie no longer matters. */
  body.hostna-os-page .stage {
    padding: var(--os-gap) var(--os-gap) var(--os-edge);
  }
  body.hostna-os-page .scroll:not(.flat),
  body.hostna-os-page .os-scroll--doc { padding-inline: var(--os-pad); }
  body.hostna-os-page .wt-act { display: none; }
  body.hostna-os-page .os-cta__go { width: 100%; justify-content: center; }
  body.hostna-os-page .os-pagedock {
    bottom: var(--os-dock-b);
    padding: 6px;
    border-radius: 18px;
    /* the same side margin as the window — see --os-gap in os-chrome.css */
    max-width: calc(100% - (var(--os-gap) * 2));
  }

  /* The window's floor, which had gone stale on three terms at once: it
     subtracted --bar-h for a menubar that os-chrome.css hides on this
     breakpoint, and a trailing 40px that was the old `14 + 26` stage padding.
     The real reservation is --os-gap on top and --os-edge underneath, so the
     floor was 70-116px shorter than the box it is a floor for. A min-height is
     silent until a short document lands on it, which is the only reason this
     was not visible.

     --os-edge, not the `--nav-h + 2` literal it used to spell out, and the
     literal is the reason this line is being touched at all: the phone's
     --os-dock-b now carries env(safe-area-inset-bottom), so on a handset with
     a home indicator the dock lifts by the inset and a floor written as a
     constant would have let the bar climb back over the last of the text. The
     stage above reads the same token for the same reason. */
  body.hostna-os-page .win,
  body.hostna-os-page .os-win--doc {
    min-height: calc(100dvh - var(--os-gap) - var(--os-edge));
  }
  body.hostna-os-page .os-pagedock__btn { width: 38px; height: 38px; }
  /* a tooltip is a pointer affordance; on touch it only gets in the way */
  body.hostna-os-page .os-pagedock__btn[data-os-label]::before { display: none; }
}

/* ── 10. enquiry forms ──────────────────────────────────────────────
   inc/forms.php emits the markup the previous storefront used
   (.enquiry-section > .site-shell.enquiry-grid, .enquiry-field, .button), and
   hostna-v6.css — which styled all of it — is dequeued on these pages. Left
   alone the forms render as raw browser defaults on the two pages where that
   matters most: /kuendigung/ is the § 312k BGB cancellation route and
   /report-abuse/ is the DSA Art. 16 notice-and-action channel, and a
   statutory control that looks broken is barely better than one that is
   missing. So the old class names are dressed in OS clothes rather than
   rewritten — the markup stays one source, in inc/forms.php. */
body.hostna-os-page .enquiry-section {
  margin-top: 30px;
  padding: 0;
}
/* The form's outer element carries BOTH classes: <div class="site-shell
   enquiry-grid">. So this reset must not set padding — at (0,3,1) it outranks
   a plain `.enquiry-grid` rule (0,2,1) and would flatten the card to nothing,
   which is exactly what it did on first deploy. Width and margin only; the
   grid rule below owns the padding and is scoped to match. */
body.hostna-os-page .enquiry-section .site-shell {
  width: auto;
  max-width: none;
  margin: 0;
}
body.hostna-os-page .enquiry-section .enquiry-grid {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 20px;
  padding: clamp(20px, 2.8vw, 32px);
  border-radius: var(--r-tile);
  background: var(--tile);
  border: 1px solid var(--stroke-2);
}
@media (min-width: 900px) {
  body.hostna-os-page .enquiry-section .enquiry-grid { grid-template-columns: minmax(0, .85fr) minmax(0, 1.15fr); gap: 32px; }
}

body.hostna-os-page .enquiry-intro h2 { margin: 6px 0 8px; font-size: clamp(19px, 1.9vw, 24px); }
body.hostna-os-page .enquiry-intro p { font-size: 13.5px; color: var(--ink-3); margin: 0 0 14px; }
body.hostna-os-page .plain-checks { list-style: none; padding: 0; margin: 0; display: grid; gap: 7px; }
body.hostna-os-page .plain-checks li {
  position: relative;
  padding-left: 22px;
  font-size: 12.5px;
  color: var(--ink-3);
}
body.hostna-os-page .plain-checks li::before {
  content: "";
  position: absolute;
  left: 0;
  top: .42em;
  width: 12px;
  height: 6px;
  border-left: 1.8px solid var(--ok);
  border-bottom: 1.8px solid var(--ok);
  transform: rotate(-45deg);
}

body.hostna-os-page .enquiry-form { display: grid; gap: 13px; }
body.hostna-os-page .enquiry-field { display: grid; gap: 5px; }
body.hostna-os-page .enquiry-field > span,
body.hostna-os-page .enquiry-field > label > span {
  font-size: 11.5px;
  letter-spacing: .04em;
  color: var(--ink-3);
}
body.hostna-os-page .enquiry-field :where(input, select, textarea) {
  width: 100%;
  min-height: 44px;
  padding: 11px 13px;
  border-radius: var(--r-ctl);
  background: var(--sunk);
  border: 1px solid var(--stroke-2);
  color: var(--ink);
  font: inherit;
  font-size: 14px;
  transition: border-color .18s, background .18s;
}
body.hostna-os-page .enquiry-field :where(textarea) { min-height: 132px; resize: vertical; line-height: 1.55; }
/* The dropdown popup is painted by the OS, not by the page, so it does not
   inherit the field's colours. os.css already sets these explicitly for its own
   selects; the enquiry forms need the same or night mode renders near-white
   option text on a light system sheet — invisible except for the highlighted
   row. Affects the DSA abuse-type select and the cancellation reason. */
body.hostna-os-page .enquiry-field select option {
  background: #12161f;
  color: #eef2f8;
}
[data-theme="light"] body.hostna-os-page .enquiry-field select option {
  background: #ffffff;
  color: #15181f;
}
/* The outline stays. os.css:21 strips outlines from every control and restores
   them with a global `:focus-visible` rule at (0,1,0); this selector is (0,3,1)
   and outranked it, replacing a real focus ring with a border tint that a
   native checkbox does not paint at all. On /report-abuse/ that left the
   required Art. 16 (2)(d) good-faith declaration with no visible focus state
   for a keyboard user, and on /kuendigung/ the same for the cancellation
   consent. The tint is kept as an extra, not as a replacement. */
body.hostna-os-page .enquiry-field :where(input, select, textarea):focus-visible,
body.hostna-os-page .enquiry-check input[type="checkbox"]:focus-visible {
  outline: 2px solid var(--accent);
  outline-offset: 2px;
  border-color: color-mix(in srgb, var(--accent) 55%, var(--stroke));
  background: var(--tile);
}

/* The consent and confirmation checkboxes. On /kuendigung/ one of these is the
   statement that carries the cancellation, so it has to be unmistakably a
   control and unmistakably readable. */
/* Only .enquiry-check gets the card. Two corrections from a review:
   .enquiry-field--checkbox is its PARENT (inc/forms.php nests
   <div class="enquiry-field enquiry-field--checkbox"><label class="enquiry-check">),
   so boxing both drew two concentric rounded rectangles around every checkbox;
   and .enquiry-consent is not a checkbox row at all but a <p> of prose with an
   inline link, so `display:flex` turned its three child runs — text, the
   privacy-policy anchor, the closing full stop — into three side-by-side
   columns with a stray period floating at the far right. */
body.hostna-os-page .enquiry-check {
  display: flex;
  align-items: flex-start;
  gap: 10px;
  padding: 12px 14px;
  border-radius: var(--r-ctl);
  background: var(--sunk);
  border: 1px solid var(--stroke-2);
  font-size: 12.5px;
  line-height: 1.5;
  color: var(--ink-2);
}

body.hostna-os-page .enquiry-consent {
  margin: 0;
  font-size: 12.5px;
  line-height: 1.55;
  color: var(--ink-3);
}
body.hostna-os-page .enquiry-consent a { color: var(--accent); }
body.hostna-os-page .enquiry-check input[type="checkbox"] {
  width: 18px;
  height: 18px;
  min-height: 0;
  margin: 1px 0 0;
  flex: 0 0 auto;
  accent-color: var(--accent);
}

/* The honeypot is not for people to see. */
body.hostna-os-page .enquiry-hp { position: absolute; left: -9999px; width: 1px; height: 1px; overflow: hidden; }

body.hostna-os-page .enquiry-form .button,
body.hostna-os-page .enquiry-form button[type="submit"] {
  justify-self: start;
  display: inline-flex;
  align-items: center;
  gap: 9px;
  height: 46px;
  padding: 0 24px;
  border: 0;
  border-radius: 14px;
  background: linear-gradient(120deg, var(--btn), var(--btn-2));
  color: #fff;
  font-size: 15px;
  font-weight: 600;
  cursor: pointer;
  box-shadow: var(--shadow-pop);
  transition: transform .2s var(--ease), filter .2s;
}
body.hostna-os-page .enquiry-form .button:hover,
body.hostna-os-page .enquiry-form button[type="submit"]:hover { transform: translateY(-2px); filter: brightness(1.06); }

body.hostna-os-page .enquiry-status,
body.hostna-os-page .enquiry-error {
  font-size: 13px;
  padding: 10px 13px;
  border-radius: var(--r-ctl);
  background: var(--sunk);
  border: 1px solid var(--stroke-2);
}
/* The status box lives in the DOM from first paint and is empty until a submit
   resolves. Without this it renders as a permanent empty bordered capsule under
   every button — under the statutory one on /kuendigung/, where it reads as
   something that failed to load. hostna-v6.css had this rule; it was not
   carried over with the rest. */
body.hostna-os-page .enquiry-status:empty,
body.hostna-os-page .enquiry-error:empty { display: none; }

body.hostna-os-page .enquiry-status.is-success { border-left: 3px solid var(--ok); color: var(--ink); }
body.hostna-os-page .enquiry-status.is-error,
body.hostna-os-page .enquiry-error { border-left: 3px solid var(--bad, #c8324f); color: var(--ink); }

@media (max-width: 700px) {
  body.hostna-os-page .enquiry-form .button,
  body.hostna-os-page .enquiry-form button[type="submit"] { width: 100%; justify-content: center; }
}

/* ── 11. no reflow by window height ─────────────────────────────────
   os.css carries eight `@media (max-height: …)` blocks. They are right for the
   application, whose whole job is to fit one screen exactly, and wrong for a
   document, which is meant to be longer than the screen — a page that
   rearranges itself because the browser window is short is a surprise with no
   explanation the reader can see, and this theme has never done it.

   Of the classes those blocks touch (.bento, .tile, .t-hero, .hero-copy,
   .hero-art, .hero-cta, .lad*, .xcard, .dom-card, .plan-grid, .rig-*), the
   only one a page actually renders is .eyebrow, which drops from 10px to 6px
   of margin below 820px of viewport height. Pinning it is the whole fix; the
   rest cannot match here. Written flat rather than inside a media query so it
   wins in every viewport. */
body.hostna-os-page .eyebrow { margin-bottom: 10px; }

/* ── the pages next to this one ──────────────────────────────────────────
   The same tile as .os-cards, made clickable. Deliberately the same shape
   rather than a louder one: these are lateral moves between product pages,
   not the call to action — the window bar and the closing card already carry
   that, and a rail that competed with them would sell the visitor a sideways
   step at the moment they were ready to buy.

   os-nav.js turns every one of these into an in-window swap, which is the
   other half of why they can be quiet: there is no page load to brace for. */
body.hostna-os-page .os-siblings {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(230px, 1fr));
  gap: 12px;
  list-style: none;
  padding: 0;
  margin: 0 0 8px;
}
body.hostna-os-page .os-siblings a {
  display: block;
  height: 100%;
  padding: 16px 18px;
  border-radius: var(--r-tile);
  background: var(--tile);
  border: 1px solid var(--stroke-2);
  text-decoration: none;
  transition: background .2s, border-color .2s, transform .2s var(--ease);
}
body.hostna-os-page .os-siblings a:hover,
body.hostna-os-page .os-siblings a:focus-visible {
  background: var(--tile-2, var(--tile));
  border-color: var(--stroke);
  transform: translateY(-2px);
}
body.hostna-os-page .os-siblings b { display: block; margin-bottom: 5px; font-size: 14.5px; color: var(--ink); }
body.hostna-os-page .os-siblings span { display: block; font-size: 13px; line-height: 1.5; color: var(--ink-3); }

@media (prefers-reduced-motion: reduce) {
  body.hostna-os-page .os-siblings a { transition: none; }
  body.hostna-os-page .os-siblings a:hover,
  body.hostna-os-page .os-siblings a:focus-visible { transform: none; }
}

/* A wide table scrolls inside its own box instead of widening the document.
   The free-hosting comparison has eight columns and the limits table three
   with a sentence in the last; on a 360px phone either would otherwise push
   the layout viewport out and drag every position:fixed layer with it — the
   9.7.0 halo bug, in table form. (9.19.0) */
body.hostna-os-page .os-doc .os-tablewrap {
  overflow-x: auto;
  -webkit-overflow-scrolling: touch;
  margin: 16px 0;
  border: 1px solid var(--stroke-2);
  border-radius: 14px;
}
body.hostna-os-page .os-doc .os-tablewrap table { margin: 0; }
body.hostna-os-page .os-doc .os-tablewrap--wide table { min-width: 620px; }
body.hostna-os-page .os-doc .os-tablewrap th[scope="row"] { font-weight: 640; color: var(--ink); white-space: nowrap; }
body.hostna-os-page .os-doc .os-tablewrap thead th { font-size: 12px; letter-spacing: .04em; text-transform: uppercase; color: var(--ink-3); background: var(--tile); }
body.hostna-os-page .os-doc .os-tablewrap tbody tr:last-child :where(th, td) { border-bottom: 0; }

/* The English/German switch on a legal document. Shown only where a German
   version exists — the Terms tell the reader to choose it "above", so it has
   to be above, and it has to be real. */
.os-langswitch{
  display:flex;flex-wrap:wrap;gap:8px;align-items:center;
  margin:0 0 14px;font-size:12.5px;
}
.os-langswitch a,.os-langswitch span{
  padding:3px 9px;border-radius:999px;border:1px solid var(--stroke);
}
.os-langswitch span{background:var(--tile-2);color:var(--ink)}
.os-langswitch a{color:var(--ink-2);text-decoration:none}
.os-langswitch a:hover{color:var(--ink);border-color:var(--accent)}

/* ═══════════════════════════════════════════════════════════════════════
   SERVICE PAGES — the surface that has to sell
   ═══════════════════════════════════════════════════════════════════════
   These 25 addresses are the company's whole search presence, and until now
   they were documents: a stat list, six flat cards and a three-column TABLE
   of plans with no price emphasis and nothing to press. The layout below is
   the same OS material as the desktop — the tile, the stroke, the one action
   colour — arranged so that a visitor who arrived from a search result can
   see the price, the plan and the way in without scrolling.

   Everything is scoped to body.hostna-os-page like the rest of this file, and
   built from os.css tokens only, so a theme change carries it along.
   ═══════════════════════════════════════════════════════════════════════ */

/* ── the offer ──────────────────────────────────────────────────────────
   First block under the hero. Price, one primary action, and the family's
   own selling points. */
body.hostna-os-page .sv-offer {
  display: grid;
  gap: 14px;
  margin: 0 0 clamp(18px, 2.6vw, 28px);
  padding: clamp(16px, 2.2vw, 24px);
  border-radius: var(--r-tile);
  border: 1px solid var(--stroke);
  background:
    radial-gradient(120% 140% at 100% 0%, color-mix(in srgb, var(--accent) 12%, transparent), transparent 62%),
    var(--tile);
  box-shadow: inset 0 1px 0 var(--spec);
}

body.hostna-os-page .sv-offer__price {
  display: flex;
  align-items: baseline;
  flex-wrap: wrap;
  gap: 6px;
  margin: 0;
}
body.hostna-os-page .sv-offer__price span {
  font-size: 13px;
  letter-spacing: .08em;
  text-transform: uppercase;
  color: var(--ink-3);
}
body.hostna-os-page .sv-offer__price b {
  font-size: clamp(32px, 5vw, 44px);
  font-weight: 620;
  line-height: 1;
  letter-spacing: -.03em;
  color: var(--ink);
}
body.hostna-os-page .sv-offer__price i {
  font-style: normal;
  font-size: 15px;
  color: var(--ink-2);
}

/* Not fine print. § 19 (1) UStG means the published number IS the final
   number, and the PAngV wants that said rather than implied. */
body.hostna-os-page .sv-offer__vat {
  margin: 0;
  font-size: 12.5px;
  line-height: 1.5;
  color: var(--ink-3);
}

body.hostna-os-page .sv-offer__acts {
  display: flex;
  flex-wrap: wrap;
  gap: 10px;
}
body.hostna-os-page .sv-offer__acts .prime-btn,
body.hostna-os-page .sv-offer__acts .ghost-btn {
  height: 42px;
  padding: 0 20px;
  font-size: 14px;
}

/* THE BUTTONS INSIDE .os-doc NEED THEIR COLOUR BACK, and this is the trap
   CLAUDE.md warns about rather than a new one. `body.hostna-os-page .os-doc
   :where(a)` is (0,2,1): :where() zeroes the `a`, NOT the two classes in front
   of it, so it beats .prime-btn and .ghost-btn at (0,1,0) and repaints every
   button label in accent blue. White-on-purple became blue-on-purple on the
   featured plan — the single most important control on the page, and the one
   with the worst contrast of anything we would have shipped. */
body.hostna-os-page .os-doc a.prime-btn { color: #fff; text-decoration: none; }
body.hostna-os-page .os-doc a.ghost-btn { color: var(--ink); text-decoration: none; }
body.hostna-os-page .os-doc a.prime-btn:hover,
body.hostna-os-page .os-doc a.ghost-btn:hover { text-decoration: none; }

/* ── check lists ────────────────────────────────────────────────────────
   One rule for every tick on the page: the hero points, the plan features,
   the argument bullets and the includes grid. The icon is sized and coloured
   here so no caller has to pass arguments. */
body.hostna-os-page .sv-checks {
  display: grid;
  gap: 8px;
  margin: 0;
  padding: 0;
  list-style: none;
}
body.hostna-os-page .sv-checks li {
  display: grid;
  grid-template-columns: 18px 1fr;
  align-items: start;
  gap: 9px;
  margin: 0;
  font-size: 13.5px;
  line-height: 1.5;
  color: var(--ink-2);
}
body.hostna-os-page .sv-checks svg {
  width: 18px;
  height: 18px;
  margin-top: 1px;
  fill: none;
  stroke: var(--ok);
  stroke-width: 2.1;
  stroke-linecap: round;
  stroke-linejoin: round;
}
body.hostna-os-page .sv-checks--inline {
  grid-template-columns: repeat(auto-fit, minmax(190px, 1fr));
  gap: 8px 18px;
}

/* ── the trust strip ────────────────────────────────────────────────────
   Three facts, wide and quiet. It sits between the offer and the plans
   because that is where the "is this real" question is asked. */
body.hostna-os-page .sv-trust {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(160px, 1fr));
  gap: 10px;
  margin: 0 0 clamp(22px, 3vw, 34px);
  padding: 0;
  list-style: none;
}
body.hostna-os-page .sv-trust li {
  display: grid;
  grid-template-columns: 34px 1fr;
  grid-template-rows: auto auto;
  align-items: center;
  gap: 0 11px;
  margin: 0;
  padding: 12px 14px;
  border-radius: 15px;
  border: 1px solid var(--stroke-2);
  background: var(--tile-2);
}
body.hostna-os-page .sv-trust svg {
  grid-row: 1 / 3;
  width: 34px;
  height: 34px;
  padding: 8px;
  border-radius: 11px;
  box-sizing: border-box;
  fill: none;
  stroke: var(--accent);
  stroke-width: 1.7;
  stroke-linecap: round;
  stroke-linejoin: round;
  background: color-mix(in srgb, var(--accent) 13%, transparent);
}
body.hostna-os-page .sv-trust b { font-size: 14px; color: var(--ink); }
body.hostna-os-page .sv-trust span { font-size: 12.5px; color: var(--ink-3); }

/* ── section rhythm ─────────────────────────────────────────────────────
   One spacing scale for the whole page so the eight blocks read as one
   document rather than eight pasted ones. */
body.hostna-os-page .sv-sec {
  margin: 0 0 clamp(30px, 4.5vw, 52px);
  scroll-margin-top: 76px;
}
body.hostna-os-page .sv-head { margin: 0 0 clamp(14px, 2vw, 22px); }
body.hostna-os-page .sv-head h2 {
  margin: 0 0 8px;
  font-size: clamp(21px, 2.8vw, 27px);
  letter-spacing: -.02em;
  color: var(--ink);
}
body.hostna-os-page .sv-head p {
  margin: 0;
  max-width: 62ch;
  font-size: 14px;
  line-height: 1.6;
  color: var(--ink-3);
}

/* ── the plans ──────────────────────────────────────────────────────────
   The block this page exists for. Cards, not table rows: a price a buyer can
   find, the features that justify it, and a button that opens THAT plan in
   the desktop's configurator. */
body.hostna-os-page .sv-plans {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(248px, 1fr));
  gap: 14px;
  align-items: start;
}
body.hostna-os-page .sv-plan {
  position: relative;
  display: flex;
  flex-direction: column;
  gap: 10px;
  padding: 18px 17px 17px;
  border-radius: var(--r-tile);
  border: 1px solid var(--stroke-2);
  background: var(--tile);
  box-shadow: inset 0 1px 0 var(--spec);
  transition: transform .2s var(--ease), border-color .2s, box-shadow .25s;
}
body.hostna-os-page .sv-plan:hover {
  transform: translateY(-3px);
  border-color: color-mix(in srgb, var(--accent) 42%, var(--stroke));
  box-shadow: 0 18px 34px -22px rgba(5, 10, 25, .5), inset 0 1px 0 var(--spec);
}

/* The featured plan is the one the top button opens, so it has to be
   findable in the grid without reading every card. */
body.hostna-os-page .sv-plan.is-featured {
  border-color: color-mix(in srgb, var(--btn) 46%, var(--stroke));
  background:
    radial-gradient(120% 120% at 50% 0%, color-mix(in srgb, var(--btn) 11%, transparent), transparent 60%),
    var(--tile);
}
body.hostna-os-page .sv-plan__flag {
  position: absolute;
  top: -9px;
  left: 17px;
  padding: 3px 10px;
  border-radius: 999px;
  font-size: 10.5px;
  font-weight: 600;
  letter-spacing: .08em;
  text-transform: uppercase;
  color: #fff;
  background: linear-gradient(180deg, var(--btn-2), var(--btn));
  box-shadow: 0 6px 14px -8px var(--btn);
}

body.hostna-os-page .sv-plan h3 {
  margin: 0;
  font-size: 16.5px;
  letter-spacing: -.01em;
  color: var(--ink);
}
body.hostna-os-page .sv-plan__desc {
  margin: 0;
  font-size: 13px;
  line-height: 1.5;
  color: var(--ink-3);
}
body.hostna-os-page .sv-plan__price {
  display: flex;
  align-items: baseline;
  gap: 4px;
  margin: 2px 0 0;
}
body.hostna-os-page .sv-plan__price b {
  font-size: 27px;
  font-weight: 620;
  line-height: 1;
  letter-spacing: -.025em;
  color: var(--ink);
}
body.hostna-os-page .sv-plan__price i {
  font-style: normal;
  font-size: 13px;
  color: var(--ink-3);
}
/* The renewal price is a § 312a/PAngV transparency point, not decoration:
   the buyer is told before the click what the second invoice says. */
body.hostna-os-page .sv-plan__renew {
  margin: 0;
  font-size: 12px;
  color: var(--ink-3);
}
body.hostna-os-page .sv-plan .sv-checks { margin-top: 2px; }
body.hostna-os-page .sv-plan .sv-checks li { font-size: 12.5px; }

/* Pushed to the bottom so buttons line up across cards of unequal height. */
body.hostna-os-page .sv-plan__go {
  margin-top: auto;
  align-self: stretch;
  height: 40px;
  text-decoration: none;
}

body.hostna-os-page .sv-note {
  margin: 14px 0 0;
  font-size: 12.5px;
  line-height: 1.55;
  color: var(--ink-3);
}

/* ── the argument beside a 3D piece ─────────────────────────────────────
   The same objects the desktop uses, so the page and the machine are
   recognisably one product. */
body.hostna-os-page .sv-split {
  display: grid;
  grid-template-columns: minmax(0, 1.05fr) minmax(0, .95fr);
  align-items: center;
  gap: clamp(20px, 3.4vw, 46px);
}
body.hostna-os-page .sv-split--flip .sv-split__art { order: 2; }
body.hostna-os-page .sv-split--flip .sv-split__copy { order: 1; }
body.hostna-os-page .sv-split__copy h2 {
  margin: 0 0 10px;
  font-size: clamp(20px, 2.6vw, 26px);
  letter-spacing: -.02em;
  color: var(--ink);
}
body.hostna-os-page .sv-split__copy p {
  margin: 0 0 14px;
  font-size: 14px;
  line-height: 1.65;
  color: var(--ink-2);
}
body.hostna-os-page .sv-split__art { display: grid; place-items: center; }
body.hostna-os-page .sv-split__art svg {
  width: 100%;
  max-width: 340px;
  height: auto;
}

/* ── how it works ───────────────────────────────────────────────────────
   Three steps, numbered. The counter is a real element rather than a CSS
   counter so it can carry the badge styling. */
body.hostna-os-page .sv-steps {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(230px, 1fr));
  gap: 14px;
  margin: 0;
  padding: 0;
  list-style: none;
  counter-reset: none;
}
body.hostna-os-page .sv-steps li {
  margin: 0;
  padding: 18px 17px;
  border-radius: var(--r-tile);
  border: 1px solid var(--stroke-2);
  background: var(--tile-2);
}
body.hostna-os-page .sv-steps b {
  display: grid;
  place-items: center;
  width: 30px;
  height: 30px;
  margin-bottom: 11px;
  border-radius: 10px;
  font-size: 13.5px;
  font-weight: 600;
  color: #fff;
  background: linear-gradient(180deg, var(--btn-2), var(--btn));
}
body.hostna-os-page .sv-steps h3 {
  margin: 0 0 6px;
  font-size: 15px;
  color: var(--ink);
}
body.hostna-os-page .sv-steps p {
  margin: 0;
  font-size: 13px;
  line-height: 1.55;
  color: var(--ink-3);
}

/* ── included as standard ───────────────────────────────────────────── */
body.hostna-os-page .sv-includes {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(210px, 1fr));
  gap: 10px 20px;
  margin: 0;
  padding: 16px 18px;
  border-radius: var(--r-tile);
  border: 1px solid var(--stroke-2);
  background: var(--tile-2);
  list-style: none;
}
body.hostna-os-page .sv-includes li {
  display: grid;
  grid-template-columns: 18px 1fr;
  align-items: start;
  gap: 9px;
  margin: 0;
  font-size: 13.5px;
  line-height: 1.5;
  color: var(--ink-2);
}
body.hostna-os-page .sv-includes svg {
  width: 18px;
  height: 18px;
  margin-top: 1px;
  fill: none;
  stroke: var(--ok);
  stroke-width: 2.1;
  stroke-linecap: round;
  stroke-linejoin: round;
}

/* ── why this family ────────────────────────────────────────────────── */
body.hostna-os-page .sv-benefits {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(230px, 1fr));
  gap: 12px;
  margin: 0;
  padding: 0;
  list-style: none;
}
body.hostna-os-page .sv-benefits li {
  margin: 0;
  padding: 16px 16px 17px;
  border-radius: 17px;
  border: 1px solid var(--stroke-2);
  background: var(--tile);
}
body.hostna-os-page .sv-benefits b {
  display: block;
  margin-bottom: 6px;
  font-size: 14.5px;
  color: var(--ink);
}
body.hostna-os-page .sv-benefits span {
  font-size: 13px;
  line-height: 1.55;
  color: var(--ink-3);
}

/* ── the client area block ──────────────────────────────────────────── */
body.hostna-os-page .sv-control {
  padding: clamp(16px, 2.2vw, 24px);
  border-radius: var(--r-tile);
  border: 1px solid var(--stroke-2);
  background: var(--sunk);
}
body.hostna-os-page .sv-control h2 {
  margin: 0 0 8px;
  font-size: clamp(19px, 2.4vw, 24px);
  letter-spacing: -.02em;
  color: var(--ink);
}
body.hostna-os-page .sv-control p {
  margin: 0 0 14px;
  max-width: 68ch;
  font-size: 14px;
  line-height: 1.65;
  color: var(--ink-2);
}

/* ── narrow ─────────────────────────────────────────────────────────────
   The split stacks copy-first in BOTH directions: on a phone the argument
   has to arrive before the illustration, and --flip's order values would
   otherwise put a 340px drawing above the sentence explaining it. */
@media (max-width: 760px) {
  body.hostna-os-page .sv-split { grid-template-columns: 1fr; }
  body.hostna-os-page .sv-split--flip .sv-split__art,
  body.hostna-os-page .sv-split__art { order: 2; }
  body.hostna-os-page .sv-split--flip .sv-split__copy,
  body.hostna-os-page .sv-split__copy { order: 1; }
  body.hostna-os-page .sv-split__art svg { max-width: 240px; }
  body.hostna-os-page .sv-offer__acts .prime-btn,
  body.hostna-os-page .sv-offer__acts .ghost-btn { flex: 1 1 100%; }
}

@media (prefers-reduced-motion: reduce) {
  body.hostna-os-page .sv-plan { transition: none; }
  body.hostna-os-page .sv-plan:hover { transform: none; }
}

/* ═════════════════════════════════════════════════════════════════════
   FULL-BLEED DOCUMENT SURFACE (8.64) — owner's revision, 2026-09-02.

   The outer pages no longer render as a rounded window floating on the
   wallpaper: the frame gaps in the corners and the gradient showing
   through the glass read as "a window on a page", and the owner wants
   "a computer screen" — the document IS the display, edge to edge,
   opaque, exactly like a panel screen. The menubar and the title bar
   stay (they are the machine); the wallpaper and the float go.

   Kept at the very end of this file on purpose: several rules below
   re-declare properties at the same specificity as §1 above, and the
   tie is decided by source order.
   ═════════════════════════════════════════════════════════════════════ */
body.hostna-os-page {
  background: var(--bg-base);
}
/* the wallpaper never shows on a document — stop paying for its blobs too */
body.hostna-os-page .wall {
  display: none;
}
body.hostna-os-page .stage {
  padding: 0;
}
body.hostna-os-page .win,
body.hostna-os-page .os-win--doc {
  border-radius: 0;
  border: 0;
  box-shadow: none;
  /* opaque: the surface is the screen, not a glass over scenery */
  background: var(--bg-base);
  min-height: calc(100dvh - var(--bar-h));
}
body.hostna-os-page .win::before {
  border-radius: 0;
  box-shadow: inset 0 1px 0 var(--spec);
}
body.hostna-os-page .winbar {
  border-radius: 0;
  /* nothing behind it to blur any more */
  -webkit-backdrop-filter: none;
  backdrop-filter: none;
  background: var(--tile-2);
}
body.hostna-os-page .menubar {
  -webkit-backdrop-filter: none;
  backdrop-filter: none;
  background: var(--bg-base);
}
/* the stage no longer reserves a floor for the dock, so the scroller does —
   without this the floating dock sits on the last lines of every page */
body.hostna-os-page .scroll,
body.hostna-os-page .os-scroll--doc {
  padding-bottom: calc(30px + var(--os-edge, 72px));
}

/* ═════════════════════════════════════════════════════════════════════
   THE APP'S SCROLL LAW (8.65) — owner's revision, 2026-09-02.

   The computer is the fixed thing; the page moves INSIDE it. Exactly the
   desktop application's own layout law: the menubar and the window bar
   never leave the screen, the document scrolls in the window's scroller.
   This deliberately reverses §1's "the document scrolls the body" — §1
   was written for a window floating on wallpaper, and that window is
   gone (8.64). Source order decides the tie, which is why this block
   sits below everything else in the file.
   ═════════════════════════════════════════════════════════════════════ */
body.hostna-os-page {
  height: 100dvh;
  overflow: hidden;
}
body.hostna-os-page .win,
body.hostna-os-page .os-win--doc {
  height: calc(100dvh - var(--bar-h));
  min-height: 0;
  overflow: hidden;
  overflow: clip;
}
body.hostna-os-page .scroll,
body.hostna-os-page .os-scroll--doc {
  flex: 1;
  min-height: 0;
  height: auto;
  overflow-y: auto;
  overscroll-behavior: contain;
}