/* The service's one stylesheet.
 *
 * Hand-written CSS, no framework and no build step (decision V13): the
 * pages are server-rendered HTML, this file is the whole design layer,
 * and the browser is the only thing that has to understand it.
 *
 * Order: tokens, reset, layout, chrome, landing, forms, the preview
 * band, the job page, motion. Everything is driven by custom
 * properties, so the light and dark palettes differ only in the token
 * block and nowhere else.
 *
 * Motion doctrine: animations communicate STATE and nothing else. A
 * tile that is being drawn or re-checked carries a calm sweep — it
 * reads as diligence, not as a glitch — and a preview fades in when its
 * pixels arrive. Everything else is still, and every animation stops
 * under prefers-reduced-motion.
 *
 * Mobile is first class: hit targets are at least 44 px, the band is a
 * swipe with snap-to-tile, an enlarged preview allows pinch zoom, and
 * the file picker is the phone's own.
 */

/* -- tokens ------------------------------------------------------- */

:root {
  /* How long a kit state change takes — the page kit's own token and
     name (C.58), so the two agree when they meet: the accordion's
     opening and closing run on it. */
  --motion-quick: 200ms;
  /* C.211-B4: how far a preview whose plate is being drawn again fades
     while the new sheet is on its way; the old one stays readable */
  --redraw-dim: 0.45;
  /* JOB PAGE 9 round 4 (scope 3, laws S8 and S8a; kit/hoverintent.js):
     THE HOVER INTENT of every hover-driven grow or shrink - it opens only
     after the pointer rested, closes only after it left for a while, and
     moves calmly with no overshoot (both y control points of the curve
     stay within 0..1); and the EDGE PREVIEW of the panel's edge across an
     asymmetric zone (10 mm over the stage, 3 mm into the panel) */
  --hover-rest: 200ms;
  --hover-leave: 500ms;
  --hover-move: 220ms;
  --hover-ease: cubic-bezier(0.2, 0, 0, 1);
  --edge-hint-outside: 10mm;
  --edge-hint-inside: 3mm;
  --edge-preview-offset: 6px;
  --edge-preview-fade: 160ms;
  --edge-preview-line: 2px;
  /* 13.11.2026 (a press is never stolen): a control narrower than this
     share of the pane - a keep box, a mark, an icon - is pressed where it
     stands, so the pane does not widen while the pointer rests on it (the
     widening slid the parts list's keep box from under the resting
     pointer); a list row spans the pane and stays under the pointer */
  --hover-control-share: 0.5;
  /* owner feedback E (01.11.2026): from this width on the 3D view is
     large - the widened panel's - and shows its arrangement slider and
     starts its legend open */
  --view-large-min: 30rem;
  color-scheme: light dark;

  --paper: #f7f6f3;
  --panel: #ffffff;
  --panel-sunken: #f1efea;
  --ink: #1b1a17;
  --ink-soft: #55524b;
  --ink-faint: #83807a;
  --line: #d9d5cc;
  --line-strong: #b9b4a8;
  --accent: #1d4e89;
  --accent-ink: #ffffff;
  --accent-soft: #e6eef8;
  --good: #2f6b3d;
  --good-soft: #e6f1e8;
  --bad: #96311f;
  --bad-soft: #f8e9e5;
  --wait-soft: #f3efe2;
  /* THE SEARCH FIELD'S STATES (C.58j, owner 28.09.2026; values from the
     C.104 scope, section 5): words that find nothing wear the problem
     red, words that find something the amber of a filtered view - apart
     from the links' blue and the finished green - each on its soft fill,
     so a filtered list is never read as the whole list. The kit field's
     own frame is `--field-line` (the old frame stood at 2.07:1, under the
     3:1 a field's edge needs). Frames stand at least 3:1 and the count
     line 4.5:1 on their ground in both schemes. */
  --search-none: var(--bad);
  --search-none-soft: var(--bad-soft);
  --search-active: #8a5300;
  --search-active-soft: #fbf0d9;
  --search-ink: var(--ink);
  --field-line: #8a8578;
  /* THE PART PAINTS (C.104, owner 28.09.2026): one colour per answer to
     "is work on this part finished?" (pipeline.PART_PAINTS), the same in
     the parts list, the 3D navigator, the legend and the phone finder's
     chips. One value in both schemes, because the stage they stand on is
     dark in both; the part-paint gate measures every pair. Green is
     finished and nothing else; in progress is the green striped with the
     timber, not drawn the problem red cross-hatched, left out the timber
     faint. Colour is never alone: every row says its state in words. */
  --part-done: #43a353;
  --part-done-ink: #08110b;
  --part-todo: #c9c2b4;
  --part-fail: #ff9b8a;
  --part-run: var(--part-done);
  --part-left: var(--part-todo);
  --part-left-alpha: 0.35;
  --part-stripe: 6px;
  --part-hatch: 8px;
  /* THE KIND STYLE TABLE (C.211-B2a, PLATES_ARCHITECTURE.md 4.1): how a
     beam and a plate differ in the 3D view, with the numbers beside the
     colours; partstyle.js holds the screen-pixel sizes, assembly3d.js
     reads both and decides nothing. Never Slatlyn blue: the gate keeps
     every part colour and the selection far from the accent's hue.
     The colour shows the kind (the owner's choice of 26.10.2026): a
     finished beam is --kind-beam, a mid warm grey, a finished plate
     --kind-plate, a clearly lighter and warmer honey wood (owner review
     of 26.10.2026: apart at a glance); a part still owed work is its
     tone faded towards --kind-pending by --kind-pending-mix, one being
     drawn the paint's stripes over that. A plate's back is its
     Sichtseite moved towards its grey by --kind-back-grey and darkened
     by --kind-back-factor - clearly darker AND greyer, which no angle of
     the light undoes (a skipped or failed plate keeps its colour and
     darkens its back by --kind-back-paint only); its
     Maserung lines darken the face by --maserung-alpha every
     --maserung-pitch-mm model millimetres, thinned and faded by their
     density on screen (--maserung-min-px); selection lifts both faces
     by --select-lift and draws the neutral --select-outline on a dark
     --select-halo, on top; a part asking "Bitte prüfen" carries a
     dashed --check-outline over everything. A skipped part is
     --kind-skipped (orange), a failed one --kind-failed (red), both
     fully coloured and shining through every part in front of them at
     --xray-alpha; while the switch is on they are the paints of those
     two states everywhere on the page (body[data-kinds-3d], below).
     One value in both schemes, as the paints: the only drawn viewer
     stands on the theatre's navy in both. */
  --kind-beam: #8e8884;
  --kind-plate: #dfb872;
  --kind-pending: #ffffff;
  --kind-pending-mix: 0.6;
  --kind-back-factor: 0.47;
  --kind-back-paint: 0.7;
  --kind-back-grey: 0.7;
  --maserung-alpha: 0.06;
  /* job page 9 round 5 (SKETCH_D7B M3, C5, M2): the Maserung drawn strong
     for a surface or selection scope and during a pick; the parts outside
     the chosen scope at rest; the parts a pick cannot reach */
  --maserung-alpha-strong: 0.22;
  --scope-dim: 0.5;
  --pick-ghost: 0.15;
  --maserung-pitch-mm: 8;
  --maserung-min-px: 6;
  --select-lift: 1.08;
  --select-outline: #f4f1ea;
  --select-halo: #121314;
  --select-halo-alpha: 0.8;
  --check-outline: #ffe08a;
  /* C.211-B2b: the plate card's scope outline - the parts a hovered
     option or button will change - solid, apart from the selection's
     off-white, the check's dashed yellow and every paint */
  --surface-outline: #5fd0c2;
  --kind-skipped: #f0913a;
  --kind-failed: #ff5c5c;
  --xray-alpha: 0.3;
  /* THE ICON SET (C.58j): one size, a share of the text it stands in,
     and one stroke, in the icons' own drawing units (a 24 box), so every
     icon is drawn alike and crisp at any pixel density */
  --icon-size: 1.25em;
  --icon-stroke: 2;
  /* QA11 item 24: code blocks get their OWN high-contrast pair, dark in
     both themes (the pattern the .code-card already used), so the API
     curl box never renders pale-on-pale again. Tokenised so the
     wcag-contrast gate reads exactly what the box paints. */
  --code-bg: #1b1f27;
  --code-ink: #e8e6e1;

  --measure: 62ch;
  --radius: 10px;
  --radius-sm: 6px;
  --shadow: 0 1px 2px rgb(27 26 23 / 6%), 0 8px 24px rgb(27 26 23 / 6%);
  --shadow-lift: 0 2px 6px rgb(27 26 23 / 10%), 0 18px 40px rgb(27 26 23 / 12%);

  --s1: 0.25rem;
  --s2: 0.5rem;
  --s3: 0.75rem;
  --s4: 1rem;
  --s5: 1.5rem;
  --s6: 2rem;
  --s7: 3rem;
  --s8: 4.5rem;

  --tap: 44px;

  /* ================================================================
     THE VERTICAL RHYTHM (round 8, items 8 and 10 — the owner's two
     screenshots of 03.09.2026).

     THE FINDING. "Off on this page." floated exactly halfway between
     the projection-lines checkbox above it and the scale-steps checkbox
     below, so the eye could not tell which control it explained; the
     Project/Customer help sat as far from its own fields as from the
     next heading. Both are one defect with one cause, and the cause was
     arithmetic rather than carelessness: a help line is a GRID ITEM of
     `.field-grid`, so it inherited that grid's row gap AND added its own
     `margin-top`, which made the distance ABOVE it larger than the
     distance below. Proximity says exactly the opposite.

     THE LAW. A thing sits close to what it belongs to and clearly
     further from what comes next — the ratio is at least one to two,
     and it is these four tokens everywhere, on every page, for headings
     as much as for help texts. `--rhythm-within` is a help line to ITS
     control and a heading to what it heads; `--rhythm-between` is one
     control group to the next; `--rhythm-heading` is the air ABOVE a
     heading, which is what separates one group of things from another;
     `--rhythm-section` is one whole section from the next.

     Templates may state NONE of this. There is no vertical margin, no
     vertical padding and no row gap in any `style=` attribute or any
     per-page stylesheet anywhere on this site, and the
     `rhythm-scale` gate holds that: a new page cannot ship its own
     spacing, so it cannot ship the drift either.

     THE NUMBERS ARE CHOSEN AGAINST THE EYE AND NOT ONLY AGAINST THE BOX
     MODEL. A checkbox row is a 44 px tap target with a 22 px glyph
     centred in it, so about eight pixels of empty box stand below the
     glyph before the help line's own gap begins. Measured between BOXES
     the ratio here is one to four; measured between INK, which is what
     the owner is looking at, it is one to two — and one to two is the
     law, so the box ratio has to be better than the law to deliver it.
     That is why --rhythm-between is two rungs above --rhythm-within on
     the size scale rather than one.
     ================================================================ */
  --rhythm-within: var(--s2);        /* 0.5rem  — to what it belongs to */
  --rhythm-between: var(--s6);       /* 2rem    — to the next thing     */
  --rhythm-heading: var(--s7);       /* 3rem    — above a heading       */
  --rhythm-section: var(--s8);       /* 4.5rem  — between sections      */

  /* An icon that labels a text (round 8, item 3). Its own token rather
     than a rung of the size scale, because it is not a rhythm value: it
     is the one fixed distance between a glyph and the word it belongs
     to, and it must never be read as "one step of spacing" and tuned
     with the rest. */
  --gap-icon-label: 0.375rem;

  /* THE CLEARANCE LAW (#172, owner live-QA: the keep control's border was
     cut off at the bottom and the left of a tile). No control anywhere in
     the preview band may be clipped — not in the first tile, not in the
     last, not in the centred one, not while the band is scrolled, and not
     while the control has keyboard focus. A focus ring is drawn OUTSIDE
     its element (`:focus-visible` above: a 3px outline at a 2px offset,
     5px in all), so every scroll box a control sits inside has to leave
     at least that much room around it. This token is that room, with
     headroom to spare, and it is the ONE number the band, the tile and
     the in-tile control rows all quote — the band-clearance gate derives
     what it must be from the `:focus-visible` rule itself and refuses a
     value that is too small, so the two can never drift. */
  --focus-clearance: 0.75rem;

  /* The focus ring itself: its width and how far it stands off the
     element. `:focus-visible` paints with these two, and so does every
     kit control that has to draw the ring on a box around a hidden
     input (the choice cards and chips) — ONE ring for a keyboard reader
     on the whole site, where the kit first wrote the two numbers out a
     second time. `band-clearance` still derives the room a ring needs
     from the `:focus-visible` rule, through these names. */
  --focus-ring-width: 3px;
  --focus-ring-offset: 2px;

  /* How far a jump to #how or #limits must stop SHORT of the target, so
     the sticky header does not sit on top of the heading it just jumped
     to. The value here is the no-script fallback and is deliberately
     generous, because the header grows a row when the navigation wraps;
     abbundo.js replaces it with the header's measured height. */
  --header-offset: 6rem;

  /* C.119: the height of the entry's drop bar, the slim bar that stands
     under the header on an entry page once the drop zone is out of
     sight. Nought on every other page; kit/entrybar.js writes the bar's
     measured height here once per layout, and the scroll padding below
     adds it, so a jump or a focused control lands below the bar. */
  --entry-bar-h: 0px;

  /* THE SITE'S WRAP (C.226, home-9 point 2): the one column every page,
     the header included, stands in. 76rem (it was 72rem) so the start
     page's hero holds its 27.5rem text column beside the film at the
     film's approved 743 px; raised for every page, not the start page
     alone, so the logo never jumps between pages. On a phone it is the
     screen less the gutters, as before. */
  --wrap: 76rem;
  /* THE HERO (C.226): the start page's entry is one grid - the text
     column (audience line, headline, subline, box, help line) at this
     width, the gutter, and the film taking the rest of the wrap, so the
     film ends on the header's right edge. Below 68.75rem (1100 px) the
     columns become one and the film follows the help line. */
  --hero-text-w: 27.5rem;
  --hero-gap: var(--s6);
  /* the narrowest column a step of a row of steps keeps (kit-content.css,
     `.kit-content-steps-row`): three across the wrap, one on a phone */
  --steps-col-min: 14rem;
  /* the headline never breaks a word (owner 27.10.): its size steps down
     with the column it stands in until the longest word of the headline
     (about six ems wide) fits, and a hyphenated compound is one unit
     (pages.nobreak) */
  --h1-size: clamp(1.9rem, 1.3rem + 2.6vw, 3rem);
  --title-fit: 14cqi;
  /* C.226 (home-9 law H7): the film's replay button stands in the frame's
     top-right corner, clear of what the end still shows. Batch 39f (owner
     29.10.2026): the film's top labels reach the right edge, so the button
     sits BELOW the label band - the end stills' labels end at 8.4 % of the
     frame's height (measured off intro_*_end.webp) - plus the margin token,
     at the frame's very edge, where no sheet of the stack reaches. The gate
     reads the ink under the button out of the stills themselves
     (check_all._intro_ink_under), so a film whose labels move turns it red.
     On a frame narrower than 37.5rem (a phone) it stands at the top's
     centre instead, between the two headings and above the arrow (the rule
     beside .kit-intro-frame). */
  --intro-label-band: 8.4%;
  --intro-replay-top: calc(var(--intro-label-band) + var(--s2));
  --intro-replay-right: var(--s2);

  /* THE PAGE KIT's own numbers (round C.58a). PAGE_DESIGN_LAWS section 13
     says it plainly: the measures belong to the resource, not to the law,
     so every number the popup and the accordion need stands HERE, in the
     one token set, and `service/static/kit/kit.css` carries none of its
     own. The `kit-tokens` gate parses that file and fails on any absolute
     length, any duration and any colour literal in it, and it fails just
     as loudly on a `var(--x)` that this block does not define — so the kit
     can neither invent a number nor invent a token. Changing a measure of
     the kit is an edit of these eight lines and of nothing else. */

  /* One device pixel: the hairline every kit border is drawn with. Named
     rather than written out because a border width IS a measure, and an
     unnamed 1px in a component file is the first of the copies that the
     rhythm laws exist to prevent. */
  --hairline: 1px;

  /* What a modal dialog darkens the page behind it with. The same value
     the site already drew four separate times (`.startpop::backdrop`,
     `.viewer::backdrop`, `.preview-lightbox::backdrop`,
     `.prepare-pop::backdrop`); one name now, so the surround of every
     popup is one decision. Deliberately NOT overridden in the dark theme:
     a scrim is a shadow over the page, and a page that is already dark
     still has to recede behind what stands in front of it. */
  --scrim: rgb(0 0 0 / 62%);

  /* The popup box. WIDTH is the reading width of a popup with one column
     of controls; WIDE is the width a popup with tabs needs so two columns
     of controls fit side by side (both measured off the existing
     `.prepare-pop` and `.settings-pop` rules, which is where the kit
     inherits its proportions from). GUTTER is what is left standing
     between the box and the edge of a narrow screen, so the box shrinks
     instead of overflowing. HEIGHT is the tallest a popup may be — a
     share of the screen, capped in absolute terms so a popup on a very
     tall monitor does not become a page of its own. */
  --pop-width: 44rem;
  --pop-width-wide: 52rem;
  --pop-gutter: var(--s6);
  --pop-height: 92vh;
  --pop-height-cap: 60rem;
  /* c243: a picture popup's frame (kit.css .kit-pop-picture-frame) is as
     wide as the glass leaves beside the gutter, and shaped like its
     picture: popup.js sets the loaded picture's own ratio on the frame;
     until then a sheet of the ISO A series (1 : the square root of 2). */
  --pop-width-glass: calc(100vw - var(--pop-gutter));
  --picture-ratio: 1.414;
  /* C.96 (page design law P16): on a phone a popup is a sheet from the
     foot of the glass, at most this share of it high, and its last row
     stands clear of the phone's own bottom inset (the home bar). */
  --pop-height-phone: 90vh;
  --safe-foot: env(safe-area-inset-bottom, 0px);
  /* C.158: the screen keyboard, as kit/keyboard.js measures it on the
     visual viewport - its height and the height it leaves free. These
     are the closed keyboard's values; the script writes the open one's
     onto the root element. */
  --kb: 0px;
  --vv-top: 0px;
  --vv-height: 100vh;

  /* The narrowest a control column may become before the kit's grid drops
     to one column. Quoted by `repeat(auto-fit, minmax(...))` rather than
     by a media query, because a media query cannot read a token and the
     laws say the number lives in the token set — so the kit has a
     breakpoint without having a breakpoint number written into it. */
  --kit-col-min: 16rem;

  /* THE STAGE (C.58 step 3): the dark theatre panel the entry component
     puts around the drop zone, in the job page's own colours. Six
     literals stood on the start page's panel and six more on the job
     page's stage; the start page's read from here now, the job page's
     follow at its migration. Both schemes: the panel lifts a step in
     the dark theme, where its own near-black would sit on a page ground
     of almost the same value and read as a border and nothing else. */
  --stage-bg: #171b22;
  --stage-line: rgba(255, 255, 255, 0.12);
  --stage-line-strong: rgba(255, 255, 255, 0.25);
  --stage-ink: #e8ecf3;
  --stage-soft: #cfd9e6;
  --stage-faint: #8fa3bd;
  --stage-hover-line: #7bb0f0;
  --stage-hover-bg: rgba(255, 255, 255, 0.05);
  --stage-button-bg: rgba(255, 255, 255, 0.08);
  --stage-file-bg: rgba(255, 255, 255, 0.06);
  --stage-ready-bg: rgba(47, 107, 61, 0.22);
  --stage-ready-line: #7dc48d;
  --stage-ready-ink: #9fd8ac;
  --stage-ready-button-ink: #dff0e4;
  /* C.58j: the rest of the job page's stage, which declared these as
     literals of its own (--th-*) until the stage became one token set */
  --stage-bar: #10141b;
  --stage-rail: #0f141c;
  --stage-head: #16202c;
  --stage-sep: #6d7f95;
  --stage-sel: #22406b;
  --stage-sel-ink: #ffffff;
  --stage-sel-soft: #cfe0f5;
  --stage-field: #1b222c;
  --stage-file-ink: #dbe6f5;
  --stage-file-head: #22313f;
  --stage-file-head-ink: #eef3f9;
  --stage-button-hover: rgba(255, 255, 255, 0.18);
  --stage-fault: #ff9b8a;
  /* the search field's two state colours as they read on the stage's
     dark ground (the parts finder on the rail, C.58j) */
  --stage-search-none: var(--stage-fault);
  --stage-search-none-soft: #3a1f1c;
  --stage-search-active: #e8b84f;
  --stage-search-active-soft: #2f2816;
  /* C.223: a state that asks for the reader's attention (the Plankopf
     still open) as it reads on the stage's dark ground: amber ink on a
     dark amber step, 8:1 */
  --stage-attention: #e8b84f;
  --stage-attention-soft: #2f2816;
  --stage-field-line: #6b7280;

  /* The two type sizes the entry component uses: a lead line under a
     title, and the small print of a promise or a note. Named because
     a font size is a measure and the kit may not write one. */
  --fs-lead: 1.15rem;
  --fs-small: 0.9rem;

  /* The column the accordion's open/shut mark stands in. ONE number for
     two rules: the mark's own width, and how far the answer below is
     inset so its first letter stands under the question's first letter
     rather than under the mark. Written out as a token because an
     answer indented by a number somebody measured off a screenshot
     drifts the moment the mark changes. */
  --kit-marker: 0.75rem;

  /* How long a kit state change takes is `--motion-quick`, below with the
     line's numbers: ONE duration for every small change the kit makes. The
     popup and the accordion first carried a second one of their own
     (120 ms beside the line's 200 ms), so the same disclosure mark turned
     at two speeds on one site; the merge kept the value the site already
     used for its own markers. */

  /* ================================================================
     THE PAGE KIT'S OWN NUMBERS (C.58, page-design laws sections 2, 4
     and 13).

     Section 13 of PAGE_DESIGN_LAWS is the reason these live here and
     not in the kit's stylesheets: "the measures are the token set of
     the page kit, not the law". The law is one grid and one picture
     that follows the form; 160 px and 250 ms are this resource's
     current answer to it, and changing one of them is a change of the
     resource rather than a new ruling. The kit's own stylesheets state
     no number at all — `gate_kit_tokens_b` reads them and refuses a
     literal length or duration — so there is exactly one place on this
     site where a settings line's label column is decided.
     ================================================================ */

  /* The label column of a settings line (`_kit_line.html`). 10rem is
     the law's 160 px at the root size, written in rem so a reader who
     enlarges the page's type enlarges the column with it — a fixed
     pixel column would clip the very label a larger type is being
     asked for. */
  --line-label: 10rem;

  /* The button column of a settings line: right-aligned and FIXED, so
     every line on a page puts its button at the same x and the column
     reads as a column. Wide enough for the longest of the kit's own
     actions in German, which is the longer of the two languages. */
  --line-actions: 11rem;

  /* The gutter between the three columns of a settings line, and the
     air between two stacked buttons in the third one. The law's 16 px
     gutter, quoted from the size scale rather than restated. */
  --line-gutter: var(--s4);

  /* How long a live preview waits after the last keystroke before it
     asks the server for a new picture (`livepreview.js` reads this
     property off the root element rather than carrying a number).

     250 ms is the law's figure and it is a legibility number, not a
     performance one: below about 200 ms the picture flickers under a
     touch-typist's hands, and above about 350 ms a reader who has
     stopped typing starts to wonder whether anything is listening.
     A field that is LEFT (change, blur) never waits — that is a
     decision, not a keystroke. */
  --preview-debounce: 250ms;

  /* The measures the kit needs that the site had been spelling out at
     each of its two dozen use sites: the weight a label is set in, the
     size of a disclosure's own triangle, and how long a small state
     change takes. The rule between two things (`1px solid var(--line)`,
     written twenty-four times) is `--hairline`, defined once above with
     the popup's numbers. None of them is new to the site — they are the
     values it already uses — and none of them may be spelled out inside
     the kit, which is the point of naming them. */
  --weight-strong: 650;
  --marker-size: 0.5rem;
  --motion-quick: 200ms;

  /* How tall a live preview's frame is BEFORE it holds anything, and
     how tall it stays between two pictures of different heights. A
     floor rather than a height: the page must not jump when the
     picture changes, and a picture taller than this must still be
     allowed to be taller rather than be cropped by its own frame. */
  --preview-min: 12rem;

  /* The site's small type — a pill's word, a caption under a picture, a
     job's reference. It was written out at four slightly different
     sizes before the kit needed to quote it. */
  --font-small: 0.85rem;

  /* THE PAGE KIT'S OWN MEASURES (C.58, page design law 13: "numbers
     belong to the resource, not to the law"). The kit's stylesheets
     state no length of their own — every distance, size and duration
     they paint is one of these names or one of the names above, and the
     kit-tokens gate refuses a length written any other way. A number
     changed here is a change to the resource, in one place, for every
     page that was ever built out of it.

     --kit-card-min is the narrowest a choice card may be before the row
     drops a column. It is 10rem because three of them plus their two
     gutters are what fits across `--measure`, the width a choice group
     is read at: a three-answer question stands on ONE row on a page and
     folds by itself in a popup. It was 14rem and then 11rem first, and
     both left three answers sitting two-and-one, which reads as a group
     of two beside a stray. --kit-status-hold and --kit-status-fade are how
     long an after-action word stands and how long it takes to go, read
     by kit/action.js off the element rather than typed into the script,
     so the word's timing is a property of the component and not of the
     file that animates it. */
  --kit-card-min: 10rem;
  --kit-status-hold: 1600ms;
  --kit-status-fade: 300ms;

  /* THE KIT'S DATA BLOCKS (C.122): count tile, data table, line chart,
     bar chart, region map and funnel (`_kit_data.html`,
     `kit/kit-data.css`). Every colour a figure paints is one of the
     site's own colours under a chart name, so the dark scheme flips them
     with the rest and no figure holds a colour of its own; every measure
     is here, so `kit-data.css` writes none. Two series are told apart by
     the dash and the marker's cap as well as by colour. */
  --chart-1: var(--accent);
  --chart-2: var(--good);
  --chart-bad: var(--bad);
  --chart-rest: var(--ink-faint);
  --chart-grid: var(--line);
  --chart-axis: var(--ink-soft);
  --chart-dash: 7 4;
  --chart-marker: 7px;
  --chart-stroke: 2px;
  --chart-line-h: 15rem;
  --chart-line-h-narrow: 11rem;
  --chart-bar-h: 0.75rem;
  --chart-label-w: 12rem;
  --chart-axis-w: 3rem;
  --chart-readout-w: 11rem;
  /* the region map's five classes, lightest to full accent, and the
     ground of a region nothing was counted in */
  --map-step-1: color-mix(in srgb, var(--accent) 20%, var(--panel));
  --map-step-2: color-mix(in srgb, var(--accent) 40%, var(--panel));
  --map-step-3: color-mix(in srgb, var(--accent) 60%, var(--panel));
  --map-step-4: color-mix(in srgb, var(--accent) 80%, var(--panel));
  --map-step-5: var(--accent);
  --map-none: var(--panel-sunken);
  --map-max-w: 34rem;
  /* the narrowest a block or a tile may become before the grid drops a
     column, and the size a tile's number is set in */
  --kit-block-min: 26rem;
  --kit-tile-min: 9rem;
  --fs-tile: 1.6rem;

  --font: "Segoe UI", system-ui, -apple-system, "Helvetica Neue", sans-serif;
  --mono: ui-monospace, "Cascadia Mono", "Consolas", monospace;
}

/* Both mechanisms, on purpose: scroll-margin-top belongs to the TARGET
   and is what an in-page link honours, scroll-padding-top belongs to the
   SCROLLER and catches everything else (a focused element, a browser's
   own restore). One without the other leaves a case behind. */
html {
  /* C.119: plus the entry's drop bar, which stands under the header on
     an entry page; the target's own margin below keeps the header alone,
     so the bar's room is counted once. */
  scroll-padding-top: calc(var(--header-offset) + var(--entry-bar-h));
  scroll-behavior: smooth;
}

:where(main [id], section[id], h1[id], h2[id], h3[id]) {
  scroll-margin-top: var(--header-offset);
}

/* An expanding panel opens DOWNWARDS (round 7, the owner's phone
   finding of 01.09.2026). A <details> that opens makes the page taller
   where it stands, and the browser's scroll anchoring pays for that by
   scrolling the page down to hold some paragraph further down still —
   which pushes the control the reader just pressed, and the first lines
   of what it opened, off the top of the screen. Switching anchoring off
   for the page's own content is the half of the cure that works with
   JavaScript blocked; panels.js does the other half, bringing a control
   near the bottom edge up far enough that the panel's first line shows.

   The site pays nothing for it: every image here states its own width
   and height and no content is loaded in late, so there is no reflow
   for anchoring to smooth over in the first place. */
main#content { overflow-anchor: none; }

/* AND FOR THE PAGE ITSELF (C.122, measured 04.10.2026). With the content
   excluded, the browser still picks an anchor OUTSIDE main - the footer,
   once it stands on the screen - and an accordion near the foot of a page
   (the statistics' questions) had the browser scroll by the closed
   answer's height and back, so the kit accordion's own hold-still saw no
   movement and the pressed question jumped up by that height. The page
   scroller anchors nothing; the components that must hold something
   still (the accordion, the panels, anchor.js) do it themselves. */
html { overflow-anchor: none; }

/* And when a summary IS scrolled to, it stops below the sticky header
   rather than under it — the same offset every in-page anchor uses. */
summary { scroll-margin-top: var(--header-offset); }

@media (prefers-color-scheme: dark) {
  :root {
    --stage-bg: #232830;
    --paper: #14161a;
    --panel: #1b1e24;
    --panel-sunken: #21252c;
    --ink: #eceae5;
    --ink-soft: #b3b0a9;
    --ink-faint: #85837d;
    --line: #333842;
    --line-strong: #4a505c;
    --accent: #7bb0f0;
    --accent-ink: #10131a;
    --accent-soft: #1d2836;
    --good: #7fc490;
    --good-soft: #1a2820;
    --bad: #e39182;
    --bad-soft: #2c1d1a;
    --wait-soft: #24262b;
    --search-active: #e8b84f;
    --search-active-soft: #2e2716;
    --field-line: #6b7280;
    /* C.211-B2a: the kind style table, read for the dark scheme - the
       same values, because the 3D view's ground is the theatre's navy in
       both schemes (the gate measures each scheme on its own) */
    --kind-beam: #8e8884;
    --kind-plate: #dfb872;
    --kind-pending: #ffffff;
    --kind-pending-mix: 0.6;
    --kind-back-factor: 0.47;
    --kind-back-paint: 0.7;
    --kind-back-grey: 0.7;
    --maserung-alpha: 0.06;
    --maserung-alpha-strong: 0.22;
    --scope-dim: 0.5;
    --pick-ghost: 0.15;
    --maserung-pitch-mm: 8;
    --maserung-min-px: 6;
    --select-lift: 1.08;
    --select-outline: #f4f1ea;
    --select-halo: #121314;
    --select-halo-alpha: 0.8;
    --check-outline: #ffe08a;
    --surface-outline: #5fd0c2;
    --kind-skipped: #f0913a;
    --kind-failed: #ff5c5c;
    --xray-alpha: 0.3;
    /* QA11 item 24: the code pair stays dark and high-contrast in dark
       mode too — a hair darker than the panel so the box still reads as
       inset. */
    --code-bg: #0f1217;
    --code-ink: #e8e6e1;
    --shadow: 0 1px 2px rgb(0 0 0 / 40%), 0 8px 24px rgb(0 0 0 / 32%);
    --shadow-lift: 0 2px 6px rgb(0 0 0 / 45%), 0 18px 40px rgb(0 0 0 / 45%);
  }
}

/* -- reset -------------------------------------------------------- */

*, *::before, *::after { box-sizing: border-box; }

/* The `hidden` attribute means hidden, whatever else a rule below sets.
   Without this line the browser's own `[hidden] { display: none }` is a
   USER-AGENT rule and loses to every author rule that names a display —
   `button` does, so a button the script hides stays on the screen.

   `!important` and not merely the line, because `[hidden]` and a class
   carry the SAME specificity and the later rule then wins: `.assembly`
   and `.viewer-side` are declared eight hundred lines below and each
   names a display, so without the flag a browser that cannot run the 3D
   viewer painted its hidden scaffolding anyway — an empty grey canvas in
   the file card and a lane-width sliver at the left of the maximized
   preview. Nothing else in this file may declare a display as
   `!important`; the gate checks that, because a second flag would take
   the cascade back. */
[hidden] { display: none !important; }

/* The prefixed property is the one Blink and WebKit ship; the standard
   name stands beside it so no engine is served the prefix alone
   (VC3n). */
html { -webkit-text-size-adjust: 100%; text-size-adjust: 100%; }

body {
  margin: 0;
  background: var(--paper);
  color: var(--ink);
  font-family: var(--font);
  font-size: 1rem;
  line-height: 1.55;
  text-underline-offset: 0.15em;
  /* A phone is 402 px wide and file names, job ids, keys and URLs are
     longer than that. A word that cannot break pushes the whole page
     sideways, so words break. This fences TEXT; the two scrollers below
     fence the things that must not break at all (code and tables), and
     the header navigation wraps. Between them the page never scrolls
     horizontally — which is the rule, not an aspiration. */
  overflow-wrap: break-word;
}

/* THE HEADING RHYTHM LAW (owner, 24.08.).

   A section header keeps ONE uniform amount of air above it, everywhere
   on the site, taken from the spacing scale in :root. No page and no
   section has an answer of its own.

   What the owner met: on the settings page the "Zeichnung" and
   "Schrift" headers sat hard against the last line of the section
   before them while every other header on the same page had air. That
   was not a mistake in those two places. EVERY heading's top margin was
   zero, and the air came from one adjacency rule — `.card + h2` — which
   only fired where the previous section happened to end in a card.
   Those two headers follow a plain <div> and a <p>, so they got
   nothing. A rule that depends on what the thing before a header
   happens to be is a rule that will keep producing this defect.

   So the air is on the HEADING itself, unconditionally, and its level
   decides how much. A heading that OPENS its own box owes nothing above
   it, and that is the only exception — structural, one rule, never per
   section.

   ROUND 8, item 10 WIDENS IT AND NAMES IT. The same belonging rule the
   owner stated for help texts holds for headings: a small gap BELOW a
   heading to what it heads, a clearly larger gap ABOVE it to what came
   before, at least one to two. The numbers no longer come from the size
   scale directly — they come from the four rhythm tokens in :root, so
   the heading, the help line and the control group are all measured on
   ONE scale and nobody has to notice that --s6 above and --s3 below
   happened to be in the right ratio. Read the values: --rhythm-heading
   above (2rem), --rhythm-within below (0.5rem). Four to one. */
h1, h2, h3 {
  line-height: 1.2; text-wrap: balance;
  margin: 0 0 var(--rhythm-within);
}
h1 { font-size: var(--h1-size); letter-spacing: -0.02em; }
h2 { font-size: clamp(1.3rem, 1.1rem + 0.9vw, 1.75rem); letter-spacing: -0.01em; }
h3 { font-size: 1.05rem; }
h2 { margin-top: var(--rhythm-heading); }
h3, h4 { margin-top: var(--rhythm-between); }
h1:first-child, h2:first-child, h3:first-child, h4:first-child {
  margin-top: 0;
}
p { margin: 0 0 var(--s4); }
ul { margin: 0 0 var(--s4); padding-left: 1.2em; }
li { margin-bottom: var(--s2); }

a { color: var(--accent); text-decoration-thickness: 1px; }
a:hover { text-decoration-thickness: 2px; }

img { max-width: 100%; height: auto; display: block; }

code, kbd, samp { font-family: var(--mono); font-size: 0.92em; }

:focus-visible {
  outline: var(--focus-ring-width) solid var(--accent);
  outline-offset: var(--focus-ring-offset);
  border-radius: 3px;
}

.visually-hidden {
  position: absolute; width: 1px; height: 1px; overflow: hidden;
  clip-path: inset(50%); white-space: nowrap;
}

.skip {
  position: absolute; left: var(--s4); top: -4rem; z-index: 20;
  background: var(--panel); color: var(--ink); padding: var(--s3) var(--s4);
  border-radius: var(--radius); box-shadow: var(--shadow);
}
.skip:focus { top: var(--s3); }

/* -- layout ------------------------------------------------------- */

.wrap {
  width: min(var(--wrap), 100% - 2 * var(--s4));
  margin-inline: auto;
}

.section { padding-block: var(--rhythm-section); }
.section + .section { border-top: 1px solid var(--line); }
/* A section's own header owes nothing above it (it opens the box) and
   keeps the same small gap below it every other heading keeps — one
   scale, no per-section answer (round 8, item 10). It used to state
   --s4 here, which was a fourth number for the same question. */
.section > h2 { margin-bottom: var(--rhythm-within); }

/* `.card + h2 { margin-top: var(--s6) }` used to live here — the one
   adjacency rule that gave a section header its air, and only where the
   section before it happened to end in a card. It is gone: every
   heading carries its own air now (see the heading rhythm law near the
   top of this file), which is the same value in the same case and the
   right value in the cases this rule could not see. */
.lead { font-size: 1.15rem; color: var(--ink-soft); max-width: var(--measure); }
.prose { max-width: var(--measure); }

.grid-3 {
  display: grid;
  gap: var(--s4);
  grid-template-columns: repeat(auto-fit, minmax(15rem, 1fr));
}

/* The two-factor enrolment code. White ground and its own scroller: a
   QR is read by a camera, so it must not invert under a dark page
   theme, and on a narrow phone it must not push the page sideways. */
.qr {
  background: #fff;
  padding: var(--s3);
  border: 1px solid var(--line);
  border-radius: var(--radius-sm);
  width: fit-content;
  max-width: 100%;
  overflow-x: auto;
}
.qr svg { display: block; max-width: 100%; height: auto; }

/* -- chrome ------------------------------------------------------- */

.site-header {
  border-bottom: 1px solid var(--line);
  background: var(--panel);
  position: sticky;
  top: 0;
  z-index: 10;
}

/* On a phone the navigation wraps onto two or three rows, and a sticky
   header that tall would eat a fifth of the screen for the whole visit.
   So below this width the header scrolls away with the page: every link
   is still reachable, in full, at the top. abbundo.js reads the real
   position and drops the anchor offset to nothing when the header no
   longer stands in the way. */
@media (max-width: 47.99rem) {
  .site-header { position: static; }
}

.site-header .wrap {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--s3) var(--s5);
  min-height: 3.5rem;
  padding-block: var(--s2);
}

.brand {
  display: flex;
  align-items: center;
  gap: var(--s3);
  font-weight: 650;
  color: inherit;
  text-decoration: none;
  letter-spacing: -0.01em;
}
.brand:hover { color: var(--accent); }

/* The logo (the kit's brand, _kit_brand.html). Its size is the file's
   own: the kit writes the SVG's width and height onto the <img> (read by
   service/brand.py), and NO RULE HERE NAMES A LOGO DIMENSION, so a new
   logo is a file swap and not a hunt through the stylesheet — the owner's
   pick of 10.10.2026 (E3c, the word in a dimensioned height frame) grew
   the header logo from 114 to 134 px wide by exactly that swap. `height:
   auto` keeps the global `img { max-width: 100% }` from squashing it out
   of proportion on a narrow header, and `flex: none` stops the tagline
   beside it from stealing its width.

   TWO FILES, ONE SHOWN, switched by the same `prefers-color-scheme` as
   the colour tokens: the light logo's ink word would vanish on the dark
   panel, so the dark scheme shows the reversed file (white word, the
   dark scheme's light blue) instead. Print always takes the light one —
   ink on paper — whatever scheme the screen was in; its block stands
   after the dark one so it wins at the same specificity. */
.brand-logo { display: block; height: auto; flex: none; }
.brand-logo[data-scheme="dark"] { display: none; }
@media (prefers-color-scheme: dark) {
  .brand-logo[data-scheme="light"] { display: none; }
  .brand-logo[data-scheme="dark"] { display: block; }
}
@media print {
  .brand-logo[data-scheme="light"] { display: block; }
  .brand-logo[data-scheme="dark"] { display: none; }
}
/* `min-width: 0` because it is a flex ITEM now rather than text inside
   one: without it a long tagline refuses to shrink and pushes the row
   past a 402 px screen, which is the one thing the phone rules forbid
   outright. */
.brand-tagline {
  display: block; font-weight: 400; font-size: 0.78rem;
  color: var(--ink-faint); letter-spacing: 0;
  min-width: 0;
}

/* On a phone the tagline stands down (round 8, item 2). Below this
   width the header row cannot hold the logo, the sentence, the menu
   button and the language switch at once, and the owner's screenshot
   shows what happens when it tries: the sentence takes the whole first
   row and the menu button is pushed onto a second one, alone under the
   logo. Nothing is lost — the same claim is the landing page's own
   headline, one line further down, in type a phone can actually read.
   Above this width all four fit and the tagline stays. */
@media (max-width: 33.99rem) {
  .brand-tagline { display: none; }
}

/* The navigation WRAPS. Without this the row of real-page links cannot
   fit a 402 px phone: the items were shrunk against the right edge and
   the page grew a horizontal scrollbar. It wraps onto as many rows as
   it needs. (abbundo.js still measures the header height for the
   in-BODY anchors — the honesty strip, a deep link to a section — even
   though the navigation itself no longer carries any.) */
.site-nav {
  display: flex;
  flex-wrap: wrap;
  gap: var(--s1) var(--s4);
  margin-left: auto;
  align-items: center;
  justify-content: flex-end;
  min-width: 0;
}
.site-nav a {
  color: var(--ink-soft); text-decoration: none;
  min-height: var(--tap); display: inline-flex; align-items: center;
  /* The SAME token .nav-labelled states below, and for the same reason:
     this selector is one point more specific, so a different value here
     would silently beat the shared rule in the header — which is where
     the owner saw the glyph standing apart from its word. One token,
     two selectors that agree (round 8, item 3). */
  gap: var(--gap-icon-label);
}
.site-nav a:hover { color: var(--accent); text-decoration: underline; }
/* The page you are on, named the same way the admin bar names its own
   (aria-current="page"): the accent colour and a weight, so it reads as
   current for a sighted reader as the attribute does for a screen
   reader. */
.site-nav a[aria-current="page"] {
  color: var(--accent);
  font-weight: 650;
}
/* Konto and Kontakt carry a small inline glyph (W-nav). It is pure
   decoration — aria-hidden in the markup, the text label stays the
   accessible name — and it inherits the link's own colour through
   currentColor, so it follows hover and the current-page accent and
   needs no palette of its own. flex:none keeps it from being squeezed
   when the row wraps. */
.nav-icon { flex: none; }

/* AN ICON THAT LABELS A TEXT SITS AT IT (round 8, item 3 — the owner's
   phone screenshot of 03.09.2026: the person glyph read as a separate
   bullet with "Account" some way off to its right, and the envelope did
   the same to "Contact").

   THE LAW, and it is the whole of it: a small FIXED gap between the two,
   and nothing that can stretch between them. So this rule states the
   gap from the one token, pins the row to its start, and refuses to
   grow — `justify-content: flex-start` is written out rather than left
   to the default, because the default is what a later
   `space-between` on a wider selector would quietly beat, and that is
   the shape the defect takes when it comes back.

   ONE style, everywhere an icon labels a text: the header row, the open
   phone menu and the footer all use this class, so there is one answer
   and not three. The `icon-labels` half of the mobile-menu gate reads
   this rule out of the stylesheet and refuses a stretch. */
.nav-labelled {
  display: inline-flex;
  align-items: center;
  justify-content: flex-start;
  gap: var(--gap-icon-label);
}
.nav-labelled > .nav-icon { flex: none; margin: 0; }
/* A MENU TAKES NO SPACE IN THE PAGE FLOW (PAGE_DESIGN_LAWS 21, the
   owner's finding of 24.09.2026). The kit behaviour, on for every
   element marked `data-menu`: its `data-menu-body` is laid out OUT of
   the flow, under its trigger, so opening or closing it changes the size
   of nothing around it and nothing else on the page moves. The account
   menu used to be laid out IN the header row: a rule meant for the
   phone menu's column (`.site-nav[data-collapsible] .nav-menu`, static)
   stood outside the phone block, and nav.js marks the navigation
   collapsible at every width, so on a wide screen the open menu grew
   the header row - the name jumped up, the other entries dropped and
   the page under the header moved with them. A menu opts out only with
   `data-menu-in-flow="<why>"`, which the gate lists with its reason. */
[data-menu] { position: relative; }
[data-menu]:not([data-menu-in-flow]) > [data-menu-body] {
  position: absolute; right: 0; top: calc(100% + var(--s1)); z-index: 70;
}
/* THE ACCOUNT MENU (owner's look 23.09.2026, 13:10): the name is the
   summary of a <details>; the two entries drop under it in the wide
   header and stand in the column of the phone menu. */
.nav-account-menu > summary { cursor: pointer; list-style: none; }
.nav-account-menu > summary::-webkit-details-marker { display: none; }
.nav-menu {
  min-width: 11rem; display: flex; flex-direction: column;
  padding: var(--s1) 0; background: var(--paper); border: 1px solid var(--line);
  border-radius: var(--radius); box-shadow: var(--shadow);
}
.nav-menu-form { margin: 0; }
.nav-menu-item {
  display: block; width: 100%; text-align: left; padding: var(--s2) var(--s3);
  background: none; border: 0; font: inherit; color: var(--ink); cursor: pointer;
  text-decoration: none;
}
.nav-menu-item:hover, .nav-menu-item:focus-visible { background: var(--paper-deep, var(--line)); }
.nav-labelled > .nav-account-label,
.nav-labelled > .nav-entry-label { min-width: 0; }

/* #170: the signed-in header identity. The icon grows a small filled
   "signed in" mark of its own (a solid dot with a check, positioned on
   the icon's own corner so it never collides with the truncated name
   beside it) — decoration, exactly like the plain nav icons already
   are, so the accessible name stays the visible text (or, at the
   narrowest widths below, the link's own title attribute). */
.nav-labelled.nav-signed-in .nav-icon { position: relative; }
.nav-labelled.nav-signed-in .nav-icon::after {
  content: "";
  position: absolute; right: -3px; bottom: -2px;
  width: 9px; height: 9px; border-radius: 50%;
  background: var(--good); border: 1.5px solid var(--panel);
}
/* On the narrowest phones even the truncated address does not fit
   beside the other header controls (the language switch, the hamburger
   toggle): the label folds away and the glyph — now carrying its own
   check mark above — stands for it alone. The full address is still
   reachable, in the link's own title attribute, exactly as it is on
   every wider screen. */
@media (max-width: 26rem) {
  .nav-labelled.nav-signed-in .nav-account-label { display: none; }
}

/* The hamburger (W-mobilelanding). A real <button> (V27/VC3o), hidden on
   desktop where the navigation stands inline in full, and revealed by
   nav.js at phone widths where the links fold behind it. It never shows
   on a wide screen, so the desktop header is unchanged. */
.nav-toggle {
  display: none;
  align-items: center;
  justify-content: center;
  width: var(--tap);
  height: var(--tap);
  padding: 0;
  border: 1px solid var(--line-strong);
  border-radius: var(--radius-sm);
  background: var(--panel);
  color: var(--ink);
  cursor: pointer;
}
.nav-toggle:hover { color: var(--accent); border-color: var(--accent); }
.nav-toggle-icon { flex: none; }

/* The rest of the site, inside the header menu (W-mobilemenu, round 7).
   It is display:none everywhere and the phone rule below turns it on
   only once nav.js has marked the navigation collapsible, so the wide
   header row is exactly the five links it always was, and a reader with
   the script blocked keeps the full inline navigation and the footer
   directory rather than a menu that cannot open. */
.nav-more { display: none; }

/* THE PHONE HEADER (W-mobilelanding, repaired round 7).
   These rules used to stand higher up the file, ABOVE the .nav-toggle
   block just written: a media query adds no specificity, so the plain
   `.nav-toggle { display: none; }` there won the cascade at every width
   and the hamburger was never drawn. On a phone the header therefore
   showed the logo and the language switch and nothing else, with the
   navigation hidden behind a button nobody could see — the owner's
   finding of 01.09.2026. They stand here, after the rules they
   override, which is what makes them apply. */
@media (max-width: 47.99rem) {
  /* ONE header row, in the owner's own order (round 8, item 2): the
     logo, then the menu button, then DE/EN. It used to read logo, DE/EN,
     button — and on a 390 px phone it did not read that way at all,
     because the brand's tagline took the whole first row and pushed the
     button and the switch onto a second one, where the button stood
     alone under the logo. That is the screenshot of 03.09.2026.

     Two things fix it and both are needed. The `order` values put the
     button before the switch, and `.brand` is allowed to SHRINK
     (`min-width: 0`, and the tagline gone below the width where it
     cannot fit) so all three fit the one row. The row still wraps — it
     has to, because the open navigation drops beneath it as a full-width
     sheet at order 3.

     And the brand's BASIS is zero (C.168): a wrapping flex row forms its
     lines from each item's full width before anything shrinks, so a brand
     as wide as its logo and its whole slogan sent DE/EN onto a second row
     between 34 and 48rem — measured at 560 px with the wider logo E3c and
     the longer slogan of 10.10.2026. With a zero basis the row is formed
     from the button and the switch alone, the brand takes the rest, and
     the slogan wraps inside it instead of pushing anything down. */
  .nav-toggle { display: inline-flex; order: 1; }
  .brand { margin-right: auto; min-width: 0; flex: 1 1 0; }
  .lang-switch { order: 2; }

  /* The navigation collapses ONLY once nav.js has marked it collapsible
     (data-collapsible). With the script blocked it carries no such mark,
     stays visible and every link is reachable — the server-rendered
     fallback, never a dead menu. When marked it drops to its own full
     width row below the header and the button opens it downward. */
  .site-nav[data-collapsible] {
    display: none;
    order: 3;
    margin-left: 0;
    flex-basis: 100%;
    flex-direction: column;
    /* THE TWO-COLUMN DEFECT (round 8, item 2 — the owner's screenshot of
       03.09.2026: the open menu rendered as two side-by-side columns
       whose texts ran into each other, "Automatic dimensioning" over the
       top of "LEGAL").

       `.site-nav` above is the WIDE header's row and carries
       `flex-wrap: wrap` so those links can wrap onto a second line. This
       rule turned the same box into a COLUMN and put a 70vh ceiling on
       it — and a wrapping column flex box that runs out of height does
       not scroll, it starts a second column. The menu was doing exactly
       what it had been told. `nowrap` is the whole cure: one column, as
       long as it needs to be, scrolling inside its own ceiling. */
    flex-wrap: nowrap;
    align-items: stretch;
    gap: 0;
    margin-top: var(--rhythm-within);
    border-top: 1px solid var(--line);
    max-height: 70vh;
    overflow-y: auto;
    overscroll-behavior: contain;
  }
  /* THE OPEN PHONE MENU TAKES NO SPACE EITHER (PAGE_DESIGN_LAWS 21): it
     is a sheet laid over the page under the header row, not a row that
     pushes the page down. The header's own row is the box it hangs
     from, so the sheet lines up with the logo and the switch above it;
     the header keeps its height whether the sheet is open or shut. */
  .site-header .wrap { position: relative; }
  .site-nav[data-collapsible] {
    position: absolute;
    /* under the header's own hairline, which is the sheet's top edge */
    top: calc(100% + 1px);
    left: 0;
    right: 0;
    margin-top: 0;
    border-top: 0;
    z-index: 70;
    background: var(--panel);
    border-bottom: 1px solid var(--line);
    box-shadow: var(--shadow);
  }
  .site-nav[data-collapsible].open { display: flex; }
  /* Inside the sheet the account menu stands in the sheet's own column:
     the sheet is already out of the page flow and scrolls itself, and a
     box floating over the sheet would be clipped by that scroller. */
  .site-nav[data-collapsible] [data-menu] > [data-menu-body] {
    position: static; box-shadow: none; border: 0; border-radius: 0; padding: 0;
  }
  .site-nav[data-collapsible] a {
    padding-block: var(--s3);
    border-bottom: 1px solid var(--line);
  }
  /* The whole site inside the open menu. `display: contents` drops the
     wrapper's own box so its headings and links join the menu column as
     rows of their own, which is what keeps one border rhythm down the
     list instead of a box inside a box. */
  .site-nav[data-collapsible] .nav-more { display: contents; }
  /* A long group, folded behind its own heading (round 8, item 2).
     Deliberately NOT `display: contents`: that would drop the
     <details> box, and the closed state is drawn by the element's own
     content slot, which more than one browser stops hiding when the box
     is gone. It stays a real block; its links are made full-width rows
     so the single column reads the same whether a group is folded or
     not. */
  .site-nav[data-collapsible] .nav-more-group { display: block; }
  .site-nav[data-collapsible] .nav-more-group > a { display: flex; }
  .nav-more-heading {
    margin: 0;
    padding-block: var(--rhythm-within);
    padding-top: var(--s4);
    font-size: 0.78rem;
    font-weight: 650;
    text-transform: uppercase;
    letter-spacing: 0.06em;
    color: var(--ink-faint);
  }
  /* The folded group's heading is a control, so it says so: the pointer,
     the tap height every other menu row has, and a marker that turns
     when it opens. */
  summary.nav-more-heading {
    cursor: pointer;
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: var(--gap-icon-label);
    min-height: var(--tap);
    border-bottom: 1px solid var(--line);
    list-style: none;
  }
  summary.nav-more-heading::-webkit-details-marker { display: none; }
  summary.nav-more-heading::after {
    content: "";
    flex: none;
    width: 0.5rem; height: 0.5rem;
    border-right: 2px solid currentColor;
    border-bottom: 2px solid currentColor;
    transform: rotate(45deg) translate(-0.1rem, -0.1rem);
  }
  .nav-more-group[open] > summary.nav-more-heading::after {
    transform: rotate(-135deg) translate(-0.15rem, -0.15rem);
  }
}

/* A dependent setting, shown as dependent (round 7). The control is
   really disabled — the browser refuses the click and the keyboard
   skips it — and this only says so to the eye; the sentence naming the
   setting it needs is real text beside it, never a colour. */
.setting-dependent.depends-unmet > span,
.setting-dependent.depends-unmet > label { opacity: 0.55; }
.setting-dependent.depends-unmet { cursor: default; }
.depends-note { font-style: italic; }

.lang-switch { display: flex; gap: var(--s1); align-items: center; }
.lang-switch a, .lang-switch span {
  min-width: var(--tap); min-height: var(--tap);
  display: inline-flex; align-items: center; justify-content: center;
  padding-inline: var(--s2);
  border-radius: var(--radius-sm);
  font-size: 0.85rem; text-transform: uppercase; letter-spacing: 0.06em;
  text-decoration: none;
}
.lang-switch span { background: var(--accent-soft); color: var(--accent); font-weight: 650; }
.lang-switch a { color: var(--ink-faint); }
.lang-switch a:hover { background: var(--panel-sunken); color: var(--ink); }

/* THE EXAMPLE CALL, as a terminal card (round 7C).

   A real <pre><code>, not a picture and not a paragraph pretending to
   be code: a reader selects it and pastes it, which is the whole point
   of showing it. The dark ground is the one place on this site that
   inverts, because a terminal is what this is and a reader recognises
   it before reading a word of it.

   IT SCROLLS SIDEWAYS AND NEVER WRAPS, and it does that through the
   site's own `.code-scroll` — the wrapper a code block already lives in
   here, exactly as a table lives in `.table-scroll`. A curl line broken
   mid-flag is a line that fails when pasted, so `white-space: pre` (the
   <pre> default, kept) holds it on one line and the WRAPPER takes the
   scroll instead of the page. This class only adds the terminal ground
   on top of that shape; it invents no second way to scroll, which is
   what `mobile-layout` refused about the first cut and was right to.

   `tabindex="0"` in the markup because a scrollable box that only a
   mouse can scroll is unreachable from a keyboard — the browser gives a
   focusable element arrow-key scrolling for free. */
.code-card {
  margin: var(--s5) 0;
  border-radius: var(--radius);
  border: 1px solid var(--line-strong);
  background: var(--code-bg);
  overflow-x: auto;
  overscroll-behavior-x: contain;
  -webkit-text-size-adjust: 100%;
  text-size-adjust: 100%;
}
.code-card pre {
  margin: 0;
  padding: var(--s4) var(--s5);
  background: none;
  border: 0;
  color: var(--code-ink);
  font-family: var(--mono);
  font-size: 0.86rem;
  line-height: 1.6;
}
.code-card code {
  background: none;
  color: inherit;
  padding: 0;
  font-size: inherit;
}
.code-card:focus-visible {
  outline: 3px solid var(--accent);
  outline-offset: 2px;
}

.site-footer {
  border-top: 1px solid var(--line);
  background: var(--panel);
  padding-block: var(--s6);
  color: var(--ink-soft);
  font-size: 0.92rem;
}
.site-footer .wrap { display: grid; gap: var(--s4); }
.site-footer .notice { font-style: italic; color: var(--ink); }

/* The footer directory is grouped now (W-mobilemenu): the same
   `service.pages.site_menu` the phone menu renders, one column per run
   of links with its own heading, wrapping to as many rows as the width
   allows. */
.footer-links {
  display: flex; flex-wrap: wrap;
  gap: var(--s2) var(--s6);
  align-items: flex-start;
}
.footer-group {
  display: flex; flex-direction: column;
  gap: var(--s1);
  min-width: 0;
}
.footer-group-heading {
  margin: 0 0 var(--s1);
  font-size: 0.78rem; font-weight: 650;
  text-transform: uppercase; letter-spacing: 0.06em;
  color: var(--ink-faint);
}
.footer-links a {
  min-height: var(--tap); display: inline-flex; align-items: center;
  color: var(--ink-soft);
}
.footer-links a:hover { color: var(--accent); }

/* -- documents (legal drafts and manuals) -------------------------- */

/* The two per-page heading margins that used to stand here said --s6
   for an h2 and --s5 for an h3 — the same two values the heading rhythm
   law now gives every heading on the site. They are gone because a
   document page is not a special case, and a second statement of a
   value is a second place for it to drift. */
.document { max-width: var(--measure); }
.document blockquote {
  margin: var(--s4) 0; padding: var(--s3) var(--s4);
  border-left: 3px solid var(--accent); background: var(--panel-sunken);
  border-radius: 0 var(--radius-sm) var(--radius-sm) 0;
}
/* Code blocks and tables get their OWN sideways scroll, so the page
   keeps its. Both wrappers are produced by the renderer, so a document
   cannot grow an unfenced one. */
.code-scroll, .table-scroll {
  overflow-x: auto;
  max-width: 100%;
  -webkit-overflow-scrolling: touch;
}
.code-scroll { margin: var(--s4) 0; }
.code-scroll pre { margin: 0; }
.document pre, .code-scroll pre {
  padding: var(--s3) var(--s4);
  background: var(--panel-sunken); border-radius: var(--radius-sm);
  border: 1px solid var(--line);
}
/* ...except where the wrapper is ALSO a terminal card. `.code-card pre`
   says the same three things higher up the file and loses on source
   order alone, both selectors weighing the same, so a card carrying
   both classes drew light ink on the light sunken ground — the one
   combination nobody can read. The card's own ground is restated here
   at a weight the ordering cannot beat. Found on the start page's API
   popup (14.09.2026); the same pair of classes has been the API band's
   markup since it was written, so this was wrong there too. */
.code-scroll.code-card pre {
  background: none;
  border: 0;
  color: var(--code-ink);
}
/* inside a scroller a line may be as long as it likes; everywhere else
   an inline code span breaks like a word */
.code-scroll code { white-space: pre; }
.document code { overflow-wrap: anywhere; }
.document hr { border: 0; border-top: 1px solid var(--line); margin: var(--s5) 0; }
.document table { margin: var(--s4) 0; }

.banner-draft {
  margin: 0 0 var(--s5);
  padding: var(--s4);
  border: 1px solid var(--bad);
  border-radius: var(--radius);
  background: var(--bad-soft);
  color: var(--bad);
  font-weight: 600;
}

/* -- pricing -------------------------------------------------------- */

.tiers { margin-bottom: var(--s5); }
.tier { display: flex; flex-direction: column; gap: var(--s2); }
.tier .price { font-size: 1.5rem; margin: 0; }
.tier .price strong { letter-spacing: -0.02em; }
.tier .price .muted { font-size: 0.9rem; }
.tier .units { font-weight: 650; margin: 0; }

/* A12, owner ruling: the expiry sentence stands directly beside the
   price and is NOT small print. The attack's whole point is that an
   expiry a reader has to hunt for is what makes a piece-price image
   misleading; printed at the size of the offer's own statement it is
   simply part of the offer.

   THE ONE JUDGEMENT CALL, recorded here because it departs from the
   literal instruction: the price NUMBER is 1.5rem, and a full
   sentence set at 1.5rem would be larger than the tier heading and
   would wrap to four lines in a card. This takes the size of the
   line that states what the plan GIVES (.tier .units, the card's
   body size) instead, weighted the same, so it reads as a term of
   the offer rather than as a footnote. What the ruling forbids —
   small print — is what the gate measures: never .muted, and never
   smaller than the units line beside it.

   No colour of its own. It is not a warning and not an error; it is
   a term, and painting it red would be the warning-style law
   broken in the other direction. */
.tier .expiry { font-weight: 650; margin: 0; font-size: inherit; }
.tier p:last-child { margin-top: auto; padding-top: var(--s3); }

/* A LINE, not a fifth tier card: there is no product behind it. */
.on-request {
  margin: 0 0 var(--s5);
  padding: var(--s3) var(--s4);
  border: 1px dashed var(--line-strong);
  border-radius: var(--radius);
  color: var(--ink-soft);
}
.on-request a { margin-left: var(--s2); }

.quote-clauses {
  margin: 0 0 var(--s5);
  padding: var(--s4);
  border-left: 3px solid var(--accent);
  background: var(--panel-sunken);
  border-radius: 0 var(--radius) var(--radius) 0;
  max-width: var(--measure);
}
.quote-clauses p:last-child { margin-bottom: 0; }

/* The billing terms below the tiers fold in the kit's accordion (a
   native <details>, keyboard-reachable, open with JS off; C.58k); the
   page keeps only the place it stands in. */
.pricing-rules { margin: var(--s5) 0 0; max-width: var(--measure); }

.doc-list { list-style: none; padding: 0; margin: 0; display: grid;
            gap: var(--s3); }
.doc-list a { font-weight: 650; }
.doc-list li { margin: 0; }

/* -- the start page (round C.23) ----------------------------------- */

/* The owner's orders of 13.09.2026: the start page is the job page's
   sibling. One headline, the drop area in the theatre's own dark panel,
   a sticky action bar, and nothing on the first screen a first visitor
   did not come for.

   The two-column hero — headline and sales copy on the left, an upload
   CARD on the right, the sample sheet underneath — is gone with the card
   it was built around, and so is its phone `order` block: there is one
   column now at every width, so there is nothing left to reorder. */
.start {
  padding-block: var(--s4) var(--s6);
  background:
    linear-gradient(var(--paper), var(--paper)),
    repeating-linear-gradient(0deg, var(--line) 0 1px, transparent 1px 2.5rem),
    repeating-linear-gradient(90deg, var(--line) 0 1px, transparent 1px 2.5rem);
  background-blend-mode: normal;
  border-bottom: 1px solid var(--line);
}
/* the page's one submit is pinned to the viewport's foot, so the flow
   ends far enough above it that the bar can never cover the last line —
   the same clearance law the phone-pinned Draw button carried */
.startform {
  padding-bottom: calc(var(--tap) + var(--s6)
                        + env(safe-area-inset-bottom, 0px));
}

/* THE HERO (C.226, home-9 point 2, owner-approved 27.10.2026). The stool
   picture, its two captions and the batch line left the page: the film
   tells what they told. The entry is ONE GRID: the text column at
   --hero-text-w (the audience line, the owner's headline and subline,
   the box, the help line) and the film in the rest of the site's wrap,
   so every block of the page starts on the logo's left edge and the
   film ends on the language switch's right edge (law H2). Below 1100 px
   the columns become one: the box and its help line come BEFORE the
   film, so a phone has the upload in the first view (owner's answer to
   question 2, law H3). */
.start .startform { padding-bottom: var(--rhythm-between); }
.kit-entry.kit-entry-hero {
  display: grid;
  grid-template-columns: var(--hero-text-w) minmax(0, 1fr);
  column-gap: var(--hero-gap);
  align-items: start;
}
/* the text column is the headline's container: the headline's size
   steps down with this column (--title-fit) and never breaks a word */
.kit-entry-main {
  container-type: inline-size;
  min-width: 0;
}
.kit-entry-hero .kit-intro { margin: 0; }
/* the replay button at the top's centre on a narrow film (see the
   --intro-replay-* tokens); the frame is its container (kit-intro.css) */
@container (max-width: 37.5rem) {
  .kit-intro .kit-intro-replay {
    --intro-replay-right: calc(50% - var(--tap) / 2 + var(--s2));
  }
}
@media (max-width: 68.74rem) {
  .kit-entry.kit-entry-hero { grid-template-columns: minmax(0, 1fr); }
  .kit-entry-hero .kit-intro { margin-top: var(--rhythm-between); }
}
/* the headline's four lines stand close, as a block (home-9 3.1's
   height budget: 52 px a line at 1280) */
.kit-entry-hero .kit-entry-title { line-height: 1.04; }
/* the audience line: small, above the headline, where the eye starts */
.kit-entry-audience {
  margin: 0 0 var(--s2);
  color: var(--ink-soft);
  font-size: var(--fs-small);
}
/* the box on the hero is the zone itself on the theatre's ground: the
   stage gives up its own padding and frame so the zone's dashed edge is
   the box's edge and the ready line ("add more files" or "Draw") fits
   the text column on one row */
.kit-entry-hero .kit-entry-stage {
  padding: 0;
  border: 0;
}
.kit-entry-hero .kit-entry-stage .kit-entry-job { margin: var(--s2) var(--s3); }
.kit-entry-hero .dropzone {
  min-height: 0;
  gap: var(--s2);
  padding: var(--s3);
}
.kit-entry-hero .dropzone strong { font-size: 1rem; }
.kit-entry-hero .dropzone-choices { gap: var(--s2); }
/* the help line under the box: price words, then the terms */
.kit-entry-help {
  margin: var(--s2) 0 0;
  max-width: none;
  line-height: 1.45;
}
.kit-entry-help .start-price-slot > [hidden] { display: none; }
/* the terms on their own line, smaller, full width */
.kit-entry-terms {
  margin: var(--s1) 0 0;
  max-width: none;
  font-size: var(--fs-small);
  line-height: 1.45;
}

/* home-9 A (second half): the film's column holds the film and, under
   it, the sample row - the button to the sample and its live price line */
.kit-entry-side {
  display: flex;
  flex-direction: column;
  gap: var(--s3);
  min-width: 0;
}
.kit-entry-hero .kit-entry-side .kit-intro { margin: 0; }
@media (max-width: 68.74rem) {
  .kit-entry-hero .kit-entry-side { margin-top: var(--rhythm-between); }
}
.start-sample {
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  gap: var(--s2) var(--s3);
}
.start-sample-line {
  flex: 1 1 18rem;
  margin: 0;
  max-width: var(--measure);
  line-height: 1.45;
}
.start-sample-line > [hidden] { display: none; }

/* home-9 B (law H10 as restated by the owner, 28.10.2026): one sheet of
   the sample as a THUMBNAIL - about a third of the content width on a
   wide screen (--sheet-thumb-w, 24rem: 384 px at 1280), the whole sheet
   always visible, full width on a phone but never taller than
   --sheet-thumb-h. It is read in the popup at its native size. White
   paper in both themes because it is the stored preview itself. */
.start-sheet {
  --sheet-thumb-w: 24rem;
  --sheet-thumb-h: 60vh;
  margin: 0;
  width: 100%;
  max-width: var(--sheet-thumb-w);
}
.start-sheet-frame {
  display: block;
  border: var(--hairline) solid var(--line);
  background: #fff;
  position: relative;
  cursor: zoom-in;
}
/* the picture is the control (owner, 29.10.2026): it lifts on hover and
   focus, and a corner badge names the action */
@media (prefers-reduced-motion: no-preference) {
  .start-sheet-frame { transition: box-shadow 0.15s ease; }
}
.start-sheet-frame:hover,
.start-sheet-frame:focus-visible { box-shadow: var(--shadow-lift); }
.start-sheet-frame:focus-visible {
  outline: var(--focus-ring-width) solid var(--surface-outline);
  outline-offset: var(--focus-ring-offset);
}
.start-sheet-badge {
  position: absolute;
  right: var(--s2);
  bottom: var(--s2);
  display: inline-flex;
  align-items: center;
  gap: var(--s1);
  padding: var(--s1) var(--s2);
  border-radius: var(--radius-sm);
  border: var(--hairline) solid var(--line-strong);
  background: var(--panel);
  color: var(--ink);
  font-size: var(--fs-small);
  font-weight: 650;
  line-height: 1.2;
  pointer-events: none;
}
.start-sheet-badge-icon { width: 1em; height: 1em; flex: none; }
.start-sheet-image {
  display: block;
  width: 100%;
  height: auto;
  max-height: var(--sheet-thumb-h);
  object-fit: contain;
}
.start-sheet figcaption { margin-top: var(--s2); }
.start-sheet-whole { margin-top: var(--s5); text-align: left; }
/* the plate and the beam beside it (owner, 29.10.2026): two thumbnails
   side by side on a wide screen (2 x 384 px and the gap inside 1216),
   stacked on a phone; one sheet alone keeps its place on the left */
.start-sheets {
  display: flex;
  flex-wrap: wrap;
  align-items: flex-start;
  gap: var(--s4) var(--s5);
  margin-top: var(--s4);
}
.start-sheets > .start-sheet { flex: 1 1 18rem; }
@media (max-width: 40rem) {
  .start-sheet { max-width: none; }
  .start-sheets > .start-sheet { flex-basis: 100%; }
}
/* THE SHEET VIEWER'S FRAME (c243): the box an enlarged sheet is looked at
   in (kit/sheetview.js owns every gesture inside it). It clips, centres
   the sheet both ways so a zoom turns about its true middle, gives every
   finger to the script (no page scroll, no browser pinch fighting the
   viewer) and keeps a scroll from leaking to the page behind (law 18).
   The sunken tone tells the letterbox from the sheet's own white paper. */
.sheet-view {
  position: relative;
  display: flex;
  align-items: center;
  justify-content: center;
  overflow: hidden;
  touch-action: none;
  overscroll-behavior: contain;
  background: var(--panel-sunken);
  border: var(--hairline) solid var(--line);
  cursor: zoom-in;
  -webkit-user-select: none;
  user-select: none;
}
.sheet-view[data-zoomed="true"] { cursor: grab; }
.sheet-view[data-zoomed="true"]:active { cursor: grabbing; }
.sheet-view:focus-visible {
  outline: var(--focus-ring-width) solid var(--accent);
  outline-offset: var(--focus-ring-offset);
}
/* c248: until the viewer has fitted the sheet (its script still on the
   way, the frame not yet measured) the picture stands WHOLE inside the
   frame by this rule alone, never at its own size; the viewer's fit
   overrides it on the element */
.sheet-view > img {
  display: block;
  flex: none;
  max-width: 100%;
  max-height: 100%;
  object-fit: contain;
  background: #fff;
  -webkit-user-drag: none;
  user-drag: none;
}
/* c248: A POPUP THAT HOLDS THE SHEET VIEWER GIVES ITS FRAME WHAT THE POPUP
   LEAVES after its title, its lines and its foot. A frame of a fixed share
   of the window stood beside them in a popup capped at another share, so
   on a short window the body scrolled and the sheet opened with its lower
   edge (and the title block on it) under the foot. The body is a column,
   its lines keep their height, the frame gives way down to a floor; below
   the floor the body scrolls as any popup does. The popup says so itself
   (kit_popup(..., viewer=True) marks its body), so the rule needs no
   :has() and holds before any script. */
.kit-pop-body-viewer { display: flex; flex-direction: column; }
.kit-pop-body-viewer > * { flex: none; }
.kit-pop-body-viewer > .sheet-view { flex: 0 1 auto; min-height: 12rem; }
/* the start page's enlargement: as tall as the popup leaves room for */
.start-sheet-pan { height: min(68vh, 68dvh); }

/* „Gut zu wissen“ (C.226, home-9 E): the facts as a quiet list, then the
   four lookups as the group's own buttons */
.start-facts {
  list-style: none;
  margin: 0;
  padding: 0;
  display: flex;
  flex-wrap: wrap;
  gap: var(--s2) var(--s5);
}
.start-lookups { margin-top: var(--s4); }

/* The newsletter sign-up (C.26): one line — an address, a button, and
   the consent sentence that is the box's own label, wrapping under both
   on a narrow screen. Quiet by design: it is an offer on a page whose
   first business is the upload. */
/* C.226: the form stands in its own group („Neuigkeiten“), whose header
   and hairline are the content kit's, so the form draws no rule of its
   own */
.start-news {
  display: flex; flex-wrap: wrap; align-items: center;
  gap: var(--s2) var(--s3);
  margin: 0;
}
.start-news-address { flex: 1 1 16rem; margin: 0; }
.start-news-submit { flex: 0 1 auto; }
.start-news-consent {
  flex: 1 1 100%;
  align-items: flex-start;
  font-size: 0.82rem; font-weight: 400; color: var(--ink-faint);
}
.start-news-consent input { flex: none; margin-top: 0.1em; }

.claims { list-style: none; padding: 0; margin: 0; display: grid; gap: var(--s2); }
.claims li {
  display: flex; gap: var(--s3); align-items: baseline;
  color: var(--ink-soft);
}
.claims li::before {
  content: "";
  flex: none;
  width: 0.55rem; height: 0.55rem;
  border: 2px solid var(--accent);
  border-radius: 2px;
  transform: translateY(-0.1em);
}

/* The sample drawing. It is a real sheet, so it is shown as one: a
   framed page on the hero's grid, never cropped and never larger than
   its column. */
.sample {
  margin: var(--s5) 0 0;
  max-width: 100%;
}
.sample img {
  width: 100%;
  border: 1px solid var(--line-strong);
  border-radius: var(--radius-sm);
  background: #fff;
  box-shadow: var(--shadow);
}
.sample figcaption {
  margin-top: var(--s2);
  color: var(--ink-faint);
  font-size: 0.85rem;
}

/* The honesty doctrine as one visible line, leading to the numbers. */
.honesty-strip {
  margin: var(--s5) 0 0;
  padding: var(--s3) var(--s4);
  border-left: 3px solid var(--accent);
  background: var(--panel-sunken);
  border-radius: 0 var(--radius-sm) var(--radius-sm) 0;
  color: var(--ink-soft);
}
.honesty-strip a { margin-left: var(--s2); }

/* The FAQ list (round C.23). `<dl class="faq">` is the shape the feature
   pages, the API page and the stamp stage have used for a year, and the
   stylesheet had no opinion about it at all — so the browser's own
   default indent was the only thing separating a question from its
   answer, and the answer from the next question. The proximity law says
   which of those two gaps is the small one: an answer belongs to the
   question above it, and the next question is what comes next. */
.faq { margin: 0; }
.faq dt {
  margin: var(--rhythm-between) 0 var(--rhythm-within);
  font-weight: 650;
  color: var(--ink);
}
.faq dt:first-child { margin-top: 0; }
.faq dd {
  margin: 0;
  padding-left: var(--s4);
  border-left: 2px solid var(--line);
  color: var(--ink-soft);
  max-width: var(--measure);
}
.faq dd > :last-child { margin-bottom: 0; }

/* -- cards -------------------------------------------------------- */

.card {
  background: var(--panel);
  border: 1px solid var(--line);
  border-radius: var(--radius);
  padding: var(--s5);
  box-shadow: var(--shadow);
}
.card h3 { margin-bottom: var(--s2); }
.card p:last-child { margin-bottom: 0; }

.quote-notice {
  margin: var(--s3) 0 0;
  padding: var(--s3) var(--s4);
  border-left: 3px solid var(--accent);
  background: var(--panel-sunken);
  border-radius: 0 var(--radius-sm) var(--radius-sm) 0;
  font-style: italic;
}

/* A dashed fact list.

   ROUND 8, item 14 (the owner, 03.09.2026): on the API guide the /docs
   and /redoc rows rendered their description ONE CHARACTER PER LINE.

   THE CAUSE, and it is general rather than local to that page. A row
   used to be a two-column grid, `1.5rem 1fr`, which is right only for a
   row whose whole content is ONE grid item. Every element child is an
   item of its own, and so is every contiguous run of text — so a row
   written as `<a>…</a> — some words` produced THREE items: the dash
   marker, the link, and the words. The words were auto-placed into the
   next free cell, which is the 1.5rem marker column on an implicit
   second row, and 24 pixels is about one character wide. Every other
   fact list on this site happens to hold exactly one child per row,
   which is the only reason nothing had shown it before.

   THE CURE IS THE ROW ITSELF, not that one template. The marker comes
   out of the flow and the row is ordinary text again, so a row may hold
   as many elements and text runs as it likes and they read as one
   sentence. A list row must not depend on having exactly one child;
   that dependency WAS the defect. */
.facts { list-style: none; padding: 0; margin: 0; display: grid; gap: var(--s3); }
.facts li {
  position: relative;
  padding-left: calc(1.5rem + var(--s3));
}
.facts li::before {
  content: "\2014";
  position: absolute;
  left: 0;
  top: 0;
  width: 1.5rem;
  color: var(--accent);
  font-weight: 700;
}

/* -- forms -------------------------------------------------------- */

/* THE STICKY ACTION BAR (round C.23, owner 13.09.2026), the start page's
   answer to the job page's sticky dock: Draw, the title block with its
   mark, and the two popups, on the screen at every scroll position and
   at every width.

   It replaces fix #3.5's phone-only pinned Draw button, which existed
   because "the primary Draw button sits far below the fold" — and which
   was true on a desktop too, once the page had grown a view picker, a
   language select, a title block and two disclosures. The answer is no
   longer a breakpoint; it is that the actions live in a bar of their
   own. `env(safe-area-inset-bottom)` clears the home-indicator strip on
   a notched phone; the fallback `0px` is what every other browser
   reads, and `.startform`'s own bottom padding is what keeps the bar
   from ever covering the form's last line. */
.start-bar {
  position: fixed;
  left: 0; right: 0; bottom: 0;
  z-index: 15;
  display: grid;
  gap: var(--s1);
  padding: var(--s2) var(--s4);
  padding-bottom: calc(var(--s2) + env(safe-area-inset-bottom, 0px));
  background: var(--panel);
  border-top: 1px solid var(--line-strong);
  box-shadow: var(--shadow-lift);
}
/* one column for the row and the retention line, so the bar's contents
   stand over the page's own column rather than at the screen's edge */
/* C.226 (home-9): the bar's row stands over the site's own column, so its
   Draw button starts on the page's left edge and the settings button
   ends on its right edge; between them the reason line while no file is
   held, the settings summary once one is (the quiet bar, law H4) */
.start-bar-row {
  width: min(var(--wrap), 100%);
  margin-inline: auto;
}
.start-bar-row {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--s2) var(--s4);
}
.start-draw { flex: 0 1 20rem; }
.start-bar .button-ghost { flex: 0 1 auto; padding-inline: var(--s3); }
.start-bar .start-settings { margin-left: auto; }
.start-bar-row > .start-bar-reason {
  flex: 1 1 12rem;
  margin: 0;
}
.dock-stamp-dot[hidden],
.start-settings-summary[hidden] { display: none; }
/* The bar is fixed for the whole page, not only for the form, so the
   page's own last line owes it the same clearance the form does. The
   footer is what ends every page, so that is where the room goes —
   scoped to a page that really carries the bar, because no other page
   has anything pinned to its foot. A browser with no :has() loses the
   room and nothing else: the bar covers the footer's last line, which
   is the site's own address row and not a control. */
body.has-start-bar .site-footer {
  padding-bottom: calc(var(--tap) + var(--s6)
                        + env(safe-area-inset-bottom, 0px));
}

/* the title block's incomplete mark: the job page's own dot and its own
   colour, but plain words rather than a filled pill — the sentence the
   owner asked for is a sentence and does not fit in a badge */
.start-stamp .stamp-state {
  background: transparent;
  color: #8a5a10;
  padding: 0;
  font-size: 0.85em;
  font-weight: 500;
}
@media (max-width: 47.99rem) {
  /* On a phone the bar has two rows (C.226, home-9 3.2): the two buttons
     side by side, a thumb's height each (law H12), and under them the
     reason line or the summary - a sentence squeezed beside two buttons
     would wrap into a column of single words. */
  .start-bar-row { gap: var(--s2); }
  .start-draw { flex: 1 1 0; order: 1; }
  .start-bar .start-settings {
    flex: 1 1 0; order: 2; margin-left: 0; justify-content: center;
  }
  .start-bar .start-draw, .start-bar .start-settings {
    min-height: calc(var(--tap) + var(--s1));
  }
  .start-bar-row > .start-bar-reason,
  .start-bar-row > .start-settings-summary { order: 3; flex-basis: 100%; }
}


/* THE FEATURE GRID (owner, 14.09.2026): one small drawing per feature
   the engine dimensions, with the trade word and its one line. The
   drawings use the icon's own three tones plus the accent for the cut
   the feature makes, so a reader who has seen the start page's picture
   is looking at the same timber. */
.feat-group-name {
  margin: var(--rhythm-between) 0 var(--rhythm-within);
  font-weight: 650; color: var(--ink-soft); font-size: 0.9rem;
}
.feat-grid {
  list-style: none; margin: 0; padding: 0;
  display: grid; gap: var(--s3);
  grid-template-columns: repeat(auto-fill, minmax(11rem, 1fr));
}
.feat-cell {
  display: flex; align-items: center; gap: var(--s2);
  margin: 0;
}
.feat-icon { flex: none; width: 4rem; height: auto; }
.feat-name { font-weight: 650; font-size: 0.9rem; }
.feat-detail { color: var(--ink-faint); font-size: 0.85rem; }
.feat-grid-refused {
  grid-template-columns: 1fr;
  margin-top: var(--rhythm-between);
  padding-top: var(--s4);
  border-top: 1px solid var(--line);
}
/* the drawings' own tones: the timber in the page's ink, the cut the
   feature makes in the accent, so the feature is what the eye finds. The
   drawings are MADE from solids by dev/pictograms/make_pictograms.py
   (C.48), which reads these rules to write the same tones into each file;
   the areas carry no stroke, the visible edges are one path of their own */
.feat-icon .face-top { fill: color-mix(in srgb, var(--ink-soft) 14%, var(--paper)); }
.feat-icon .face-front { fill: color-mix(in srgb, var(--ink-soft) 30%, var(--paper)); }
.feat-icon .face-right { fill: color-mix(in srgb, var(--ink-soft) 46%, var(--paper)); }
.feat-icon .feat { fill: color-mix(in srgb, var(--accent) 38%, var(--paper)); }
.feat-icon .feat-deep { fill: color-mix(in srgb, var(--accent) 66%, var(--paper)); }
.feat-icon .pic-edge { stroke: color-mix(in srgb, var(--ink) 45%, var(--ink-soft)); }
.feat-icon .feat-cross { stroke: var(--bad); stroke-width: 2.4; }

/* ...and the save button pulses while a control differs from what was
   last saved, the same keyframes the Plankopf stage's own save uses —
   one animation, so the two places cannot pulse differently. */
.start-pop-save.is-dirty {
  animation: save-pulse 1.4s ease-in-out infinite;
  box-shadow: 0 0 0 0 rgba(37, 99, 168, 0.55);
}

/* THE PROXIMITY LAW ON A FORM (round 8, item 8 — the owner's screenshot
   of 03.09.2026).

   The row gap is the BETWEEN token: one control group to the next. The
   help line that follows a control is pulled back up to the WITHIN
   token, so it reads as belonging to the control above it and not as
   floating equidistant between that control and the next — which is
   exactly what "Off on this page." was doing, and it was arithmetic
   rather than carelessness: as a grid item the help line inherited this
   grid's row gap AND added a top margin of its own, so the distance
   above it was LARGER than the distance below.

   THE CURE IS STRUCTURAL AND NOT ARITHMETIC. The first attempt pulled
   the help line back up with a negative top margin derived from the two
   tokens — and it changed almost nothing on the screen, because a grid
   item's negative margin shrinks its own row rather than moving it
   within one, so everything below simply came up with it. The right
   answer was the one proximity itself points at: an explanation that
   belongs to a control BELONGS IN THE SAME BOX as that control. A
   `.setting` is that box. Its own gap is the within-token, the grid's
   row gap between boxes is the between-token, and the two distances are
   now different distances rather than one distance with a correction on
   it. Nothing has to be derived, and nothing can drift. */
.field-grid { display: grid; gap: var(--rhythm-between); }
.setting { display: grid; gap: var(--rhythm-within); }
@media (min-width: 34rem) {
  .field-grid { grid-template-columns: 1fr 1fr; }
  .field-grid .span-2 { grid-column: 1 / -1; }
}

/* A field row is a <label> where the control is one the label can point
   at, and a <div> where it is not. The colour picker is the second kind:
   it is a custom element whose real control and real caption both live
   in its own shadow root, so wrapping it in a <label> would point that
   label at nothing and print the caption a second time. Same layout,
   same measure, either way. */
/* A field is a box of its own for the same reason a .setting is: the
   caption, the control and the help line belong together, so the gap
   inside it is the within-token and the gap to the next field is the
   grid's own (round 8, items 8 and 10). */
label.field, div.field {
  display: grid; gap: var(--rhythm-within); font-size: 0.9rem;
}
label.field > span, div.field > span {
  color: var(--ink-soft); font-weight: 600;
}

/* #174 (owner QA, F-A): the job's own identity — project and customer,
   printed in the title block of every sheet. They are a first-class
   block on the upload and redraw forms now, ahead of the collapsed
   technical settings, so the block wears the same heading the view-set
   and paper controls wear rather than reading as one more switch. Same
   bottom margin as .viewset-toggle, so the first-class tier keeps one
   rhythm down the form. */
.titleblock-fields { margin: 0 0 var(--s5); }
.titleblock-heading {
  margin: 0;
  color: var(--ink-soft); font-weight: 600; font-size: 0.9rem;
}

/* C.58g: a number or search field in a kit form wears the same box. The
   site rule never named the two types, so the operator's invite, grant,
   entry-link and search fields stood as bare browser boxes beside styled
   selects (seen in the page golden admin-invite-en-dark). Scoped to the
   kit's field group, which the jobs list's search stands in since C.58h;
   the phone finder's box is the job page's own (job.html). */
input[type="text"], input[type="password"], input[type="email"],
.kit-form-fields input[type="number"], .kit-form-fields input[type="search"],
select, textarea {
  font: inherit;
  min-height: var(--tap);
  padding: var(--s2) var(--s3);
  color: var(--ink);
  background: var(--panel);
  border: 1px solid var(--line-strong);
  border-radius: var(--radius-sm);
  width: 100%;
}
input:hover, select:hover, textarea:hover { border-color: var(--accent); }
textarea { resize: vertical; line-height: 1.5; }

.check {
  display: flex; align-items: center; gap: var(--s3);
  font-size: 0.9rem; font-weight: 600;
  color: var(--ink-soft);
}
/* THE 44 PX HIT TARGET IS A TOUCH PROMISE, so it is kept where touch is
   (round 8, item 8). It used to stand unconditionally, and on a mouse
   screen that left about eleven pixels of empty box under every
   checkbox — which is invisible to the reader and which diluted the
   very proximity the owner asked for: the help line sat --rhythm-within
   from the control's BOX and eleven pixels further from its INK, on
   both sides, flattening a four-to-one box ratio into something the eye
   read as level. A fine pointer needs no 44 px target. */
@media (hover: none), (pointer: coarse) {
  .check { min-height: var(--tap); }
}
.check input { width: 1.35rem; height: 1.35rem; accent-color: var(--accent); }

/* The view-set segmented control (VC3k): a first-class, always-visible
   choice, styled as two tappable buttons rather than a bare dropdown.
   Plain radios under the hood, so it needs no script and degrades to a
   readable pair of ticked/unticked rows if a browser lacks :has(). */
.viewset-option {
  display: flex; align-items: center; gap: var(--s3);
  min-height: var(--tap);
  padding: var(--s3) var(--s4);
  border: 1px solid var(--line-strong);
  border-radius: var(--radius-sm);
  background: var(--panel);
  font-size: 0.9rem; font-weight: 600; color: var(--ink-soft);
  cursor: pointer;
}
.viewset-option input {
  width: 1.1rem; height: 1.1rem; accent-color: var(--accent); flex: none;
}
.viewset-option:has(input:checked) {
  border-color: var(--accent);
  background: var(--accent-soft);
  color: var(--ink);
}

/* The paper control (VC3p), first-class beside the view-set toggle and
   wearing its clothes — same label, same option chip, same checked
   state — because it is the same kind of decision and a visitor should
   not have to learn two controls. It differs in one way only: it has
   six answers rather than two, so the options flow into as many columns
   as fit instead of a fixed pair, and the first one — the automatic
   resolution, which is the page's own default — takes the whole first
   row so it reads as the recommendation it is. */
.paper-toggle { display: grid; gap: var(--s2); margin: 0 0 var(--s5); }
.paper-options {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(5.5rem, 1fr));
  gap: var(--s3);
}
.paper-options .paper-auto { grid-column: 1 / -1; }

/* The family toggle (VC3q, V28): the two named groups sit on their own
   row above the sizes, wearing the same option chip, so choosing ISO or
   US is one click in the same clothes as everything else here. */
.paper-family {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(11rem, 1fr));
  gap: var(--s3);
}
/* A sub-heading inside the size list, one per family, so a size reads
   under the group it belongs to (VC3q, V28). It spans the whole row and
   is a plain caption, never a chip. */
.paper-group-heading {
  grid-column: 1 / -1;
  margin: var(--s2) 0 0;
  font-weight: 600;
  color: var(--ink);
}

/* The line under the band that points a refused reader at that control
   (VC3p). It is rendered only for a job that named its own paper, so it
   never argues with a refusal the service could not have cured. */
.paper-hint { margin: var(--s3) 0 0; }

/* The refusal tile's own button (VC3p, owner extension). It sits under
   the refusal text inside the tile's frame, and its button is allowed
   to wrap onto two lines: the label is a whole sentence and a tile is
   narrow, and a truncated instruction is worse than a tall one. */
.tile .refit { margin-top: var(--s3); }
.tile .refit button {
  font-size: 0.8rem;
  padding: var(--s2) var(--s3);
  min-height: var(--tap);
  white-space: normal;
  line-height: 1.2;
}

.dropzone {
  display: grid;
  gap: var(--s2);
  place-items: center;
  text-align: center;
  padding: var(--s6) var(--s4);
  border: 2px dashed var(--line-strong);
  border-radius: var(--radius);
  background: var(--panel-sunken);
  cursor: pointer;
  min-height: 8rem;
}
.dropzone:hover, .dropzone:focus-within { border-color: var(--accent); }
.dropzone.dragging { border-color: var(--accent); background: var(--accent-soft); }

/* Fix #3 (W-uipolish2): the sticky bottom Draw button is never a dead
   end on an empty tap — abbundo.js scrolls back up to this drop zone,
   moves focus into it and adds one of these two classes to make sure it
   is actually seen, not merely reachable. `.attn` is three strong
   accent pulses (owner: "real visual attraction, not a subtle hint");
   `.dismiss`-free by design, `animationend` below just tidies the class
   so a second empty tap can restart it. `.attn-still` is the
   prefers-reduced-motion answer: one steady highlight, no motion,
   removed by the same script after a few seconds or the moment a file
   is actually chosen. Owner ruling: a strong cue, not a subtle one. */
@keyframes dropzone-attn {
  0%, 100% { border-color: var(--line-strong); box-shadow: 0 0 0 0 transparent; }
  16%, 50%, 84% {
    border-color: var(--accent);
    box-shadow: 0 0 0 5px var(--accent-soft), 0 0 20px 3px var(--accent);
  }
  33%, 67% { border-color: var(--line-strong); box-shadow: 0 0 0 0 transparent; }
}
.dropzone.attn { animation: dropzone-attn 1.8s ease-in-out 1; }
.dropzone.attn-still {
  border-color: var(--accent);
  box-shadow: 0 0 0 5px var(--accent-soft), 0 0 20px 3px var(--accent);
}
.dropzone strong { font-size: 1.05rem; }
.dropzone .chosen { color: var(--ink-soft); font-size: 0.9rem; }
/* the zone's words are labels of the one file input, and take no box of
   their own: their contents are the zone's own grid items */
.dropzone-pick { display: contents; }
/* "add more files" OR "Draw", on one line, one above the other where they
   do not fit (a phone); the "or" stands between them either way */
.dropzone { container: dropzone / inline-size; }
.dropzone-choices {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: center;
  gap: var(--s2) var(--s3);
}
.dropzone-or[hidden],
.kit-draw-mirror[hidden] { display: none; }
/* C.226: 24rem (it was 30rem) so the hero's text column keeps "Datei ins
   Feld ziehen oder [Dateien auswählen]" and the ready line on one row */
@container dropzone (max-width: 24rem) {
  .dropzone-choices { flex-direction: column; }
}
/* C.226 (home-9 point 4, law H5): the formats line, the zone's last line -
   every format the register offers, and the upload help one press away */
.dropzone-formats {
  margin: 0;
  font-size: var(--fs-small);
  color: var(--ink-soft);
}
/* before a file the zone says only what to do; the "chosen" line is the
   ready state's (the tick and the count) */
.dropzone:not(.ready) .chosen { display: none; }
/* the Draw mirror wears the sticky button's own states: the ring while
   files are held and the answer to every arrival (drawn from its classes,
   which kit/drawmirror.js copies) */
.kit-draw-mirror.ready {
  box-shadow: 0 0 0 3px var(--accent-soft), 0 0 16px 2px var(--accent);
}
.dropzone input[type="file"] {
  /* the phone's own picker, reachable by tap and by keyboard */
  position: absolute; opacity: 0; width: 1px; height: 1px;
}
/* Fix #3 (W-uipolish), C.226: a phone has no drag-and-drop, so the drag
   words stand down on a touch device with no hover (not merely a narrow
   window) and the picker's button is the zone: full width, a thumb's
   height (home-9 3.2, law H12), with no script involved either way. */
@media (hover: none) and (pointer: coarse) {
  .dropzone-hint-pointer { display: none; }
  .dropzone-choices { justify-self: stretch; }
  .dropzone .dropzone-choose {
    flex: 1 1 auto;
    width: 100%;
    min-height: calc(var(--tap) + var(--s2));
  }
}

/* #161/W-uipolish3: the loaded state, added by abbundo.js's
   `updateReady()` the moment at least one file sits in the input — a
   JS-off reader never sees `.ready` at all and keeps the ordinary
   drop/tap hint and the plain "chosen" line, which is why the label
   below defaults to hidden rather than being toggled by an inline
   style. `.dropzone-ready-label` replaces BOTH hint lines at once (the
   two-class selector outranks the (hover: none) swap above regardless
   of source order), the zone's own border and background pick up the
   same accent :root already uses for a finished state elsewhere
   (`--good`, the pill a done job wears), and the chosen line grows a
   check mark and the same colour so the whole zone reads as loaded, not
   just the small text under it. */
.dropzone-ready-label { display: none; }

/* Round 8's second action row under the zone is retired (owner,
   13.09.2026 — round C.23). It put Draw "where the eye already is"
   because the page's own Draw button was far below the fold; the sticky
   action bar does that at every scroll position and at every width, and
   two rows offering one act is the shape the row itself warned about.
   Its rules are gone with it rather than left to rot. */

/* THE HELD LIST (round 9, item 16). One row per file the page is really
   holding, each with a cross that takes that one file out. The cross is
   drawn, not written — its accessible name comes from the catalogue
   through `data-remove` on the list, because a multiplication sign is
   not a word and a screen reader must still be told what the button
   does.

   `[hidden]` is honoured on both of these for exactly the reason the
   action row above honours it: `display: grid`/`flex` on the element
   itself beats the browser's own `[hidden] { display: none }`, and a
   JS-off reader would then meet an empty box under the zone. */
.dropzone-files {
  display: grid;
  gap: var(--s1);
  margin: var(--rhythm-within) 0 0;
  padding: 0;
  list-style: none;
}
.dropzone-files[hidden] { display: none; }
.dropzone-file {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--s2);
  padding: var(--s1) var(--s2);
  border: 1px solid var(--line);
  border-radius: var(--radius-sm);
  background: var(--panel);
  font-size: 0.9rem;
}
.dropzone-file-name { overflow-wrap: anywhere; }
.dropzone-file-remove {
  flex: none;
  min-width: var(--tap);
  min-height: var(--tap);
  padding: 0;
  border: 0;
  border-radius: var(--radius-sm);
  background: none;
  color: var(--ink-soft);
  font-size: 1.1rem;
  line-height: 1;
  cursor: pointer;
}
.dropzone-file-remove:hover, .dropzone-file-remove:focus-visible {
  color: var(--bad);
}

/* The quiet note: a repeat was left out. It is not a refusal — it wears
   the ordinary soft ink, never the red the field message below uses. */
.dropzone-note {
  margin: var(--s1) 0 0;
  color: var(--ink-soft);
  font-size: 0.9rem;
}
.dropzone-note[hidden] { display: none; }

.dropzone.ready {
  border-style: solid;
  border-color: var(--good);
  background: var(--good-soft);
}
.dropzone.ready .dropzone-hint-pointer { display: none; }
.dropzone.ready .dropzone-ready-label { display: block; color: var(--good); }
.dropzone.ready .chosen { color: var(--good); font-weight: 600; }
/* the ready tick (C.58j): the icon set's own, shown once files are ready */
.chosen-mark { display: none; color: var(--good); }
.dropzone.ready .chosen-mark { display: inline-block; }

/* THE PICKER'S WORD (round 9, item 16). Both words sit in the markup and
   CSS picks one, exactly as the pointer/touch hint swap above does — no
   script writes a word here any more.

   The reason is honesty rather than tidiness. `.ready` is a class only
   abbundo.js ever adds, so with JavaScript blocked this button says
   "Choose files" for as long as the page exists — which is the truth
   there, because the input then replaces its files on every pick the way
   a file input always has. `.noaccum` is the same truth for a browser
   whose DataTransfer will not build a FileList: the page cannot hold a
   list there either, so the loaded word is withheld again. */
.choose-word-loaded { display: none; }
.dropzone.ready .choose-word-empty { display: none; }
.dropzone.ready .choose-word-loaded { display: inline; }
.dropzone.ready.noaccum .choose-word-empty { display: inline; }
.dropzone.ready.noaccum .choose-word-loaded { display: none; }

/* THE UPLOAD UNDER WAY (C.231, owner complaint 29.10.2026). The zone
   carries `uploading` INSTEAD of `ready` (kit/entrysend.js through the
   zone's one state function), so nothing of the ready state - its
   heading, its count with the tick, the Draw mirror - stands beside the
   upload's own words: one state at a time. The heading, the bar and the
   byte line stand at the top of the box where the ready heading stood;
   the picker stays where it is, greyed, with the cancel beside it and
   the reason line under both (law 23). The bar is the site's one
   determinate bar (`.progress-track`); its fill never loops, and with
   reduced motion it loses its width transition by the bar's own rule. */
.dropzone-upload[hidden], .dropzone-upload-reason[hidden],
.dropzone-cancel[hidden] { display: none; }
.dropzone-upload {
  display: grid;
  gap: var(--s2);
  justify-items: center;
  width: 100%;
  max-width: 30rem;
}
.dropzone-upload-progress {
  display: grid;
  gap: var(--s1);
  width: 100%;
}
.dropzone-upload-track { width: 100%; }
.dropzone-upload-line {
  font-size: 0.9rem;
  font-variant-numeric: tabular-nums;
  color: var(--ink-soft);
}
.dropzone-upload-reason {
  margin: 0;
  font-size: 0.9rem;
  color: var(--ink-soft);
}
.dropzone.uploading {
  border-style: solid;
  border-color: var(--accent);
  cursor: default;
}
.dropzone.uploading .dropzone-hint-pointer,
.dropzone.uploading .dropzone-hint-touch,
.dropzone.uploading .dropzone-ready-label,
.dropzone.uploading .chosen,
.dropzone.uploading .chosen-mark { display: none; }
/* the picker keeps its loaded word, greyed while nothing may be added */
.dropzone.uploading .choose-word-empty { display: none; }
.dropzone.uploading .choose-word-loaded { display: inline; }
.dropzone.uploading.noaccum .choose-word-empty { display: inline; }
.dropzone.uploading.noaccum .choose-word-loaded { display: none; }
.dropzone.uploading .dropzone-choices .button-ghost {
  opacity: 0.55;
  cursor: not-allowed;
}
.dropzone-file-remove[disabled] { opacity: 0.45; cursor: not-allowed; }

/* The zone wears the refusal too, not only the sentence under it — the
   same pairing `.field-invalid` makes everywhere else on the site, said
   here on the label because the input inside it is the visually hidden
   one and would show nothing of its own. */
.dropzone.field-invalid { border-style: solid; border-color: var(--bad); }

/* The other half of the same cue (#161): once the zone is loaded, the
   reader's next tap belongs on the Draw button, so the emphasis moves
   there too — the same accent the drop zone's own `.attn` pulse uses,
   held steady rather than pulsing (a loaded, ready-to-submit state is
   not the same signal as "you tapped Draw with nothing chosen yet"). */
#submitbutton.ready {
  box-shadow: 0 0 0 3px var(--accent-soft), 0 0 16px 2px var(--accent);
}

/* ...and it ANSWERS EVERY ARRIVAL (owner, 14.09.2026, 15:55): "the
   Zeichnen button shall very obviously animate every time a file is
   uploaded". The steady ring above says "loaded"; this says "something
   just landed", which is a different message and needs a different
   strength — it is the save pulse's family (a ring thrown off the
   button's own accent) but bigger, with the button growing under it,
   and it runs twice and stops rather than breathing for ever. A signal
   that never ends stops being a signal, and the state it leaves behind
   is the ready ring, which is the truth from then on.

   `is-fresh` is added by abbundo.js on every arrival and taken off two
   seconds later; the animation is rewound on the way in, so the second
   file in a row is as loud as the first. */
.kit-draw-mirror.is-fresh,
#submitbutton.is-fresh {
  animation: draw-arrived 0.85s ease-out 2;
  background: var(--accent);
  box-shadow: 0 0 0 4px var(--accent-soft), 0 0 22px 4px var(--accent);
}
@keyframes draw-arrived {
  0% { transform: scale(1); box-shadow: 0 0 0 0 rgb(29 78 137 / 75%); }
  40% { transform: scale(1.07);
        box-shadow: 0 0 0 0.85rem rgb(29 78 137 / 0%); }
  70% { transform: scale(0.99); box-shadow: 0 0 0 0 rgb(29 78 137 / 0%); }
  100% { transform: scale(1); box-shadow: 0 0 0 0 rgb(29 78 137 / 0%); }
}

/* -- the stamp editor (design 2) ---------------------------------- */

.stamp-card { position: relative; }
.stamp-state { margin: 0; }

/* The drawing-font default (#130): the pickers stack, and the live
   before/after preview lays its two sample sheets side by side on a wide
   screen and stacks them on a narrow one. The images are fenced by width
   so a landscape sheet never spills the card, and never cropped (V27). */
.font-card .field { margin: 0; display: grid; gap: var(--s1); }
.font-card select { max-width: 22rem; }
.font-preview {
  display: flex;
  flex-wrap: wrap;
  gap: var(--s4);
  /* C.145b: the page-scale switch that stood between the selects and
     the two pictures is gone; the pictures keep their distance */
  margin-top: var(--s4);
}
.font-preview figure {
  margin: 0;
  flex: 1 1 14rem;
  min-width: 12rem;
}
.font-preview figcaption {
  color: var(--ink-soft);
  font-weight: 600;
  font-size: 0.9rem;
  margin-bottom: var(--s1);
}
.font-preview img {
  display: block;
  width: 100%;
  height: auto;
  border: 1px solid var(--line);
  background: #fff;
}
/* #175 (owner live-QA finding): the default view is a MAGNIFIED CROP of
   the sheet, not the whole thing shrunk — a font/size difference lives
   in the dimension text and is invisible at whole-sheet-thumbnail size.
   A plain <button> with the full preview PNG as its background image,
   scaled up and shifted so the SAME fraction of the sheet shows in both
   panes (identical background-size/position on both, and both PNGs are
   the same pixel dimensions — one producer, one paper, one scale — so
   percentage positioning lands on the same drawn content either side).
   No cropping on the server: this is the existing preview PNG, viewed
   through a smaller, zoomed window. Also the (only) way to open the
   shared lightbox (#174, stamp.js) at native size for reading it
   properly. */
.font-preview-detail {
  display: block; width: 100%; height: 9rem;
  margin: 0 0 var(--s1); padding: 0;
  border: 1px solid var(--line); border-radius: var(--radius-sm);
  background-color: #fff;
  background-repeat: no-repeat;
  background-size: 260%;
  background-position: 50% 62%;
  cursor: zoom-in;
}
.font-preview-caption {
  margin: 0 0 var(--s2); font-size: 0.78rem;
}
/* The small whole-sheet thumbnail kept for orientation — what the
   magnified crop above is a piece of. */
.font-preview-thumb { opacity: 0.85; }

/* Two panes on a wide screen: the form, and beside it a preview that
   stays in view while the form is scrolled — it is a real render by the
   core's own stamp engine, so it earns the room. On a narrow screen the
   preview comes FIRST, and — for the editor (SV-stampeditor) — it is
   sticky-pinned to the top so live edits stay in view while the form
   scrolls beneath it. This REFINES W-stamplayout (#98), which made the
   mobile preview non-sticky; the editor reverses that but keeps the
   pinned preview COMPACT so the form still has room. */
.stamp-editor { display: grid; gap: var(--s5); }
.stamp-editor .stamp-preview {
  order: 1;
  margin: 0;
  position: sticky;
  top: calc(var(--header-offset) + var(--s2));
  z-index: 3;
  /* opaque, so the scrolling form does not show through the pinned
     preview, with a hair of air below it. #174: the image inside is now
     WIDTH-constrained to this column (see below), so nothing here spills
     past the column or the card's edge and no sideways scroll is needed
     to see the whole stamp — the earlier height-first sizing let a wide
     landscape stamp block run past the column and get clipped at the
     card/viewport edge before a reader ever noticed there was more to
     scroll to. */
  background: var(--panel);
  padding-bottom: var(--s2);
}
.stamp-editor .stamp-form { order: 2; min-width: 0; }

.stamp-preview img {
  border: 1px solid var(--line-strong);
  border-radius: var(--radius-sm);
  background: var(--panel);
}
/* #174: the preview is now also a real button (stamp.js), so it answers
   Tab/Enter/Space; everything the base button rule sets is given back so
   it still reads as a picture and not as one of the page's accent
   buttons. */
.stamp-preview-open {
  display: block; padding: 0; margin: 0; border: 0; background: none;
  cursor: zoom-in; text-align: left;
}
.stamp-preview-open img { display: block; }
/* #174 (owner live-QA finding): the whole stamp must always be visible,
   never cropped at an edge. The preview is already cropped tight to the
   stamp block server-side (render_stamp_png), never the whole sheet —
   this only has to fit THAT crop inside the column without cutting it
   further. max-width:100% is the binding constraint on every screen (the
   column's own width is what the reader can actually see); max-height
   keeps a very tall configured stamp from overrunning the viewport
   either. Both together, with height/width both auto, make the browser
   scale the image down by whichever limit binds first, aspect ratio
   kept, full stamp always in view — the standard "contain" behaviour for
   a plain image with no CSS layout engine needed. The higher
   STAMP_PREVIEW_PX_PER_MM (service/preview.py) keeps a shrunk block
   crisp rather than upscaling a blur; click-to-enlarge (below) is the
   reader's way to read fine print at full size. */
.stamp-editor .stamp-preview img {
  display: block;
  width: auto;
  height: auto;
  max-width: 100%;
  max-height: 34vh;
  cursor: zoom-in;
}
.stamp-preview figcaption { margin-top: var(--s2); }

/* On a phone the site header is static and scrolls away (mobile-layout),
   so the pinned preview sits against the very top rather than below a
   header that is no longer there. */
@media (max-width: 47.99rem) {
  .stamp-editor .stamp-preview { top: var(--s2); }
}

/* Two panes only once there is genuine room for both: a form that keeps
   a usable minimum width AND the preview beside it. The form floor
   (22rem) stops the column collapsing below its content — the old
   minmax(0, 1fr) let a wide input spill rightward under the sticky
   preview, which read as the preview overlapping the controls
   (W-stamplayout). The breakpoint is lifted from 60rem to 64rem so the
   split engages only when the card's inner width clears both mins with
   room to spare; every narrower viewport keeps the clean stacked layout
   (preview first, form under, nothing sticky) instead of the squished
   in-between. */
@media (min-width: 64rem) {
  .stamp-editor {
    grid-template-columns: minmax(22rem, 1fr) minmax(0, 22rem);
    align-items: start;
  }
  .stamp-editor .stamp-form { order: 1; }
  /* Item 2 (SV-stampeditor): keep the preview sticky (inherited above)
     but CONTAINED within the white card — no crossing its edge. The
     preview column is shrink-safe (minmax(0, 22rem)) so the two panes
     plus the gap never exceed the card's padded content box and the
     preview cannot spill across the card's right edge; a max-height with
     its own scroll keeps a tall configured stamp from overhanging the
     card's bottom edge. */
  .stamp-editor .stamp-preview {
    order: 2;
    top: calc(var(--header-offset) + var(--s3));
    max-height: calc(100vh - var(--header-offset) - var(--s6));
    overflow: auto;
    padding-bottom: 0;
  }
  /* #174: the wide-screen column has real vertical room (up to the
     viewport's own height, less the header and a margin), so the
     max-height ceiling can be generous here — but max-width:100% (the
     narrow-screen rule, inherited) is still what actually binds for a
     wide landscape stamp, exactly as it does on mobile: the whole block
     fits the column, never spills into the form or past the card's
     edge, and never needs a sideways scroll to be seen whole. */
  .stamp-editor .stamp-preview img {
    max-height: calc(100vh - var(--header-offset) - var(--s6));
  }
}

.stamp-form > * + * { margin-top: var(--s5); }

.stamp-group {
  border: 1px solid var(--line);
  border-radius: var(--radius-sm);
  padding: var(--s4);
  margin: 0;
}
.stamp-group > legend { font-weight: 650; color: var(--ink); padding: 0 var(--s2); }
.stamp-group > summary { font-weight: 650; color: var(--ink); cursor: pointer; }
.stamp-group > * + * { margin-top: var(--s4); }
/* C.131: the concierge editor's parts are settings sections (groups of
   the law); their controls keep the fieldsets' step between them, and the
   help line keeps the section's own 8 px under its controls */
.stamp-editor .settings-section > * + *:not([data-help]) { margin-top: var(--s4); }

/* label + alignment toggle + height on ONE line, wrapping on narrow. */
.stamp-inline {
  display: flex; flex-wrap: wrap; align-items: flex-end; gap: var(--s3);
}
.stamp-inline .stamp-height { flex: 0 1 8rem; }
.stamp-height > span { font-size: 0.8rem; }

/* one custom row: the text pair over its inline controls. */
.stamp-rows { display: grid; gap: var(--s3); }
.stamp-row {
  border: 1px solid var(--line);
  border-radius: var(--radius-sm);
  padding: var(--s3);
  background: var(--panel-sunken);
  display: grid; gap: var(--s3);
}
.stamp-row-text { display: grid; gap: var(--s3); }
@media (min-width: 34rem) {
  .stamp-row-text { grid-template-columns: 1fr 1fr; }
}
.stamp-row-controls { align-items: center; }
.stamp-row-remove {
  margin-left: auto; padding: var(--s2) var(--s3);
}

/* C.145b: the title block's cells as one table - name, alignment icons,
   height figure; the unit stands once in the column head */
.stamp-cells-table { width: 100%; border-collapse: collapse; }
.stamp-cells-table th, .stamp-cells-table td {
  padding: var(--s2) var(--s3) var(--s2) 0;
  text-align: left; vertical-align: middle;
}
.stamp-cells-table thead th { font-size: 0.85rem; color: var(--ink-soft); font-weight: 600; }
.stamp-cell { border-top: 1px solid var(--line); }
.stamp-cell-name { font-weight: 600; color: var(--ink-soft); font-size: 0.9rem; }
.stamp-cells-table .kit-choice { margin: 0; }
/* the table fits a 390 px popup without a sideways scroll: the heads
   wrap and the height select is as wide as its figure */
.stamp-cells-table thead th { white-space: normal; letter-spacing: 0; }
.stamp-cells-table select { width: auto; min-width: 4.5rem; max-width: 100%; }
@media (max-width: 34rem) {
  .stamp-cells-table th, .stamp-cells-table td { padding-right: var(--s1); }
  .stamp-cells-table thead th { font-size: 0.7rem; }
  .stamp-cell-name { font-size: 0.8rem; }
}

/* the sticky save bar of the form pane, reachable from any group. */
.stamp-save-bar {
  position: sticky; bottom: 0;
  margin-top: var(--s4);
  padding-top: var(--s3);
  background: var(--panel);
  border-top: 1px solid var(--line);
}

.stamp-logo-drop { min-height: 6rem; }
.stamp-concierge {
  border-left: 3px solid var(--accent);
  padding-left: var(--s3);
  color: var(--ink-soft);
}


/* An explanation, wherever it stands. Its top margin is the WITHIN
   token — it belongs to the thing above it — and it states no bottom
   margin at all, because in ordinary flow the distance to what comes
   next is that next thing's own business and every heading, paragraph
   and list on this site already carries its own top margin from the
   same scale. Inside .field-grid the grid's row gap does that job
   instead; see the pull-back rule above (round 8, items 8 and 10). */
.help {
  color: var(--ink-faint);
  font-size: 0.85rem;
  margin: var(--rhythm-within) 0 0;
}

button, .button {
  font: inherit; font-weight: 650;
  min-height: var(--tap);
  padding: var(--s2) var(--s5);
  border-radius: var(--radius-sm);
  border: 1px solid transparent;
  background: var(--accent);
  color: var(--accent-ink);
  cursor: pointer;
  text-decoration: none;
  display: inline-flex; align-items: center; justify-content: center;
  gap: var(--s2);
}
button:hover, .button:hover { filter: brightness(1.08); }
button[disabled] { opacity: 0.55; cursor: progress; }

/* QA11 item 13: the little turning ring a slow action's button shows
   the instant it is pressed, beside the working sentence busywork.js
   swaps in. A bare span the script builds — no glyph, no image — so it
   inherits the button's own ink. A reader who asked their system for
   less motion gets the ring without the spin (busywork.js adds the
   -still class), so the "it is working" mark is still there, just not
   moving. */
.button-spinner {
  display: inline-block;
  width: 0.85em;
  height: 0.85em;
  margin-inline-end: var(--s2);
  vertical-align: -0.1em;
  border: 2px solid currentColor;
  border-top-color: transparent;
  border-radius: 50%;
  animation: button-spin 0.7s linear infinite;
}
.button-spinner-still { animation: none; }
@media (prefers-reduced-motion: reduce) {
  .button-spinner { animation: none; }
}
@keyframes button-spin {
  to { transform: rotate(360deg); }
}

.button-ghost {
  background: transparent;
  color: var(--accent);
  border-color: var(--line-strong);
}
.button-ghost:hover { background: var(--accent-soft); filter: none; }

/* "Forget the key" (_key_forget.html): a small outlined button that
   stands in the line telling the reader his browser keeps a key. */
.key-forget { min-height: 0; padding: var(--s1) var(--s3); font-size: 0.85rem; margin-inline-start: var(--s2); }

/* QA11 item 22: the job-page stop control is a REAL outlined button
   (base .button), never a bare .button-ghost rendering as an underlined
   link the owner could not find for two days.

   C.78, PAGE_DESIGN_LAWS section 7 (owner 22.09.2026): a DESTRUCTIVE
   action is outlined red and confirmed in place. This is the one class
   that says so, for every destructive control on the site: the outline
   and the word in the red token, the face left clear, so it reads as a
   consequence to weigh and never as a fault already happened (a filled
   red face stays .button-danger's, for the operator's irreversible
   deletions). It supersedes the #172 reading that kept the stop control
   grey. */
.button-destructive {
  background: transparent;
  color: var(--bad);
  border-color: var(--bad);
}
.button-destructive:hover { background: var(--panel-sunken); filter: none; }
.job-cancel-button { font-weight: 700; }

.submit-row {
  display: flex; flex-wrap: wrap; align-items: center;
  gap: var(--s4); margin-top: var(--s5);
}
/* the Plankopf stage (owner 13.09.): its two buttons stick to the foot
   of the window while the long form scrolls, and the save button pulses
   while a field differs from what is saved (stampwidget.js sets it) */
.stamp-widget .submit-row {
  position: sticky; bottom: 0; z-index: 2; margin-top: var(--s4);
  padding: var(--s3) 0; background: var(--paper); border-top: 1px solid var(--line);
}
.stamp-widget .submit-row button[type="submit"].is-dirty,
.stamp-foot-part button[type="submit"].is-dirty {
  animation: save-pulse 1.4s ease-in-out infinite;
  box-shadow: 0 0 0 0 rgba(37, 99, 168, 0.55);
}
@keyframes save-pulse {
  0% { box-shadow: 0 0 0 0 rgba(37, 99, 168, 0.55); }
  70% { box-shadow: 0 0 0 0.6rem rgba(37, 99, 168, 0); }
  100% { box-shadow: 0 0 0 0 rgba(37, 99, 168, 0); }
}

/* -- C.7: the Plankopf stage's live preview, its two-line boxes and its
      popup -------------------------------------------------------- */

/* THE LIVE PREVIEW (owner 12.09.): the block, re-drawn as the reader
   types. It stands at the TOP of the widget and stays in view while the
   long form scrolls under it, because the whole point of it is to be
   looked at while typing — a preview that scrolls away is a picture
   nobody sees change. Its top is the header's own offset on a page and
   zero inside the popup, whose head is its own strip. */
.stamp-live {
  position: sticky;
  top: calc(var(--header-offset) + var(--s2));
  z-index: 3;
  margin: 0;
  background: var(--panel);
  padding-bottom: var(--s2);
}
/* The whole block, never a crop of it: width is what binds on every
   screen and the height ceiling keeps a tall configured block from
   taking the window. Both with height/width auto, so the browser scales
   by whichever limit binds first and the aspect is kept — the same rule
   the account editor's own preview keeps (#174). */
.stamp-live img {
  display: block;
  width: auto; height: auto;
  max-width: 100%; max-height: 30vh;
  border: 1px solid var(--line-strong);
  border-radius: var(--radius-sm);
  background: var(--panel);
}
/* On a phone the site header is static and scrolls away
   (mobile-layout), so the pinned preview sits against the very top
   rather than below a header that is no longer there. */
@media (max-width: 47.99rem) {
  .stamp-live { top: var(--s2); }
  .stamp-live img { max-height: 24vh; }
}
/* THE PINNED PICTURE MUST NOT COVER THE FIELD BEING TYPED INTO (C.45/46
   close). A browser brings a focused field "into view" by the window's
   own edges, which is the top of the area the sticky picture sits over,
   so on a short window — a phone with its keyboard up is the ordinary
   case — the field the reader just tapped could land behind the very
   picture that is meant to show what he is typing.

   Two answers, in the order a screen runs out of room. Every field in
   the widget keeps a scroll margin the size of the picture's own
   ceiling, so a browser scrolling one into view puts it UNDER the
   picture and not behind it. And below the height where a pinned
   picture and a usable form cannot both fit, the picture stops being
   pinned altogether: it scrolls away with the form, which is the honest
   trade when there is no room for both, and it is still one flick
   above the field. */
.stamp-widget :where(input, select, textarea, .settings-value) {
  scroll-margin-top: calc(30vh + var(--s4));
}
@media (max-width: 47.99rem) {
  .stamp-widget :where(input, select, textarea, .settings-value) {
    scroll-margin-top: calc(24vh + var(--s4));
  }
}
@media (max-height: 34rem) {
  .stamp-live { position: static; }
  .stamp-live img { max-height: 18vh; }
  .stamp-widget :where(input, select, textarea, .settings-value) {
    scroll-margin-top: var(--s4);
  }
}

/* A multi-line title-block box, and the line under it that counts its
   lines. The note is a .help like every other explanation on this site.
   C.116: the box carries NO minimum height of its own any more. The
   3.4rem floor stood here for the two-line boxes of C.7 and held a one-
   line Firma two lines high, so the box did not open one line high and
   grow with what is typed (law 17, fields.js); the box's height is the
   field resource's, line by line, up to the seven lines the cell prints. */
/* The limit ends the box's own help line rather than starting a second
   one, so it needs the space between two sentences and nothing else. */
.stamp-lines-note { font-style: italic; margin-inline-start: 0.25em; }

/* The remembered values a TWO-LINE field offers. A textarea cannot
   carry a datalist — HTML allows `list` on an input and on nothing else
   — so stampwidget.js fills this list instead, and it is hidden until
   there is something in it. Chips rather than rows: the list sits
   directly under the box it fills and must not push the next field a
   screen away. */
.stamp-picks {
  list-style: none; margin: var(--rhythm-within) 0 0; padding: 0;
  display: flex; flex-wrap: wrap; gap: var(--s2);
}
.stamp-picks[hidden] { display: none; }
.stamp-pick {
  min-height: auto; padding: var(--s1) var(--s3);
  font-size: 0.82rem; font-weight: 600;
}

/* Inside a popup the sticky bar sticks to the popup's own foot, and the
   preview to its own head. C.58 step 3 and C.58j: every popup with the
   widget is the kit's (the start page's, the account page's and the job
   page's settings popup), whose head is a fixed row above the one
   scrolling body, so the picture sticks to the body's own top edge and
   no title height has to be measured at all. */
.kit-pop-body .stamp-live { top: 0; }
/* C.131: in the popup's pinned foot the title-block form's note and save
   row are the foot's own parts: no bar of their own, the note at the
   foot's left as the kit's note stands */
.kit-pop-foot .stamp-foot-part.submit-row {
  position: static; margin: 0; padding: 0; border: 0; background: none;
  display: flex; flex-wrap: wrap; gap: var(--s3); align-items: center;
}
.kit-pop-foot .stamp-foot-part.settings-footer-note { margin: 0 auto 0 0; }
.kit-pop-foot .stamp-foot-part[hidden] { display: none; }
.kit-pop-body .stamp-widget .submit-row { background: var(--panel); }
/* batch 38: where another row is the popup's foot (the job's C.86
   settings foot), the form's own row stands in the flow under the
   fields' box; two rows stuck to one edge put one over the other */
.stamp-widget .submit-row[data-row-flow] { position: static; }

/* Decision V18's sentence stands beside the button, not in a footnote. */
.honesty {
  flex: 1 1 20rem;
  margin: 0;
  font-size: 0.88rem;
  color: var(--ink-soft);
  border-left: 3px solid var(--line-strong);
  padding-left: var(--s3);
}

/* -- status pills -------------------------------------------------- */

.pill {
  display: inline-flex; align-items: center; gap: var(--s2);
  padding: var(--s1) var(--s3);
  border-radius: 999px;
  font-size: 0.82rem; font-weight: 650;
  background: var(--panel-sunken); color: var(--ink-soft);
  white-space: nowrap;
}
.pill::before {
  content: ""; width: 0.5rem; height: 0.5rem; border-radius: 50%;
  background: currentColor; flex: none;
}
.pill[data-status="done"] { background: var(--good-soft); color: var(--good); }
.pill[data-status="failed"] { background: var(--bad-soft); color: var(--bad); }
.pill[data-status="running"], .pill[data-status="previewing"],
.pill[data-status="writing"], .pill[data-status="previewed"],
.pill[data-status="bundling"] {
  background: var(--accent-soft); color: var(--accent);
}
.pill[data-status="pending"] { background: var(--wait-soft); color: var(--ink-soft); }
/* #242's fourth job state: every preview finished and the files not
   asked for. It is the reader's turn, so it wears the accent the
   other actionable states wear rather than the finished green. */
.pill[data-status="ready"] { background: var(--accent-soft); color: var(--accent); }
/* W-filestage: a file whose own parts are all finished but whose bundle
   (VC3i) failed — the parts' own files are unaffected, so this reads as
   a warning, not the hard failure the part/file "failed" pill means. */
.pill[data-status="bundle_failed"] { background: var(--bad-soft); color: var(--bad); }

/* -- the job page -------------------------------------------------- */

.job-head {
  display: flex; flex-wrap: wrap; align-items: baseline;
  gap: var(--s3) var(--s5); margin-bottom: var(--s4);
}
.job-head h1 { margin: 0; font-size: clamp(1.5rem, 1.2rem + 1.4vw, 2.2rem); }
.job-id { font-family: var(--mono); font-size: 0.85rem; color: var(--ink-faint); }

.meta {
  display: flex; flex-wrap: wrap; gap: var(--s2) var(--s5);
  margin: 0 0 var(--s5); padding: 0; list-style: none;
  color: var(--ink-soft); font-size: 0.9rem;
}
.meta dt { font-weight: 600; color: var(--ink-faint); }
.meta div { display: flex; gap: var(--s2); align-items: baseline; }
.meta dd { margin: 0; }
.job-id-full {
  font-family: var(--mono); font-size: 0.85rem; color: var(--ink-faint);
  word-break: break-all;
  display: flex; flex-wrap: wrap; align-items: center; gap: var(--s2);
}

/* #172: the copy-to-clipboard control. Generic on purpose — any element
   that names a `data-copy-from` gets one — because the job reference is
   not the last identifier on this site a reader will want to take with
   them. It arrives hidden and abbundo.js reveals it only where the
   clipboard API is actually available, so it is never a dead button. */
.copy-button {
  font-size: 0.78rem;
  padding: var(--s1) var(--s2);
  min-height: 0;
}
/* the icon form (C.58j, the guest notice): the kit's copy icon on a
   square that sits in the line of words without widening it */
.copy-button.copy-icon {
  display: inline-flex; align-items: center; justify-content: center;
  padding: 0 var(--s1); vertical-align: middle;
}
.copy-button.copy-icon .kit-icon { width: 1.1em; height: 1.1em; }

table { border-collapse: collapse; width: 100%; font-size: 0.92rem; }
.table-scroll { overflow-x: auto; }
th, td {
  text-align: left; padding: var(--s2) var(--s3);
  border-bottom: 1px solid var(--line);
  vertical-align: top;
}
th { font-size: 0.8rem; text-transform: uppercase; letter-spacing: 0.06em;
     color: var(--ink-faint); }
td.num { font-variant-numeric: tabular-nums; }

/* -- the customer's own job list: cards, not columns ---------------- */
/* (owner QA, 25.08.2026 and 30.08.2026)

   This list was a six-column table that stacked into cards below 64rem.
   Above that width it did what a wide table does: the first column
   carried an unbreakable job reference, the table ran past the window,
   the scroller took over, and the last columns — the deletion day and
   both controls — were, to the person looking at the page, not there.
   The owner reported the deletion column missing for the second time.
   The same shape gave every row the height of its tallest cell, which
   is the large empty area he saw under the other five.

   A table is the wrong instrument for a control surface. So there are
   no columns at any width: one card per job, one layout in every state,
   each fact naming itself. Nothing here reserves room for something
   another row has — a batch waiting to be asked for its files GROWS a
   link, and a row without one is simply shorter.

   The reference is the one unbreakable run on the card; it wraps rather
   than pushing the card out from the inside, and it is small and last
   because it is what a person quotes in an email, never what they read
   the list by. */
.job-rows { list-style: none; padding: 0; margin: 0 0 var(--s5); }
.job-row {
  border: 1px solid var(--line);
  border-radius: var(--radius);
  padding: var(--s4);
  margin-bottom: var(--s4);
}
.job-row-top {
  display: flex; flex-wrap: wrap; align-items: baseline;
  justify-content: space-between; gap: var(--s2) var(--s3);
  margin-bottom: var(--s3);
}
.job-row-name { font-size: 1.05rem; margin: 0; overflow-wrap: anywhere; }
.job-row-facts {
  display: grid; gap: var(--s2) var(--s5);
  grid-template-columns: repeat(auto-fit, minmax(12rem, 1fr));
  margin: 0 0 var(--s3);
}
.job-row-facts > div { margin: 0; }
.job-row-facts dt {
  font-size: 0.8rem; text-transform: uppercase; letter-spacing: 0.06em;
  color: var(--ink-faint);
}
.job-row-facts dd { margin: 0; }
.job-row-life {
  display: flex; flex-wrap: wrap; align-items: center; gap: var(--s3);
  margin-bottom: var(--s3);
}
.job-row-life form {
  display: flex; flex-wrap: wrap; align-items: center; gap: var(--s2);
  margin: 0;
}
.job-row-life .field { margin: 0; }
.job-row-life p { margin: 0; }
.job-row-next { margin: 0 0 var(--s3); }
.job-row-ref {
  margin: 0; font-size: 0.82rem; color: var(--ink-faint);
  display: flex; flex-wrap: wrap; gap: var(--s3);
}
.job-row-ref code { overflow-wrap: anywhere; }

.notice-box {
  padding: var(--s4);
  border: 1px solid var(--line);
  border-left: 3px solid var(--accent);
  border-radius: var(--radius);
  background: var(--panel);
  margin-bottom: var(--s5);
}
/* THE ERROR STYLE, once, for the whole site (round 7b, owner finding of
   02.09.2026: the sign-in error was a white card with a thin red left
   edge and read like any other card).

   A failure is the one message on this site a reader must not be able to
   miss, so it is the one that changes its GROUND and not merely an edge:
   a tinted background, a full border in the error colour, a heavier left
   bar, and a mark of its own. Everything quieter stays quieter — the
   plain `.notice-box` is unchanged, and `.good` keeps its single edge,
   because a site where the confirmation shouts as loudly as the refusal
   has taught its readers to ignore both.

   `--bad-soft` and `--ink` are the palette's own, defined for the light
   and the dark theme alike, so the text keeps its contrast in both
   without a second colour being invented here.

   The mark is DRAWN rather than written: a disc with a bar and a dot
   cut out of it by two background layers. No glyph and no text, so a
   screen reader is told nothing twice — the box already carries
   `role="alert"` where it matters, and the sentence itself is the
   message. */
.notice-box.bad {
  background: var(--bad-soft);
  border-color: var(--bad);
  border-left-width: 4px;
  color: var(--ink);
  display: grid;
  grid-template-columns: auto 1fr;
  gap: var(--s2) var(--s3);
  align-items: start;
}
.notice-box.bad > * { grid-column: 2; }
.notice-box.bad::before {
  content: "";
  grid-column: 1;
  grid-row: 1;
  width: 1.15rem;
  height: 1.15rem;
  margin-top: 0.15rem;
  flex: none;
  border-radius: 50%;
  background-color: var(--bad);
  background-image: linear-gradient(var(--panel), var(--panel)),
                    linear-gradient(var(--panel), var(--panel));
  background-repeat: no-repeat, no-repeat;
  background-size: 2px 0.42rem, 2px 2px;
  background-position: center 0.22rem, center 0.78rem;
}
/* The same voice one line high, for the per-field messages a stopped
   submit writes beside the control it names (round 7b, item 8). Same
   ground, same colour, same mark, no box — a field message sits under
   its own field and must not look like a second card. */
.field-error {
  display: flex;
  align-items: flex-start;
  gap: var(--s2);
  margin: var(--s1) 0 0;
  color: var(--bad);
  font-weight: 600;
}
.field-error::before {
  content: "";
  width: 1rem; height: 1rem; margin-top: 0.15rem; flex: none;
  border-radius: 50%;
  background-color: var(--bad);
  background-image: linear-gradient(var(--panel), var(--panel)),
                    linear-gradient(var(--panel), var(--panel));
  background-repeat: no-repeat, no-repeat;
  background-size: 2px 0.36rem, 2px 2px;
  background-position: center 0.19rem, center 0.68rem;
}
/* ...and the control the message is about wears the same colour, so the
   eye lands on the field and not only on the sentence. */
.field-invalid input, .field-invalid select, .field-invalid textarea,
input.field-invalid, select.field-invalid, textarea.field-invalid {
  border-color: var(--bad);
  outline-color: var(--bad);
}
/* #172: `notice-box good` has been written on the job page's own
   confirmation flash since V32 with no rule behind it, so the one box
   that reports success looked exactly like the plain accent box. Red is
   for what the reader must act on; this is its opposite and now says so.
   It stays a single edge on the ordinary panel ground: the round-7b
   error style is loud on purpose, and a confirmation that answered it in
   kind would make both of them noise. */
.notice-box.good { border-left-color: var(--good); }
.notice-box p:last-child { margin-bottom: 0; }

/* -- the anonymous way back to a running job (#173) ---------------- */
/* A band across the top of the start page, shown only when the browser
   itself remembers a job and the server confirms it is still there.
   Styled as the calm accent band and not as a warning: nothing has gone
   wrong, there is simply somewhere to go back to. It ships `hidden`, so
   a reader with no remembered job, or with no script, never sees a strip
   of empty page where it would have been. */
.pointer-band {
  border-bottom: 1px solid var(--line);
  border-top: 3px solid var(--accent);
  background: var(--panel);
  padding: var(--s3) 0;
}
/* C.226: under the hero, inside the page's column, the band's words keep
   their own breathing room on its panel */
.start .pointer-band { padding: var(--s3); }
.pointer-band p { margin: 0; }
.pointer-band p + p { margin-top: var(--s2); }
.pointer-band .button-ghost { margin-left: var(--s3); }
.pointer-band[hidden] { display: none; }

/* -- the queue-transparency indicator (W-queue-ux) -----------------

   C.5 (owner 12.09.2026): a LINE, not a box. The left-edge colours that
   used to say "drawing" and "not moving" went with the border they were
   painted on, and they had already been painted over since the words
   moved onto the stage, whose own rule set the whole border-colour. The
   stall is still said — in the sentence the stalled line carries, which
   wears the site's one error style and is the one thing in this stack
   that stays a box, because a fault the reader must act on is exactly
   what that style is for. */
.queue-status .queue-line { margin: 0; font-weight: 600; }
.queue-status .queue-eta { margin: var(--s2) 0 0; }

/* -- the production-progress line (W-progress) --------------------- */
.progress-box .progress-count {
  margin: 0 0 var(--s2); font-variant-numeric: tabular-nums;
}
.progress-box .progress-eta { margin: var(--s2) 0 0; }
/* ONE LOOK PER PHASE (round 7b, the owner's finding of 02.09.2026:
   drawing and preparing-the-download wore the same animation, so the
   two phases were visually the same event). The class comes from
   pages.PROGRESS_PHASES, the same table the words come from, and the
   MOTION differs and not merely the colour:

     analysing  a bar of unknown length sliding across  (progress-slide)
     drawing    a determinate bar growing to the right  (no loop at all)
     producing  the whole track breathing, and the fill
                stepping rather than sliding             (progress-pack)
     done       still, and accented

   No two of them share a keyframe, and each honours prefers-reduced-
   motion the way the slide already did. */
/* ANALYSING: a bar of unknown length, sliding. It rode on
   data-indeterminate alone before, which fired for this phase only by
   the coincidence that the total is unknown here; the phase class says
   it outright now, so the look belongs to the phase and not to a
   side effect of another attribute. */
.progress-box.phase-analysing .progress-fill, .progress-track.phase-analysing .progress-fill {
  width: 40%;
  background: var(--accent);
  -webkit-animation: progress-slide 1.2s ease-in-out infinite;
  animation: progress-slide 1.2s ease-in-out infinite;
}
/* QUEUED (round 8, item 11): waiting for a worker to take hold of the
   first part. Its own look, because it is its own state — a narrow,
   unhurried sweep on an unfilled track. Not the analysing sweep, which
   is wider and quicker because something really is being read; not the
   drawing bar, which is still because the bar itself is the motion and
   here there is nothing yet to measure. */
.progress-box.phase-queued .progress-fill, .progress-track.phase-queued .progress-fill {
  width: 18%;
  background: var(--line-strong);
  -webkit-animation: progress-slide 2.4s ease-in-out infinite;
  animation: progress-slide 2.4s ease-in-out infinite;
}
/* DRAWING: a determinate bar that grows and never loops. Stillness is
   this phase's own look — the bar itself is the motion. */
.progress-box.phase-drawing .progress-fill, .progress-track.phase-drawing .progress-fill {
  -webkit-animation: none;
  animation: none;
}
/* DONE: still, and in the finished green (C.104). */
.progress-box.phase-done .progress-fill, .progress-track.phase-done .progress-fill {
  background: var(--part-done);
  -webkit-animation: none;
  animation: none;
}
/* STOPPING (C.78): the reader stopped the drawing and a worker is
   finishing the part it was inside. Still, and in the muted line colour
   rather than the accent: the bar says how far the batch got, and that
   nothing more is coming. STOPPED EARLY: stopped before any part
   existed — an empty, still track, nothing to measure and nothing
   moving. */
.progress-box.phase-stopping .progress-fill, .progress-track.phase-stopping .progress-fill {
  background: var(--ink-faint);
  -webkit-animation: none;
  animation: none;
}
.progress-box.phase-stopped-early .progress-fill, .progress-track.phase-stopped-early .progress-fill {
  width: 0;
  -webkit-animation: none;
  animation: none;
}
/* INTERRUPTED (C.199): the batch's work stopped and the watchdog settled
   it. Still, in the warning colour of a part that was not drawn: the bar
   says how far the batch got and that nothing more is coming. */
.progress-box.phase-interrupted .progress-fill, .progress-track.phase-interrupted .progress-fill {
  background: var(--part-fail);
  -webkit-animation: none;
  animation: none;
}
/* RESTAMPING (C.43): the drawings are finished and their title block is
   being printed again. A determinate bar like the drawing phase's —
   there is a real count to measure — but in the accent the finished
   phase wears rather than the drawing colour, because nothing here is
   being drawn: the batch is complete and one line of text on it is
   being brought up to date. C.5 retired the box, so the left edge
   that used to carry this phase's colour is gone with it; the bar's
   own accent and breath are what tell the phase apart. */
.progress-box.phase-restamping .progress-fill, .progress-track.phase-restamping .progress-fill {
  background: var(--part-done);
  -webkit-animation: progress-breathe 2.6s ease-in-out infinite;
  animation: progress-breathe 2.6s ease-in-out infinite;
}
.progress-box.phase-producing .progress-track, .progress-track.phase-producing {
  -webkit-animation: progress-breathe 2.6s ease-in-out infinite;
  animation: progress-breathe 2.6s ease-in-out infinite;
}
.progress-box.phase-producing .progress-fill, .progress-track.phase-producing .progress-fill {
  background: var(--part-done);
  -webkit-animation: progress-pack 1.6s steps(6, end) infinite;
  animation: progress-pack 1.6s steps(6, end) infinite;
}
@-webkit-keyframes progress-breathe {
  0%, 100% { opacity: 1; }
  50% { opacity: 0.55; }
}
@keyframes progress-breathe {
  0%, 100% { opacity: 1; }
  50% { opacity: 0.55; }
}
@-webkit-keyframes progress-pack {
  from { background-position-x: 0; }
  to { background-position-x: 1.4rem; }
}
@keyframes progress-pack {
  from { background-position-x: 0; }
  to { background-position-x: 1.4rem; }
}
/* the stall line, inside the progress box: the shared error style, one
   line high, with no margin of its own to break the box's rhythm */
.progress-box .progress-stalled { margin: var(--s3) 0 0; }
.progress-track {
  position: relative;
  height: 0.5rem;
  border-radius: var(--radius);
  background: var(--line);
  overflow: hidden;
}
.progress-fill {
  display: block;
  height: 100%;
  /* the determinate length rides on a custom property the server and the
     script both set, so the markup never carries an inline width the
     phone-layout rule forbids */
  width: var(--progress-pct, 0%);
  /* C.104: every live bar that counts finished parts fills in the one
     finished green; the reading and queued sweeps keep their own looks */
  background: var(--part-done);
  border-radius: inherit;
  transition: width 0.3s ease;
}
/* Before the total is known the bar has no honest length, so it shows a
   moving sliver rather than a fill — a "working" state that never claims a
   measurement it does not have. */
.progress-track[data-indeterminate="true"] .progress-fill {
  width: 40%;
  /* a sweep of unknown length counts nothing finished (C.104) */
  background: var(--accent);
  -webkit-animation: progress-slide 1.2s ease-in-out infinite;
  animation: progress-slide 1.2s ease-in-out infinite;
}
@-webkit-keyframes progress-slide {
  0% { margin-left: -40%; }
  100% { margin-left: 100%; }
}
@keyframes progress-slide {
  0% { margin-left: -40%; }
  100% { margin-left: 100%; }
}
@media (prefers-reduced-motion: reduce) {
  .progress-track[data-indeterminate="true"] .progress-fill {
    -webkit-animation: none;
    animation: none;
    width: 100%;
  }
  .progress-fill { transition: none; }
  /* the preparing phase keeps its COLOUR and loses its motion, so the
     two phases stay told apart for a reader who has asked for stillness */
  .progress-box.phase-producing .progress-track,
  .progress-box.phase-producing .progress-fill, .progress-track.phase-producing .progress-fill {
    -webkit-animation: none;
    animation: none;
  }
  /* and the queued phase keeps its own narrow, greyed bar for the same
     reason: the sentence beside it says what is happening, and the look
     must still not be mistaken for the drawing bar (round 8, item 11) */
  .progress-box.phase-queued .progress-fill, .progress-track.phase-queued .progress-fill {
    -webkit-animation: none;
    animation: none;
  }
  /* and the re-print keeps its accent and loses its breath, the same
     bargain the preparing phase makes (C.43) */
  .progress-box.phase-restamping .progress-fill, .progress-track.phase-restamping .progress-fill {
    -webkit-animation: none;
    animation: none;
  }
}

/* -- the preview band ---------------------------------------------- */

.band-head {
  display: flex; flex-wrap: wrap; align-items: baseline; gap: var(--s3);
  margin-bottom: var(--s3);
}
.band-head .help { margin: 0; }

/* The band's edges fade out where there is more band. The mask is
   driven by data-scroll, which the job page's script sets from the real
   scroll position: "start" fades only the right edge, "end" only the
   left, "middle" both, and "none" (the no-script state, and a band that
   fits) fades nothing. A fade that stayed put when the band ended would
   be telling the reader something untrue.

   The mask lives on `.band` itself (the scrolling strip), not on
   `.band-viewport` (fix #1, W-uipolish): the viewport now also carries
   the two nudge arrows flanking the strip, and a mask on their own
   ancestor would fade THEM out near the edges along with the tiles —
   the --fade custom properties still live here and are read by the
   child rule below them. */
.band-viewport {
  --fade: 3.5rem;
  --fade-left: 0px;
  --fade-right: 0px;
  /* Fix #2: the strip of drawing tiles pins to the top of the viewport,
     just below the sticky header (its measured height, or the 6rem CSS
     fallback with the script blocked), so it stays in reach while the
     file tree and the download panel scroll beneath it. The page's own
     paper colour and a step above the scroll layer keep the content that
     passes under it from showing through. Degraded to static on a phone
     below — see the media query.

     `position: relative` is what makes the viewport a positioning
     context for the two arrow buttons (fix #1); sticky already is one,
     so this only matters once the media query below trades sticky for
     static — without it the arrows would look for the next positioned
     ancestor up the tree and drift off the strip they are meant to
     flank. */
  position: sticky;
  top: calc(var(--header-offset) + var(--jobbar-h, 0px));
  z-index: 5;
  background: var(--paper);
  padding-block: var(--s2);
  transition: none;
}
/* On a narrow phone a tile at full size is most of the screen tall, so a
   PINNED STRIP AT FULL SIZE would cover the very content the reader
   scrolled to. Below this width the strip is a plain in-flow box by
   default — the JS-off state, and the state before abbundo.js has run —
   and the horizontal tile scroll inside it is untouched either way.
   Kept `relative` (see above) so the arrows stay anchored to the strip
   even when it is not sticky. */
@media (max-width: 40rem) {
  /* Fix #1 (W-uipolish2): `top` from the sticky rule above is NOT
     cancelled by trading `position: sticky` for `position: relative` —
     a relatively positioned element still honours its own `top`, which
     here goes on shifting the whole strip DOWN by the header offset,
     out of its own box and straight over the "Angezeigtes Teil" line
     that follows it in the flow (the space the strip vacated stays
     empty; relative positioning never reflows a sibling). `top: 0`
     is what actually leaves the strip exactly where its box sits. */
  .band-viewport { position: relative; top: 0; padding-block: 0; }

  /* Fix #2 (W-uipolish2): re-instated sticky on a phone, but ONLY once
     abbundo.js has actually added this class — a script-off reader keeps
     the plain in-flow strip above, exactly as before, never a pinned box
     it has no way to shrink. `top: var(--header-offset)` matches the
     desktop rule; on a phone the header itself is static (scrolls away,
     see `.site-header` below) so abbundo.js measures its height as 0 and
     the strip pins a few pixels under the top of the viewport, never
     under a header that is not there to collide with. */
  .band-viewport.js-sticky {
    position: sticky;
    top: calc(var(--header-offset) + var(--jobbar-h, 0px));
    z-index: 5;
    background: var(--paper);
    padding-block: var(--s2);
    transition: none;
  }

  /* ...and while it is actually stuck (abbundo.js toggles this once a
     sentinel placed just above the strip scrolls past the pin point,
     never merely because the strip COULD stick), it shrinks to a
     compact row rather than going on covering a tile's worth of screen
     — the reason a pinned strip was refused here in the first place.
     The tile keeps its border, shadow and tap target; only the frame's
     height drops and the caption (name + status) is dropped, since the
     enlarge button's own accessible name lives on the button itself
     (see abbundo.js `present()`), never on the caption. Swiping,
     tapping and the nudge arrows all keep working — none of this
     touches `.band`'s own scroll mechanics or `.band-arrow`'s fixed
     44px tap target. */
}
.band-viewport[data-scroll="start"] { --fade-right: var(--fade); }
.band-viewport[data-scroll="end"] { --fade-left: var(--fade); }
.band-viewport[data-scroll="middle"] {
  --fade-left: var(--fade);
  --fade-right: var(--fade);
}

.selected-part {
  display: flex; flex-wrap: wrap; gap: var(--s2) var(--s3);
  align-items: baseline;
  margin: 0 0 var(--s5);
}
.selected-part .label { color: var(--ink-faint); font-size: 0.85rem; }
.selected-part strong {
  font-family: var(--mono); font-size: 0.95rem;
  overflow-wrap: anywhere;
}

.band {
  display: flex;
  gap: var(--s4);
  overflow-x: auto;
  /* #236 (owner live-QA): the centred tile's own enlargement (below)
     grows both up and down from its resting size, and `overflow-x: auto`
     makes the browser compute the unset Y axis as `auto` too (the CSS
     Overflow spec ties the two axes together) — so a top padding this
     thin clipped the enlarged tile's own top edge, at every scroll
     position, first tile and last tile alike. The top padding now
     matches the bottom's: real headroom, not a cosmetic four pixels.

     #172, the clearance law: this is also the band's own share of
     --focus-clearance. 1rem is comfortably more than the 5px a focus
     ring needs, and the band-clearance gate checks that it stays so. */
  padding: var(--s4) var(--s1) var(--s4);
  margin-inline: calc(-1 * var(--s1));
  /* momentum on touch, and every tile is a page the band lands on */
  scroll-snap-type: x mandatory;
  scroll-padding-inline: var(--s1);
  overscroll-behavior-x: contain;
  -webkit-overflow-scrolling: touch;
  scrollbar-width: thin;
  /* the edge fade itself (moved off `.band-viewport`, see above) */
  -webkit-mask-image: linear-gradient(to right,
      transparent 0, #000 var(--fade-left),
      #000 calc(100% - var(--fade-right)), transparent 100%);
  mask-image: linear-gradient(to right,
      transparent 0, #000 var(--fade-left),
      #000 calc(100% - var(--fade-right)), transparent 100%);
}
/* QA11 item 8: end padding so the OUTERMOST tiles can reach the middle.
   A tile centres by snapping its own centre to the scrollport's centre;
   the first and last tile could not do that because there was no band
   before or after them to scroll into, so they selected without ever
   centring or enlarging (the owner's "first/second and last/second-last"
   defect). These two flex spacers give each end exactly half a scrollport
   minus half a tile of room — the tile's own `clamp(13rem, 78vw, 17rem)`
   basis, halved — so the outermost tile lands dead centre like any other.
   Transparent and inert; they are not snap targets, so the band never
   settles on one. Clamped at zero for a band narrower than one tile. */
.band::before,
.band::after {
  content: "";
  flex: 0 0 max(0px, calc(50% - clamp(6.5rem, 39vw, 8.5rem)));
  align-self: stretch;
}

/* Fix #1 (W-uipolish): clickable nudge arrows flanking the band, in
   ADDITION to the swipe/scroll that already worked — never a
   replacement for it. Real <button>s, not the maximized view's own
   previous/next (those walk the whole job one sheet at a time; these
   only scroll the strip by roughly one tile).

   Hiding at the ends reuses the SAME state the edge fade already reads
   off `data-scroll` (updateEdges() in abbundo.js): "start" means
   nothing precedes the strip so the left arrow has nothing to do,
   "end" mirrors that on the right, and "none" means the strip does not
   scroll at all, so neither arrow has a job. With JavaScript blocked
   `data-scroll` never leaves its server-rendered "none", so both
   arrows stay hidden and the swipe/scroll a real <label>-free strip
   already offers is the only way to move it — never a dead control. */
.band-arrow {
  position: absolute;
  top: 50%;
  transform: translateY(-50%);
  z-index: 2;
  display: flex;
  align-items: center;
  justify-content: center;
  min-width: var(--tap);
  min-height: var(--tap);
  padding: 0;
  margin: 0;
  border-radius: 50%;
  border: 1px solid var(--line-strong);
  background: var(--panel);
  color: var(--ink);
  font-size: 1.2rem;
  line-height: 1;
  box-shadow: var(--shadow);
  cursor: pointer;
}
.band-arrow-prev { left: var(--s2); }
.band-arrow-next { right: var(--s2); }
/* A band that does not scroll at all — every tile already on screen, and
   the script-off `none` state — needs no arrows. But a band that DOES
   scroll keeps BOTH arrows in their boxes at every scroll position (QA11
   item 8): they no longer vanish at a scroll end, because the end of the
   SCROLL is not the end of the SELECTION. Which one is dead is decided by
   the selected part's position, and abbundo.js says so with `disabled`
   (updateArrows) — the box stays, so nothing beside it shifts as an end
   is reached. */
.band-viewport[data-scroll="none"] .band-arrow {
  display: none;
}
.band-arrow[disabled] {
  opacity: 0.35;
  cursor: default;
  pointer-events: none;
}

/* Side room only: a phone narrow enough that the swipe is the whole
   interaction gets no arrows crowding the strip; a wider phone, a
   tablet and a desktop window all keep them. Gated on touch (coarse
   pointer, no hover) so narrowing a DESKTOP window this far still
   shows the arrows — a mouse has no swipe to fall back on. */
@media (hover: none) and (pointer: coarse) and (max-width: 26rem) {
  .band-arrow { display: none; }
}

.tile {
  flex: 0 0 clamp(13rem, 78vw, 17rem);
  /* centre, not start: the band's snap positions and "bring this tile
     into the middle" have to be the same places, or a click that
     centres a tile would be undone by the snap on the way. */
  scroll-snap-align: center;
  margin: 0;
  background: var(--panel);
  border: 1px solid var(--line);
  border-radius: var(--radius);
  box-shadow: var(--shadow);
  /* #172, the clearance law: the tile does NOT clip its own content.
     It used to (`overflow: hidden`, to round the sunken frame's top
     corners over the tile's own radius), and that is precisely what cut
     the keep control's focus ring off at the tile's bottom and left
     edge — the ring is drawn outside the control, so any ancestor
     scroll box eats it. The rounding is now done where the rounding
     belongs, on `.tile .frame` below, which clips only the drawing it
     contains; nothing an ancestor of a control clips it any more. */
  overflow: visible;
  display: flex;
  flex-direction: column;
  /* #156: the centred tile's own visual focus is a gentle enlargement
     (the owner's explicit preference over a frame or border) — a plain
     transform, so it costs no layout and never shifts a neighbour.
     Also transitions box-shadow (#236) for the selected tile's own soft
     elevation below, which grows in step with the enlargement instead
     of snapping on. */
  transform: scale(1);
  transition: transform 200ms ease, box-shadow 200ms ease;
}
.tile.tile-centred {
  /* #236 (owner live-QA): a touch more recognisable than the original
     1.035 — still calm, still no bounce, just easier to see which tile
     is on show. */
  transform: scale(1.06);
  position: relative;
  z-index: 1;
  /* #236: the owner earlier rejected a hard frame around the selected
     tile, so this stays understated — the site's own elevated-panel
     shadow token plus a soft accent ring at the same low-saturation
     tint the focus states already use, never a solid border. */
  box-shadow: var(--shadow-lift), 0 0 0 2px var(--accent-soft);
}
@media (prefers-reduced-motion: reduce) {
  .tile { transition: none; }
}

.tile .frame {
  position: relative;
  aspect-ratio: 297 / 210;
  display: grid;
  place-items: center;
  background: var(--panel-sunken);
  color: var(--ink-faint);
  font-size: 0.85rem;
  /* #172: the frame is the ONLY clipping box in a tile — it holds the
     drawing and nothing interactive but the full-bleed enlarge overlay,
     which has no ring of its own to lose. The top corners are rounded
     here now that `.tile` no longer does it for everything inside it. */
  overflow: hidden;
  border-radius: var(--radius) var(--radius) 0 0;
}
.tile .frame img { width: 100%; height: 100%; object-fit: contain; }
.tile .frame button.enlarge {
  position: absolute; inset: 0;
  background: none; border: 0; padding: 0; min-height: 0;
  cursor: zoom-in;
}
.tile figcaption {
  display: flex; align-items: center; justify-content: space-between;
  gap: var(--s2);
  padding: var(--s3);
  border-top: 1px solid var(--line);
  font-size: 0.85rem;
}
.tile .part-name {
  font-family: var(--mono); font-size: 0.78rem; color: var(--ink-soft);
  overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
.tile[data-state="failed"] .frame { background: var(--bad-soft); color: var(--bad); }
.tile[data-state="failed"] .frame { padding: var(--s4); text-align: center; }

/* #153: a part the customer stopped or unticked. Deliberately MUTED and
   not the refusal's red — nothing went wrong, the service did what it
   was told, and a tile that looked broken would send a reader hunting
   for a fault they caused on purpose. */
.tile[data-state="skipped"] .frame {
  /* #172: this used to read `var(--surface-soft, var(--surface))` and
     NEITHER token is defined anywhere in this stylesheet, so the whole
     declaration was invalid at computed-value time and an excluded tile
     kept the ordinary sunken background. The muted panel token is the
     one that was meant. */
  background: var(--panel-sunken); color: var(--ink-soft);
  padding: var(--s4); text-align: center;
}
.tile[data-state="skipped"] { opacity: 0.72; }

/* #153/#172: the per-part keep box — ONE control, a real checkbox, with
   its submit button beside it only for a reader whose script is off
   (job.js hides it and submits on change). The frozen version (a
   delivered part, or a cancelled batch) carries its reason underneath.

   The side and bottom padding is the clearance law: this row holds the
   only interactive controls that sit at a tile's edge, and without it
   the checkbox's focus ring was drawn flush against — and, while the
   tile still clipped, straight through — the tile's own border. */
.tile .keep {
  display: flex; align-items: center; gap: var(--s2); flex-wrap: wrap;
  margin-top: var(--s2); font-size: 0.78rem;
  padding: 0 var(--focus-clearance) var(--focus-clearance);
}
.tile .keep label { display: flex; align-items: center; gap: var(--s1); }
.tile .keep.locked { color: var(--ink-soft); }
.tile .keep.locked .help { flex-basis: 100%; font-size: 0.72rem; }

/* #174 (owner QA): the SAME control, in the other two places a part is
   listed — the "uploaded files" rows and the maximized view's left
   lane. One law, one macro, one builder in job.js; this only decides
   how much room the words get.

   The compact variant carries its label for a screen reader and as a
   tooltip instead of printing it: the row is a line of a list and the
   lane is a fixed narrow column, and a control that pushed the part's
   own name off the line would have made the listing worse to buy a
   consistency nobody asked for. The BOX is the same size and the same
   target either way — this is a label decision, not a control one. */
.keep-row {
  display: flex; align-items: center; gap: var(--s2);
  margin: 0; font-size: 0.78rem; color: var(--ink-soft);
}
.keep-row label { display: flex; align-items: center; gap: var(--s1); }
.partlist .keep-row {
  padding: 0 var(--focus-clearance) var(--s1)
           calc(var(--s4) + var(--focus-clearance));
}
.partlist .keep-row.locked .help { font-size: 0.72rem; }
/* In the lane the control sits at the end of the row beside the part's
   own button, and a frozen box states its case by being frozen: the
   SENTENCE saying why is not repeated in a column this narrow, because
   the tile and the maximized bar both carry it in full for the same
   part. */
.viewer-tree .keep-row {
  flex: none; align-self: center; padding: 0 var(--s1);
}
.viewer-tree .keep-row .help { display: none; }

/* #153: the cancel control, beside the job status where a reader
   watching a batch they no longer want is already looking. */
.job-cancel {
  display: flex; align-items: center; gap: var(--s3); flex-wrap: wrap;
  margin-top: var(--s3);
}
.job-cancel .help { font-size: 0.8rem; color: var(--ink-soft); }

/* #168, W-sheetnav (b): the tile's own small sheet-count badge, only for
   a part the core split onto more than one sheet. `pointer-events: none`
   so it never steals the click the frame's own enlarge button (`inset: 0`
   underneath it) answers — the badge is information, not a control. */
.tile .sheet-badge {
  position: absolute; top: var(--s2); right: var(--s2);
  pointer-events: none;
  background: rgba(0, 0, 0, 0.65); color: #fff;
  font-size: 0.72rem; font-weight: 600;
  padding: 0.15em 0.5em;
}

/* #164, no-silent-quality-loss: the per-part readability shortfall note
   — the same warning colour the file-row note above uses, so a reduced-
   detail drawing reads as visually distinct from an ordinary finished
   tile, never only as a caption a reader could miss. */
.tile .readability-note {
  margin: 0; padding: var(--s2) var(--s3) var(--s3);
  font-size: 0.8rem; color: var(--bad);
  border-top: 1px solid var(--line);
}
.tile .readability-note a { color: inherit; }

/* The functional animation: a tile whose part is being drawn or
 * re-checked by the server carries a calm sweep. It says "being
 * checked", which is what is happening. */
.tile[data-state="working"] .frame::after,
.tile[data-redrawing="true"] .frame::after {
  content: "";
  position: absolute; inset: 0;
  background: linear-gradient(100deg,
      transparent 20%, var(--accent-soft) 50%, transparent 80%);
  opacity: 0.85;
  animation: sweep 2.4s ease-in-out infinite;
}
/* C.211-B4 (owner 26.10.2026): a plate whose Sichtseite or Maserung was
   changed keeps its old preview on the page, dimmed and under the
   drawing sweep, until the new sheet takes its place - never a blank
   tile. The pill under it says "wird neu gezeichnet". */
.tile[data-redrawing="true"] .frame img { opacity: var(--redraw-dim); }
/* C.211-B2b: a plate whose redraw failed twice keeps its old preview
   dimmed, without the sweep (nothing is being drawn), under the pill
   „Neu zeichnen fehlgeschlagen" until „Erneut versuchen" */
.tile[data-redraw-failed="true"] .frame img { opacity: var(--redraw-dim); }

@keyframes sweep {
  from { transform: translateX(-100%); }
  to { transform: translateX(100%); }
}
/* A part being PACKED into the download, not drawn (round 7b). Its own
   state since pages._STATE_FOR_STATUS split it off, and its own motion:
   the drawing sweep travels sideways, this one settles downwards, which
   is what "the file is being put together" looks like. */
.tile[data-state="packing"] .frame::after {
  content: "";
  position: absolute; inset: 0;
  background: linear-gradient(180deg,
      transparent 30%, var(--good-soft) 55%, transparent 75%);
  opacity: 0.9;
  animation: pack 1.8s ease-in-out infinite;
}
@keyframes pack {
  from { transform: translateY(-100%); }
  to { transform: translateY(100%); }
}

.tile .frame img { animation: settle 220ms ease-out both; }

@keyframes settle {
  from { opacity: 0; }
  to { opacity: 1; }
}

/* -- the enlarged preview ------------------------------------------ */

/* The dialog is the whole VIEWPORT, not a box around the drawing.
   That is what keeps the two step arrows still: a dialog sized to its
   content is re-centred by the browser for every sheet, so anything
   anchored inside it travels with the sheet's orientation. Here the
   overlay never changes size, the panel with the drawing is centred
   inside it, and the arrows are pinned to the screen's own left and
   right edge at half its height — the same two pixels for every part
   of every job. */
.viewer {
  position: fixed; inset: 0; margin: 0;
  width: 100vw; max-width: 100vw;
  height: 100vh; max-height: 100vh;
  height: 100dvh; max-height: 100dvh;
  border: 0; padding: 0;
  background: transparent; color: var(--ink);
  border-radius: 0; box-shadow: none;
  overflow: hidden;
  /* the surround's own containment — see the block below the backdrop
     rule: the overlay is a scroll container with nothing to scroll, so
     a wheel that lands on it is at its edge at once and must not be
     handed on to the page underneath */
  overscroll-behavior: contain;
  /* The lane the 3D column owns at the left edge. Zero until the
     script says there is a column, and ONE variable for all three
     things that must agree about it: the column's own width, the
     previous-arrow's distance from the edge, and how much width is
     left for the drawing. Three numbers typed three times is how an
     arrow ends up under a panel. */
}
/* THE ARROWS NEVER MOVE (owner's rule, VC3o). The lane is ONE width
   whenever there is a column at all, and that width does not depend on
   which part of the job is on show.

   It used to. A batch mixes files that carry an assembly with files
   that hold a single solid, and the lane was narrowed to 11rem for a
   part whose file has no mesh, widened to 15rem for one whose file
   has. Stepping from a part of the assembly to a part of a single-solid
   file therefore threw the previous-arrow 4rem — 64 px — sideways under
   a cursor that had not moved. The narrow variant is gone; the column
   now carries the WHOLE batch's tree and wants the wider lane in every
   case, and 15rem is what it already took at its widest.

   The collapse toggle is the one thing left that changes the lane, and
   that is a control the reader presses on purpose: a per-reader state,
   never a per-part one. Nothing an arrow sits on moves while somebody
   is only stepping through drawings. */
.viewer[data-side="on"] { --viewer-side: 15rem; }
.viewer[data-side="off"] { --viewer-side: 3.75rem; }
.viewer[open] {
  display: flex; align-items: center; justify-content: center;
  padding-left: var(--viewer-side);
}
.viewer::backdrop { background: rgb(0 0 0 / 62%); }

/* THE PAGE BEHIND THE MAXIMIZED VIEW NEVER SCROLLS (owner, 31.08.2026).

   He was scrolling the part list beside a sheet, reached the bottom of
   the list, and the page underneath took over and carried on — the
   drawing he was reading slid away under an overlay that had not
   moved. That is scroll chaining, and it is the browser's default: a
   scrollable box that has reached its edge hands the rest of the wheel
   to its ancestors, and a modal <dialog> does not stop it.

   THE CHAIN IS CUT WHERE IT WOULD BE HANDED ON, and nothing is taken
   away from the document. Each pane inside the overlay contains its own
   scroll (`.viewer-body` and `.viewer-tree` below), so a pane that has
   reached its end simply stops handing on what is left; and the dialog
   ITSELF contains too — it is a scroll container, having no visible
   overflow of its own it is always at its edge, so a wheel that lands
   on the darkened surround has nowhere to go either.

   The first cure written here was a lock instead: a class on the root
   element setting `overflow: hidden` on the document while the overlay
   was open. It worked and it was the wrong instrument, which this
   suite's own no-clipped-text law said out loud — that rule cuts what
   is inside the element, and what is inside that one is every sentence
   on the page. The job here is to stop a scroll from being handed on,
   not to hide anything, so it is done by the property that means
   exactly that. Nothing is switched, so nothing has to be switched
   back, and no script is needed to hold the page still. */

/* The lane each arrow owns on either side, so the panel stops before
   the arrows instead of underneath them. */
.viewer .viewer-panel {
  --viewer-lane: calc(var(--tap) + 2 * var(--s3));
  /* the anchor for fix #4's hint and zoom buttons (below): they sit as
     the panel's own children, siblings of .viewer-body and not inside
     it, so the pan/pinch pointer listeners on .viewer-body never see a
     click that lands on them. */
  position: relative;
  display: flex; flex-direction: column;
  /* Item 10 (owner design decision): a CONSTANT frame, independent of
     the sheet's own orientation. It used to be sized by its own
     CONTENT — width and height were only CEILINGS (max-width/
     max-height) and the panel actually shrank to the image's intrinsic
     size — so a landscape sheet opened a wide, short panel and a
     portrait one a narrow, tall panel: the bar, the close button and
     the starting "fit" magnification all landed on different pixels
     sheet to sheet, and paging through a mixed batch made every
     control jump. WIDTH and HEIGHT are real used values now, set once
     from the space available beside the arrows and the tree lane —
     never from what is drawn inside — so the frame is the identical
     rectangle for every sheet of every part; the letterboxing that used
     to happen implicitly (a narrower panel around a portrait image) now
     happens explicitly, inside the frame, on the image itself (see
     ".viewer img" below). */
  width: min(96vw, calc(100vw - var(--viewer-side)
                        - 2 * var(--viewer-lane)));
  height: 94vh;
  height: 94dvh;
  overflow: hidden;
  background: var(--panel);
  border-radius: var(--radius); box-shadow: var(--shadow-lift);
}
.viewer .viewer-body {
  /* Fix #7 owns every gesture in here — the wheel, a drag, a pinch — so
     the browser must not also scroll or pinch this box: touch-action:
     none hands the finger to the script, which zooms and pans the sheet
     with a transform. A fitted sheet needs no scrollbar; overflow:auto is
     kept only for the rare short screen, and a zoomed sheet is clipped to
     the panel (the .zoomed rule below). */
  overflow: auto;
  /* the drawing's own pane keeps its scroll to itself (owner,
     31.08.2026) — see the lock beside `.viewer::backdrop` */
  overscroll-behavior: contain;
  touch-action: none;
  /* centre the sheet both ways so zoom (fix #7) turns about its true
     middle and the pan clamp stays symmetric; a fitted sheet is unchanged
     to the eye, a centred letterbox either way */
  display: flex;
  align-items: center;
  justify-content: center;
  /* Item 10: this box IS the letterbox now — it fills whatever the
     panel's fixed height leaves after the bar (flex:1 1 auto below),
     never a second, viewport-relative ceiling of its own the way it
     used to duplicate the panel's. A visible neutral, not the paper-
     white the panel and most sheets share, so a reader can always tell
     the letterbox from the sheet's own white background — the same
     "sunken" tone the rest of the page already uses for a receded
     area, not a colour invented for this one box. */
  background: var(--panel-sunken);
  /* min-height:0 so the sheet scrolls INSIDE the panel on a short
     screen instead of being clipped by the panel's own ceiling */
  flex: 1 1 auto; min-height: 0;
}
/* Fix #7: a zoomed sheet is clipped to the panel and panned by transform,
   and the cursor says the sheet can be dragged. The reset control in the
   bar (also a double-click or double-tap) is the visible way back to
   fit-to-view. */
.viewer .viewer-body.zoomed { overflow: hidden; cursor: grab; }
.viewer .viewer-body.zoomed:active { cursor: grabbing; }
/* Item 9 (owner live-QA): the browser's OWN native image drag competed
   with fix #7's pointer-driven pan — a left-button drag moved about a
   pixel and then the browser took over with a ghost image on the
   cursor, which the pointermove handler below never even saw. The
   `draggable="false"` attribute in the markup is Firefox's own switch
   for this; `-webkit-user-drag` is Safari/Chromium's (WebKit invented
   it, Chromium kept it); neither engine honours the other's alone, so
   both are set. `user-select: none` stops a drag also starting a text
   selection on the surrounding panel, and `touch-action: none` already
   on `.viewer-body` above is what keeps a FINGER drag from ever reaching
   the browser's own scroll/zoom to begin with — this rule is the mouse
   engines' equivalent for their own native drag. */
.viewer .viewer-body img {
  -webkit-user-drag: none;
  user-drag: none;
  -webkit-user-select: none;
  user-select: none;
}

/* #155d: the "not drawn yet" placeholder present() shows instead of the
   image — same panel, same centring, so stepping onto an undrawn part
   never shrinks or reflows the dialog around it. */
.viewer .viewer-placeholder {
  margin: 0; padding: var(--s6);
  color: var(--ink-faint); font-size: 1rem; text-align: center;
}

/* Fix #4 (W-uipolish): pinch-zoom and pan already worked (fix #7 above)
   and nothing said so. A quiet hint, faded out by the script the first
   time any zoom happens. c243: shown to the mouse as well (the sheet
   viewer's one hint, .sheet-view-hint: the pointer's words or the
   finger's) - the owner did not find the drag, and a reader who does not
   know the double-click cannot use it. */
.viewer .viewer-zoom-hint {
  display: block;
  position: absolute;
  left: 50%;
  /* clear of the +/- buttons' own corner below it (var(--s3) tall
     plus their own height), so the two never overlap on a narrow panel */
  bottom: var(--s8);
  transform: translateX(-50%);
  z-index: 1;
  margin: 0;
  padding: var(--s2) var(--s4);
  border-radius: var(--radius-sm);
  background: rgb(27 26 23 / 72%);
  color: #fff;
  font-size: 0.85rem;
  text-align: center;
  pointer-events: none;
  opacity: 1;
  transition: opacity 0.4s ease;
}
.viewer .viewer-zoom-hint.seen { opacity: 0; }

/* The +/- buttons: always offered, for a one-handed reader who would
   rather tap than pinch. They sit over the sheet's own corner, clear of
   the reset control and the close button that already live in the bar
   above, and drive the same zoom state the wheel and the pinch do. */
.viewer .viewer-zoom-controls {
  position: absolute;
  right: var(--s3);
  bottom: var(--s3);
  z-index: 1;
  display: flex;
  flex-direction: column;
  gap: var(--s2);
}
.viewer .viewer-zoom-btn {
  min-width: var(--tap); min-height: var(--tap);
  padding: 0;
  border-radius: 50%;
  font-size: 1.2rem;
  line-height: 1;
  background: var(--panel);
  box-shadow: var(--shadow);
}
/* A preview is NEVER cropped (owner's law, VC3n). The sheet is fenced
   in BOTH directions and letterboxed inside what is left, portrait and
   landscape alike.

   It used to be fenced by height alone (`max-width: none`), which is
   right for a portrait sheet and wrong for a landscape one: an A4
   landscape preview came out wider than the panel, the panel clips,
   and a strip fell off each side unless the reader thought to scroll
   sideways. Measured before the fix: 140 px of the sheet past the
   right edge in a 1280x900 window, 456 px in a 900x1000 one — a third
   of a six-view drawing, gone.

   Item 10 (owner design decision, SUPERSEDED by the uniform true-scale
   round): a `width:100%; height:100%; object-fit:contain` frame fenced
   the sheet correctly but let a landscape sheet's box grow to fill the
   SAME frame HEIGHT a portrait sheet's box filled — legal by
   letterboxing's own rule (nothing is cropped) but wrong by a stricter
   one the owner's mockups named directly: two orientations of the same
   physical paper must occupy each other's box with width and height
   swapped, never independently re-fitted, or the landscape sheet's text
   reads visibly larger. `object-fit:contain` cannot express that — it
   fits EACH image to the frame on its own, one image at a time, with no
   memory of what the previous sheet's box was.

   So sizing moved out of CSS and into `abbundo.js`: `present()` and
   `showSheet()` compute ONE mm-to-px factor for the whole part's sheet
   set (anchored so the largest page dimension in the set fits this
   frame) and set `image.style.width`/`height` in real pixels — a
   landscape sheet's box is then exactly its portrait sibling's box with
   width and height swapped, because both were multiplied by the same
   factor. `width:auto; height:auto` here is deliberately NOT the used
   size a script sees; it is only what a JS-off reader gets — a graceful
   `object-fit:contain`-alike (the browser's own intrinsic-ratio scaling
   under a max-width/max-height fence), since progressive enhancement
   (V13) means this page still has to show something sane with the
   script blocked. `.viewer-body`'s existing centred flex is what turns
   the JS-set box into a letterbox: any side smaller than the frame
   simply centres, no CSS letterboxing rule needed beyond that. The pan
   clamp in abbundo.js reads `image.clientWidth`/`clientHeight` directly
   for exactly this reason — once the box is real pixels rather than the
   frame's own 100%/100%, those ARE the sheet's true visible rectangle
   again, and the `containedSize()` reimplementation of `object-fit`
   math is gone with the rule that made it necessary. */
.viewer img {
  display: block;
  max-width: 100%;
  max-height: 100%;
  width: auto;
  height: auto;
}
.viewer .viewer-bar {
  display: flex; align-items: center; flex: none;
  gap: var(--s3); padding: var(--s3) var(--s4);
  border-bottom: 1px solid var(--line);
}
.viewer .viewer-bar strong {
  flex: 1 1 auto; min-width: 0;
  overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
  font-family: var(--mono); font-size: 0.95rem;
}
.viewer .viewer-bar form { margin: 0; }

/* #174 (owner QA), THE FIXED-SLOT LAW. Every conditional control of this
   bar sits in a slot that is always in the markup and always in the
   layout; `data-shown="false"` takes the CONTENT out of sight and out of
   the tab order with `visibility`, which — unlike `display: none`, which
   `[hidden]` means everywhere else on this page — leaves the box exactly
   where it was. So the include box, the report link and the sheet
   controls stay on the same pixels whether or not the reader has zoomed,
   and whether the part they stepped to takes one sheet or three.

   The floors are for the two slots that can be genuinely EMPTY rather
   than merely invisible: a failed part has no include box to clone, and
   an anonymous job has no report link at all. An empty slot with no
   floor would collapse to nothing, which is the same defect by another
   route. */
.viewer .viewer-slot {
  flex: none; display: flex; align-items: center; justify-content: center;
  min-width: var(--tap);
}
.viewer .viewer-slot[data-shown="false"] {
  visibility: hidden;
}
.viewer .viewer-slot.viewer-keep { min-width: 9rem; }
.viewer .viewer-slot-report { min-width: 7rem; }
/* W-ux: the close control is an X, and it reads as one — the glyph is
   set large enough to be an obvious way back to the tile. */
.viewer .viewer-close {
  font-size: 1.5rem; line-height: 1; padding-top: 0; padding-bottom: 0;
}
.viewer .viewer-step {
  position: fixed; top: 50%; transform: translateY(-50%);
  z-index: 2;
  /* exactly one tap target wide, so the lane the panel keeps free is
     the lane the button actually occupies */
  padding: var(--s2);
  min-width: var(--tap); min-height: var(--tap);
  font-size: 1.1rem; line-height: 1;
  background: var(--panel);
  box-shadow: var(--shadow);
}
.viewer .viewer-step-prev { left: calc(var(--viewer-side) + var(--s3)); }
.viewer .viewer-step-next { right: var(--s3); }
.viewer .viewer-count { flex: none; font-variant-numeric: tabular-nums; }

/* #168, W-sheetnav (a): paging through ONE split part's own sheets, a
   distinct axis from the part-to-part left/right arrows either side of
   the panel. Lives in the bar, which never moves with sheet orientation,
   beside the "n/N" part counter it complements rather than replaces —
   invisible whole (a `.viewer-slot` with data-shown="false", #174) for
   the single-sheet majority — invisible and not removed, so the
   controls to its right do not move when a two-sheet part follows a
   one-sheet one. */
.viewer .viewer-sheet-group {
  display: flex; align-items: center; flex: none;
  gap: var(--s2);
}
.viewer .viewer-sheet-btn {
  min-width: var(--tap); min-height: var(--tap);
  padding: 0;
  font-size: 1rem;
  line-height: 1;
}
.viewer .viewer-sheet-btn:disabled { opacity: 0.35; cursor: default; }

/* #172: the open part's own keep control, in the bar where the reader is
   already looking. Its markup is the tile's, cloned, so this only has to
   place it: the tile's own `.tile .keep` rules do not reach inside the
   dialog. It may wrap (a frozen box carries its reason underneath) and it
   may shrink, but it never squeezes the sheet controls out of the bar,
   and it is a fixed slot (#174) so a part with no box at all leaves the
   space it would have taken. */
.viewer .viewer-keep {
  display: flex; align-items: center; flex: 0 1 auto; min-width: 0;
  font-size: 0.85rem;
}
.viewer .viewer-keep .keep {
  display: flex; align-items: center; gap: var(--s2); flex-wrap: wrap;
  margin: 0; padding: 0;
}
.viewer .viewer-keep .keep label {
  display: flex; align-items: center; gap: var(--s1);
}
.viewer .viewer-keep .keep.locked { color: var(--ink-soft); }
.viewer .viewer-keep .keep.locked .help {
  flex-basis: 100%; font-size: 0.72rem; margin: 0;
}
.viewer .viewer-sheet-of {
  flex: none; font-variant-numeric: tabular-nums; font-size: 0.85rem;
}

/* Owner law: every warning shown on a part's CARD is shown in the
   maximized preview of that part too, in the same words. The notes are
   the tile's own elements, cloned, so this only has to place them — and
   it has to undo the tile's own framing, because a top border and a
   tile's padding make sense under a thumbnail and read as a stray line
   inside a dialog.

   The same warning colour the tile uses, deliberately: the reader must
   see the same thing said the same way in both places, or the two stop
   reading as one warning about one part. It is NOT in the icon bar — a
   warning is a sentence — so it takes the panel's width under the bar
   and stays clear of the sheet. Hidden as a whole when the open part
   has nothing to warn about, so a drawing at full detail shows no empty
   strip. */
.viewer .viewer-notes {
  flex: none; margin: 0; padding: 0 var(--s3) var(--s2);
  display: flex; flex-direction: column; gap: var(--s1);
}
.viewer .viewer-notes[data-shown="false"] { display: none; }
.viewer .viewer-notes .readability-note {
  margin: 0; padding: 0; border: 0;
  font-size: 0.8rem; color: var(--bad);
}
/* C.27/C.28: the quiet "printed again / drawn again" line of the part,
   cloned into the same slot as the warnings and deliberately NOT red —
   it is a fact about the package, not a defect of the drawing. */
.viewer .viewer-notes .reprint-note {
  margin: 0; padding: 0; border: 0;
  font-size: 0.8rem; color: var(--ink-soft);
}
.viewer .viewer-notes a { color: inherit; }
.viewer .viewer-notes [hidden] { display: none; }

/* On a phone there is no room for two lanes beside the sheet, so the
   panel takes the width and the arrows ride over the drawing — still
   at the same two screen positions, and still clear of the bar, which
   sits at the top of the panel while they sit at half the screen. Item
   10: still a fixed WIDTH, not a ceiling — the constant-frame rule
   holds at every width, this is only which fixed value applies. */
@media (max-width: 40rem) {
  .viewer .viewer-panel { width: 96vw; }
  .viewer .viewer-step { box-shadow: var(--shadow-lift); }
}

/* -- the uploaded-files tree ---------------------------------------- */

/* A file that split into several parts opens into them; a file with one
   part is a flat row. Built from <details>/<summary>, so it works with
   JavaScript switched off and the keyboard already knows how to use it. */

.filetree { list-style: none; margin: 0 0 var(--s5); padding: 0; }
.filetree-item + .filetree-item { margin-top: var(--s2); }

.file-row {
  border: 1px solid var(--line);
  border-radius: var(--radius);
  background: var(--panel);
}
.file-row.flat, .file-row > summary {
  display: flex; flex-wrap: wrap; align-items: center;
  gap: var(--s2) var(--s3);
  padding: var(--s3) var(--s4);
  min-height: var(--tap);
}
.file-row > summary { cursor: pointer; list-style-position: inside; }
.file-row > summary::marker { color: var(--ink-faint); }
.file-row > summary:hover { background: var(--panel-sunken); }
.file-row .file-name { font-weight: 600; overflow-wrap: anywhere; }
.file-row .file-parts { color: var(--ink-faint); font-size: 0.85rem; }
.file-row .file-note { color: var(--bad); font-size: 0.85rem; margin: 0; }
.file-row > .file-note { padding: 0 var(--s4) var(--s3); }
/* C.2: what an upload held besides solids is a STATEMENT and not a
   fault — the file split, its parts are being drawn, and some shapes in
   it could not be. It reads in the quiet ink the part count uses rather
   than in the red a failed file gets, because a red line on a file that
   worked would send a reader hunting for a problem they do not have.
   It is its own class, `.file-note-quiet`, rather than `.file-note`
   overridden: warning-style-law (#172) derives its red set from every
   selector the stylesheet ever paints with `--bad`, and `.file-note` is
   one of them, so an element carrying that class reads as a warning no
   matter what a later, more specific rule repaints it to. */
.file-row .file-note-quiet { color: var(--ink-faint); font-size: 0.85rem; margin: 0; }
.file-row > .file-note-quiet { padding: 0 var(--s4) var(--s3); }
.viewer-tree .file-note-quiet { color: var(--ink-faint); font-size: 0.8rem; margin: 0; }
.stagework .viewer-tree .file-note-quiet { color: var(--ink-faint); }
/* C.2: how the file's numbers were read, and the door to the other
   reading. A notice box inside the file card, sized down to sit under a
   row rather than at the top of a page. */
/* C.58j (owner 29.09.2026): THE SIDE-PANEL NOTE (_side_note.html) - one
   line with its outcome as the kit accordion's question row, the
   explanation folded under it, the action in the row beneath. */
.file-row > .side-note { margin: 0 var(--s4) var(--s3); }
.side-note {
  border: 1px solid var(--line);
  border-left: 3px solid var(--accent);
  border-radius: var(--radius);
  background: var(--panel);
  padding: 0 var(--s3);
  font-size: 0.85rem;
}
.side-note .kit-acc-item { border-bottom: 0; }
.side-note .kit-acc-q { padding: var(--s2) 0; }
.side-note .kit-acc-a { padding-bottom: var(--s3); }
.side-note .kit-acc-a > * + * { margin-top: var(--s2); }
.side-note .file-units-note { margin: 0; }
.side-note-action { padding: 0 0 var(--s3); }
.side-note-action form { margin: 0; }
/* The note stands on the stage's ground and reads the stage's words:
   the page's own tokens inside it are the stage's, so the kit accordion,
   the link and the ghost button in it keep their contrast in both
   schemes. Before C.58j the box was the page's white note with the
   stage's pale ink - the faint text of the owner's screenshot. */
.stagework .side-note {
  --ink: var(--stage-ink);
  --ink-soft: var(--stage-soft);
  --ink-faint: var(--stage-faint);
  --line: var(--stage-line);
  --line-strong: var(--stage-line-strong);
  --panel: var(--stage-file-bg);
  --accent: var(--stage-hover-line);
  --accent-ink: #10131a;
  --accent-soft: var(--stage-button-hover);
  color: var(--stage-soft);
}

.partlist { list-style: none; margin: 0; padding: 0 var(--s4) var(--s3); }
.partlist li { margin: 0; }
/* C.187 (owner complaint 12.10.2026, traced 18.10.2026): a batch's part
   list holds a row per part - 260 for the owner's file - and every frame in
   which a row changed had the browser style and paint all of them, the
   rows out of sight included (paint fell from 130 ms to 40 ms of a frame
   at four-fold slowdown once the rows and tiles out of sight were skipped).
   A row out of sight is
   now laid out and painted only when it comes into view; until then it
   keeps the height it last had (one tap row before it was ever shown). */
.partlist > li { content-visibility: auto; contain-intrinsic-size: auto var(--tap); }
/* C.187: on the phone the band's tiles the same way - a tile out of
   sight is styled and painted only when it comes into view, keeping the
   size it last had; the desktop band, measured by its own gates, is
   left as it is. */
body.phone-job .band .tile { content-visibility: auto;
  contain-intrinsic-size: auto 17rem auto 20rem; }
/* #155a: the row is a real button now (was a plain flex row of spans),
   so it answers to Tab, Enter and Space — everything the base button
   rule sets is given back, the same trade .viewer-tree .tree-part
   already makes, so the row still reads as a line of a list and not as
   one of the page's accent-coloured buttons. */
.partlist .partrow-button {
  display: flex; flex-wrap: wrap; align-items: center; width: 100%;
  gap: var(--s2) var(--s3);
  padding: var(--s2) 0 var(--s2) var(--s4);
  margin: 0;
  border: 0; border-top: 1px solid var(--line); border-radius: 0;
  background: transparent; color: inherit;
  font: inherit; text-align: left;
  cursor: pointer;
}
.partlist .partrow-button:hover { background: var(--panel-sunken); filter: none; }
.partlist .part-n { color: var(--ink-faint); font-size: 0.85rem; }
.partlist .part-name {
  font-family: var(--mono); font-size: 0.85rem;
  overflow-wrap: anywhere;
}

/* -- the assembly in 3D --------------------------------------------- */

/* The empty right half of a file card, filled with that file's own
   assembly (owner's ruling V25 b). The part rows keep the left half,
   so nothing that was readable before has moved; on a narrow screen
   the two halves become two rows, the view under the rows.

   The class is set by the server, not asked of the DOM with :has(),
   because the server already knows which files have a mesh and a
   selector that has to search for the answer would compute it twice.
   It is set when there IS a mesh and not when there might be one: it
   used to go on for a file that was still splitting too, and half the
   card was then given to a container rendered `hidden` while the part
   rows were squeezed into the other half — the owner's "large empty
   area" of 27 August 2026, on a one-part job whose only part was
   waiting. A mesh that arrives mid-view is not lost by that: job.js
   adds this class in the same instant it wires the mesh on, so the
   column and the thing that goes in it appear together. Held by
   `part-row-layout`. */
.file-body { display: grid; gap: var(--s2); }
@media (min-width: 52rem) {
  .file-body.has-assembly {
    grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
    align-items: start;
  }
}

.assembly {
  display: grid; gap: var(--s1); padding: 0 var(--s4) var(--s3);
  /* the reset control is laid over the canvas's own top-right corner,
     so the container is the thing it is positioned against, and the
     side padding it has to step over is named once here */
  position: relative;
  --assembly-pad: var(--s4);
}
.assembly-canvas {
  display: block; width: 100%; height: auto;
  aspect-ratio: 3 / 2;
  border: 1px solid var(--line);
  border-radius: var(--radius-sm);
  background: var(--panel-sunken);
  /* the finger that turns the model must not also scroll the page, and
     the mouse that turns it must not select the words around it */
  touch-action: none;
  -webkit-user-select: none;
  user-select: none;
  cursor: grab;
}
.assembly-canvas:active { cursor: grabbing; }
/* owner 01.11.2026: the one sentence a 3D view waiting for the server
   shows in its frame (assembly3d.js waitForServer) */
.assembly-retry {
  position: absolute; left: 0; right: 0; top: 50%; transform: translateY(-50%);
  margin: 0; padding: 0 var(--s3); text-align: center; pointer-events: none;
  color: var(--th-soft, var(--ink-soft)); font-size: 0.86rem;
}
.assembly-retry[hidden] { display: none; }

/* Put the view back where it started (owner, VC3o). A double-click has
   always done this and nothing on the screen said so; the same action
   is now a control the reader can SEE, reach with the keyboard and read
   the name of. It sits over the canvas's own corner rather than under
   it, because a button in the flow would move the picture down by its
   own height in a card whose height the drawing beside it fixes.

   It is a real <button> with real text in it, so Tab reaches it and a
   screen reader says what it does; only the glyph is decoration. */
.assembly-reset {
  position: absolute; z-index: 1;
  top: var(--s2); right: calc(var(--assembly-pad) + var(--s2));
  display: flex; align-items: center; justify-content: center;
  min-width: 2rem; min-height: 2rem;
  margin: 0; padding: var(--s1) var(--s2);
  font: inherit; font-size: 1rem; font-weight: 400; line-height: 1;
  border: 1px solid var(--line);
  border-radius: var(--radius-sm);
  background: var(--panel); color: var(--ink-soft);
  /* the canvas below swallows the pointer for the orbit; this one is
     the reader's way back and must keep its own arrow */
  cursor: pointer;
  opacity: 0.85;
}
.assembly-reset:hover { opacity: 1; color: var(--accent); filter: none; }
/* W-part3d: isolate the shown part, at the canvas's own top-LEFT corner
   so it never sits over the reset control opposite it. It is the same
   kind of thing as the reset button — a real <button> the keyboard
   reaches, laid over the canvas rather than in the flow so it does not
   push the picture down — and it is only rendered on the maximized
   view's inset, where one part is the subject. aria-pressed is what a
   screen reader reads for its state; the glyph is decoration. */
.assembly-solo {
  position: absolute; z-index: 1;
  top: var(--s2); left: calc(var(--assembly-pad) + var(--s2));
  display: flex; align-items: center; justify-content: center;
  min-width: 2rem; min-height: 2rem;
  margin: 0; padding: var(--s1) var(--s2);
  font: inherit; font-size: 1rem; font-weight: 400; line-height: 1;
  border: 1px solid var(--line);
  border-radius: var(--radius-sm);
  background: var(--panel); color: var(--ink-soft);
  cursor: pointer;
  opacity: 0.85;
}
.assembly-solo:hover { opacity: 1; color: var(--accent); filter: none; }
/* Pressed: this part is the whole picture, so the control reads as held
   down rather than as one more thing to press. */
.assembly-solo[aria-pressed="true"] {
  background: var(--accent); color: var(--panel);
  border-color: var(--accent); opacity: 1;
}
/* A finger needs the site's whole tap target; a mouse does not, and a
   44 px square over a 320 px inset canvas would cover the model. */
@media (pointer: coarse) {
  .assembly-reset { min-width: var(--tap); min-height: var(--tap); }
  .assembly-solo { min-width: var(--tap); min-height: var(--tap); }
}
/* The one line a browser that will not draw gets instead of the canvas.
   Help text and not an error: nothing here is broken, the browser
   simply will not draw, and a red banner would be a lie about a
   picture nobody was promised. It stands only where a mesh really
   exists — a file with no assembly still shows nothing at all. */
.assembly-fallback { margin: 0; max-width: 44ch; }

/* The same view again in the maximized preview, in its own lane at the
   left edge with the file-and-assembly tree under it. The lane's width
   is `--viewer-side`, which is also what pushes the previous-arrow
   clear of it — see the dialog rule above. */
.viewer-side {
  position: relative; z-index: 3;
  width: var(--viewer-side);
  display: flex; flex-direction: column; gap: var(--s2);
  padding: var(--s3);
  background: var(--panel);
  border-right: 1px solid var(--line);
  box-shadow: var(--shadow);
  overflow: hidden;
}
.viewer-side-toggle {
  flex: none; align-self: flex-start;
  min-width: var(--tap); min-height: var(--tap);
  padding: var(--s2); font-size: 1.1rem; line-height: 1;
}
.viewer-side-body {
  display: flex; flex-direction: column; gap: var(--s3);
  flex: 1 1 auto; min-height: 0;
}
/* Fix #3: the 3D inset keeps its size at the TOP of the fixed left lane
   and never shrinks, so it stays pinned while the tree below it (and the
   drawing beside it, in its own scrolling panel) moves. The column itself
   is already fixed to the screen's edge — see `.viewer-side` — so the
   inset does not travel with the sheet. */
.assembly-inset { padding: 0; --assembly-pad: 0rem; flex: none; }
.stagework .assembly-inset { flex: 3 1 14rem; min-height: 6rem; max-height: 42vh; display: block; }
.stagework .assembly-inset .assembly-canvas { display: block; width: 100%; height: 100%; aspect-ratio: auto; max-height: none; min-height: 0; }

/* The whole batch's tree, scrolled INSIDE the column when it is taller
   than the lane — the lane's width is fixed by the rule above and
   nothing in here may argue with it, which is why every name that could
   be longer than the column is cut with an ellipsis and carries its
   full text in a `title` instead of being allowed to push. */
/* The part list keeps its scroll to itself. This is the pane the
   owner's screenshot was taken on: it is the tallest thing in the
   overlay, so it is the one a reader reaches the end of. */
.viewer-tree {
  overflow: auto; min-height: 0; font-size: 0.85rem;
  overscroll-behavior: contain;
}
.viewer-tree .side-file + .side-file { margin-top: var(--s3); }
.viewer-tree .file-name {
  font-weight: 600; margin: 0 0 var(--s1);
  overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
.viewer-tree ul { list-style: none; margin: 0; padding: 0; }
.viewer-tree li {
  display: flex; margin: 0;
  border-radius: var(--radius-sm);
}
/* Every row is a button, so a part can be chosen with the keyboard as
   well as the mouse — but it must read as a line of a tree and not as
   one of the page's accent-coloured buttons, so everything the base
   button rule sets is given back here. The padding moved off the list
   item and onto the control, so the whole width of the row is the
   thing that answers to a click. */
.viewer-tree .tree-part {
  flex: 1 1 auto; min-width: 0; min-height: 0;
  display: flex; gap: var(--s2); align-items: baseline;
  margin: 0; padding: var(--s1) var(--s2);
  border: 0; border-radius: var(--radius-sm);
  background: transparent; color: inherit;
  font: inherit; font-weight: inherit; text-align: left;
  cursor: pointer;
}
.viewer-tree .tree-part:hover {
  background: var(--panel-sunken); filter: none;
}
/* C.211-B5: a row the plate card has chosen (kindcard.js, data-kind-chosen)
   wears the current row's look, so the list and the 3D view show one set */
.viewer-tree li[aria-current="true"],
.viewer-tree li[data-kind-chosen="true"] {
  background: var(--accent-soft); color: var(--accent); font-weight: 650;
}
.viewer-tree li[aria-current="true"] .tree-part:hover,
.viewer-tree li[data-kind-chosen="true"] .tree-part:hover {
  background: transparent;
}
.viewer-tree .part-n { flex: none; color: var(--ink-faint); }
.viewer-tree .part-name {
  flex: 1 1 auto; min-width: 0;
  font-family: var(--mono);
  overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
/* #155a: live status, sized for the narrow lane rather than the page's
   usual pill — the lane is a list to navigate by first, and a full-size
   pill on every row would crowd out the name it sits beside. */
.viewer-tree .pill {
  flex: none; font-size: 0.7rem; padding: 0 var(--s1);
}
/* A file that holds one solid is ONE row, the way it is one row in the
   uploaded-files listing: the file's own name, with its part number in
   front of it and the part's name in the tooltip. */
.viewer-tree .tree-part .file-name {
  flex: 1 1 auto; min-width: 0; margin: 0; font-weight: 600;
}

/* The archive's own contents, on the job page and in the manual. A file
   name is not prose: it gets the monospace face, it may be longer than
   its column, and it breaks inside the word rather than pushing the
   whole page sideways. */
.filelist { list-style: none; margin: var(--s3) 0 0; padding: 0; }
.filelist li {
  margin: 0;
  padding: var(--s2) 0;
  border-top: 1px solid var(--line);
}
.filelist code {
  font-family: var(--mono); font-size: 0.85rem;
  overflow-wrap: anywhere;
}
.filelist .muted { display: block; font-size: 0.85rem; }

/* -- the admin area ------------------------------------------------- */

/* Deliberately the same vocabulary as the customer pages: cards,
   tables, pills and the one button style. An operator area that looked
   like a different product would be a second design to maintain, and
   this one has exactly one user. */

.admin-bar {
  display: flex; flex-wrap: wrap; gap: var(--s2) var(--s4);
  align-items: center; padding: var(--s3) 0;
  border-bottom: 1px solid var(--line); margin-bottom: var(--s5);
}
.admin-bar a { color: var(--ink-soft); font-weight: 600; }
.admin-bar a:hover { color: var(--accent); }
.admin-bar a[aria-current="page"] { color: var(--accent); }
.admin-bar form { margin-left: auto; }

.counts { list-style: none; padding: 0; margin: 0; display: grid;
  gap: var(--s3); grid-template-columns: repeat(auto-fit, minmax(9rem, 1fr)); }
.counts li {
  border: 1px solid var(--line); border-radius: var(--radius);
  background: var(--panel); padding: var(--s3) var(--s4);
}
.counts strong { display: block; font-size: 1.6rem; letter-spacing: -0.02em; }
.counts span { color: var(--ink-faint); font-size: 0.85rem; }

.button-danger { background: var(--bad); }
.button-danger:hover { filter: brightness(1.08); }

/* W-precontain (item 6): this class dresses both a one-line <code> (an
   API key, a minted secret) and a multi-line <pre> (a stored message
   body, a problem report's settings JSON, its consent text) — and a
   <pre> ignores `word-break` entirely, because its own user-agent
   default (`white-space: pre`) refuses to wrap at all, whitespace or
   not. A very long unbroken run inside one — a base64 logo, a long JSON
   value with no spaces of its own — used to run straight off the edge
   of its box (the "Einstellungen" panel on the problem-report view,
   owner-reported) instead of stopping at it. `pre-wrap` keeps every
   `<pre>`'s real newlines (a JSON pretty-print stays readable) while
   allowing a wrap the old bare `pre` refused; `overflow-wrap: anywhere`
   is what actually breaks a run with no natural break point at all,
   `word-break: break-all` kept as the same fallback for a browser too
   old for `anywhere`; `overflow-x: auto` is the last resort so nothing
   this misses can still push the page itself wider than the viewport. */
.secret {
  font-family: var(--mono);
  white-space: pre-wrap;
  overflow-wrap: anywhere;
  word-break: break-all;
  background: var(--panel-sunken); padding: var(--s3);
  border-radius: var(--radius); display: block;
  max-width: 100%; overflow-x: auto;
}

tr.overdue td { background: var(--bad-soft); }

/* -- misc ---------------------------------------------------------- */

.stack > * + * { margin-top: var(--s4); }
/* ...but a HEADING inside a stack keeps the heading rhythm, not the
   stack's own spacing. `.stack > * + *` carries class specificity and
   would otherwise outrank the bare `h2` selector — which is the very
   defect the heading law exists to remove: a section header whose air
   depends on what it happens to sit inside. These are not a second
   answer, they are the SAME two tokens the law states, restated only to
   win the cascade, and the gate holds that this stylesheet gives each
   heading level exactly one value. */
/* The same one value the bare h2 rule states, restated to win the
   cascade against `.stack > * + *` — the same token, never a second
   number (round 8: it is the named rhythm token now, like every
   other heading gap on this site). */
.stack > h2 { margin-top: var(--rhythm-heading); }
.stack > h3, .stack > h4 { margin-top: var(--rhythm-between); }
.stack > h1:first-child, .stack > h2:first-child,
.stack > h3:first-child, .stack > h4:first-child { margin-top: 0; }

/* THE BUTTON RHYTHM LAW (owner, 24.08.).

   A button keeps the standard vertical rhythm above AND below it,
   wherever it stands.

   What the owner met on the dashboard: "Ihre Aufbewahrung steht auf 7
   Tage." sitting directly on top of the "Neuer Auftrag" button with
   almost no gap, and "Zum Konto" hugging it underneath. Neither is a
   mistake in that column — it is arithmetic. `.help` is
   `margin: var(--s1) 0 0`, so its bottom margin is ZERO; `p` is
   `margin: 0 0 var(--s4)`, so its top margin is ZERO; and nothing in
   this stylesheet ever gave a button any margin at all. A help sentence
   above a button therefore collapsed to a nought-pixel gap every time,
   on every page, and the dashboard was simply where the owner happened
   to be looking.

   So a paragraph whose job is to carry a button is given the rhythm on
   both sides, from the same scale. `:has()` is what lets the rule ask
   "is this paragraph a button's paragraph?" without every template
   having to remember a class — it is registered in check_all.py's
   `_HAS_ALLOWED`, which is where a new one has to be declared. */
p:has(> .button, > .button-ghost, > button) { margin-block: var(--rhythm-between); }
.row { display: flex; flex-wrap: wrap; gap: var(--s4); align-items: center; }
.muted { color: var(--ink-faint); font-size: 0.9rem; }

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.001ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.001ms !important;
    scroll-behavior: auto !important;
  }
  .tile[data-state="working"] .frame::after,
  .tile[data-redrawing="true"] .frame::after {
    animation: none;
    background: var(--accent-soft);
    opacity: 0.4;
  }
  /* the packing tile keeps its own colour and loses its motion, so a
     reader who asked for stillness can still tell the two states apart */
  .tile[data-state="packing"] .frame::after {
    animation: none;
    background: var(--good-soft);
    opacity: 0.4;
  }
}

/* the usage-statistics dashboard chart (V31) — inline SVG the server
   wrote, no external asset; colours from the shared custom properties so
   the bars track light and dark like everything else. */
.stats-chart { margin: var(--s3) 0 var(--s4); }
.stats-chart svg { display: block; max-width: 100%; height: auto; }
.chart-legend {
  display: flex; flex-wrap: wrap; gap: var(--s4);
  margin: 0 0 var(--s2); color: var(--ink-soft); font-size: 0.85rem;
}
.chart-legend .legend-key { display: inline-flex; align-items: center; gap: var(--s2); }
.chart-legend .swatch {
  display: inline-block; width: 0.9rem; height: 0.9rem;
  border-radius: var(--radius-sm);
}
.chart-legend .swatch-units { background: var(--accent); }
.chart-legend .swatch-previews, .chart-legend .swatch-downloads { background: var(--good); }

/* W-chartaxes (item 5): the y-axis gridlines and both axes' printed
   labels — light on purpose, so the bars stay the thing the eye lands
   on and the numbers are there to be read against, not the picture. */
.chart-gridline { stroke: var(--line); stroke-width: 1; }
.chart-axis-line { stroke: var(--line-strong); stroke-width: 1; }
.chart-axis-label {
  fill: var(--ink-faint); font-size: 9px; font-family: var(--font);
}
.chart-axis-y { text-anchor: end; dominant-baseline: middle; }
.chart-axis-x { text-anchor: middle; }
.chart-empty { margin: 0 0 var(--s2); }

/* ==================================================================
   THE TITLE BLOCK (Planstempel, owner order 05.09.2026)

   One widget, two mounts — the stage between recognising the parts and
   drawing, and the account page, which renders the stamp as it prints
   and edits its defaults in place. The markup is one partial and these
   are its styles; nothing here is per-page and no template states a
   length of its own (the rhythm-scale gate holds that).

   THE THREE VISUAL STATES ARE THE POINT (owner ruling, section 12). A
   reader has to be able to tell, without trying, which fields are his
   to type in, which carry a proposal he may lay a hand on, and which
   the system fills. So the three are three classes with three real
   differences — a normal input, an accent-tinted one with a pencil and
   a hint word, and a row that is not an input at all — rather than one
   class with a modifier nobody can see.
   ================================================================== */

.stamp-widget { display: block; }

/* Two columns where there is room, one on a phone, and the same field
   grid every other form on this site uses so the rhythm is the shared
   one and not a second system. */
.stamp-fields { align-items: start; }
/* batch 38: on a job the job's own group stands first, and a line closes
   it, so the account's defaults under it are not read as "this job
   only" (the redesign gives that group no heading of its own) */
.stamp-job-group {
  padding-bottom: var(--rhythm-between);
  margin-bottom: var(--rhythm-between);
  border-bottom: var(--hairline) solid var(--line);
}

/* MEMORY and free fields: an ordinary input. Named so the gate can see
   the three states are distinct, and so a change to "ordinary" happens
   in one place rather than by default in three. */
.stamp-field-memory > label.field > input {
  background: var(--panel);
  border: 1px solid var(--line-strong);
}

/* SUGGEST fields carrying an UNTOUCHED proposal. Accent tint, an accent
   edge, and the pencil that says the value is there to be written over.
   The pencil is a background glyph rather than an element, so it cannot
   be read out as content by a screen reader, which has the hint word
   instead. */
.stamp-field-suggest > label.field > input {
  background: var(--panel);
  border: 1px solid var(--line-strong);
}
.stamp-field.stamp-proposal > label.field > input {
  background: var(--accent-soft);
  border: 1px solid var(--accent);
  color: var(--ink);
}
/* the proposal's pencil (C.58j: the icon set's own, in the markup) shows
   while the field still holds an untouched proposal */
.stamp-proposal-mark { display: none; color: var(--accent); margin-left: var(--s1); }
.stamp-field.stamp-proposal .stamp-proposal-mark { display: inline-block; }
.stamp-field .stamp-hint {
  color: var(--accent);
  font-weight: 600;
}
/* The hint belongs to its own field and disappears with the class the
   script removes; a field that is not carrying a proposal never renders
   one, so there is nothing here to hide. */
.stamp-field:not(.stamp-proposal) .stamp-hint { display: none; }

/* THE SAVED VALUES under a Plankopf field (owner, 22.09.2026).

   The list belongs to the field it opens under, so the field's own box
   is the positioning context and the list is exactly its width — which
   is also what makes it safe on a phone: it cannot be wider than the
   column it sits in, and it opens downward under the box rather than
   over anything the reader is reading. The look is the site's one
   floating-list look (.pencil-menu), because a second popup style would
   be a second popup style. */
.stamp-field { position: relative; }
.stamp-values-list {
  position: absolute; left: 0; right: 0; top: 100%; z-index: 8;
  margin: var(--s1) 0 0; padding: var(--s1); list-style: none;
  max-height: 17rem; overflow-y: auto;
  background: var(--panel); border: 1px solid var(--line);
  border-radius: var(--radius-sm); box-shadow: var(--shadow-lift);
}
.stamp-values-list li { margin: 0; }
.stamp-values-list button {
  display: block; width: 100%; margin: 0; padding: var(--s2) var(--s3);
  border: 0; border-radius: var(--radius-sm); background: transparent;
  color: inherit; font: inherit; text-align: left; cursor: pointer;
  overflow-wrap: anywhere;
}
.stamp-values-list button:hover,
.stamp-values-list button.is-active {
  background: var(--panel-sunken); filter: none;
}
/* "WERTE VERWALTEN" (owner 01.11.2026): the saved values open in a LAYER
   of their own, the kit's popup, over the settings popup - never as a
   list that fills it. The link is the kit's quiet action standing at the
   end of the field's label line; the layer is as wide as the popup it
   opens over and no taller (stampwidget.js measures the popup and sets
   the two custom properties), and a phone's layer is the whole window.
   The title, the way out and the foot are the kit popup's own; what is
   written here is the layer's body: the filter on top, the values
   scrolling inside their own box. */
/* under a finger the link keeps the tap size, on its own line under the
   field so its height lies over no input */
@media (pointer: coarse) {
  html .stamp-field[data-stamp-remembered] > .stamp-values-manage-link {
    position: static; display: flex; width: fit-content; margin-left: auto;
    min-height: var(--tap); padding-block: 0; align-items: center;
  }
}
.stamp-field[data-stamp-remembered] > .stamp-values-manage-link {
  position: absolute; top: 0; right: 0; margin: 0;
  min-height: 0; padding: 0 0 var(--s1) var(--s3);
  font-size: 0.9rem; line-height: 1.4;
}
.kit-pop.kit-pop-values:not(.kit-pop-picture) {
  width: var(--values-w, min(var(--pop-width-wide), calc(100% - var(--pop-gutter))));
  /* the layer's height never follows its list: its rows arrive after it
     opens and a filter empties them, and a foot that moved then left a
     row's Löschen where Fertig had stood (measured under load 07.11.2026) */
  height: var(--values-h, auto);
  max-height: var(--values-h, var(--pop-height-cap));
}
.kit-pop-values .kit-pop-body {
  display: flex; flex-direction: column; overflow: hidden;
  flex: 1 1 auto;
}
.stamp-values-layer {
  display: flex; flex-direction: column; min-height: 0; flex: 1 1 auto;
  gap: var(--s2);
}
.stamp-values-scroll {
  flex: 1 1 auto; min-height: 0; overflow-y: auto;
  overscroll-behavior: contain;
}
/* A PHONE'S LAYER IS THE WHOLE WINDOW, not the kit's sheet from the foot:
   under the kit's one breakpoint, and on the job page's phone layout at
   any width (`body.phone-job`, which the kit's own sheet rule names
   too); while the screen keyboard is open it is as tall as the part
   of the screen the keyboard leaves (the kit's `--vv-height`). */
@media (max-width: 35rem) {
  .kit-pop.kit-pop-values:not(.kit-pop-picture) {
    width: auto; height: 100dvh; max-height: min(100dvh, var(--vv-height, 100dvh));
    margin: 0; inset: 0; border-radius: 0; border: 0;
  }
}
body.phone-job .kit-pop.kit-pop-values:not(.kit-pop-picture) {
  width: auto; height: 100dvh; max-height: min(100dvh, var(--vv-height, 100dvh));
  margin: 0; inset: 0; border-radius: 0; border: 0;
}
.stamp-values-filter { width: 100%; flex: none; }
.stamp-values-held { margin: 0 0 var(--s2); padding: 0; list-style: none; }
/* A ROW IS A VALUE AND A GROUP OF ACTIONS, and the group wraps as one.
   The two actions were loose children of the row once: on a phone
   "Löschen" alone wrapped under the next value, and forbidding the wrap
   to cure that squeezed the value in the Plankopf's narrow second
   column down to a two-letter stack ("Ha / lle / nb / ad"). With the
   actions grouped and the value given a real basis, a row wide enough
   reads value-then-actions and a row too narrow reads value on one line
   and both actions under it. */
.stamp-values-held li {
  display: flex; flex-wrap: wrap; align-items: baseline;
  gap: var(--gap-icon-label);
  margin: 0; padding: var(--s1) 0; border-bottom: 1px solid var(--line);
}
.stamp-values-held-value {
  flex: 1 1 8rem; min-width: 0; overflow-wrap: anywhere;
}
.stamp-values-held-actions {
  flex: 0 0 auto; margin-left: auto;
  display: flex; gap: var(--gap-icon-label);
}
/* The actions beside a saved value are the page kit's buttons (C.106,
   PAGE_DESIGN_LAWS section 7): Bearbeiten and Abbrechen secondary,
   Speichern primary, Löschen the kit's destructive button confirmed in
   place. Their look is kit-action.css's; this rule only takes the outer
   margin off inside the row. */
.stamp-values-action { margin: 0; }
.stamp-values-held-edit { flex: 1 1 10rem; }
.stamp-values-empty { margin: 0 0 var(--s2); }

/* LOCKED rows: unmistakably not an input. No box, no border, no cursor
   — a label and a value, the way the cell reads on the sheet. */
.stamp-locked-list { display: grid; gap: var(--rhythm-within); }
.stamp-locked-row {
  display: flex; flex-wrap: wrap; gap: var(--gap-icon-label);
  align-items: baseline;
}
.stamp-locked-row > dt { color: var(--ink-soft); }
.stamp-locked-row > dd { margin: 0; font-variant-numeric: tabular-nums; }
.stamp-field-locked > dd { color: var(--ink); }

/* The saved values, managed inside the field itself (section 13): no
   separate table anywhere on the site. One row per remembered value,
   its own box and its own x. */
.stamp-memory-list { list-style: none; padding: 0; display: grid;
                     gap: var(--rhythm-within); }
.stamp-memory-entry {
  display: flex; flex-wrap: wrap; gap: var(--s2); align-items: end;
}
.stamp-memory-entry > label.field { flex: 1 1 12rem; }
.stamp-memory-forget { min-width: var(--tap); }

/* The lowest row of the block. It always prints and only its wording is
   replaceable, so it reads as prose rather than as one more category. */
.stamp-disclaimer > label.field > input {
  background: var(--panel);
  border: 1px solid var(--line-strong);
}
.stamp-disclaimer-restore { font-size: 0.9rem; }

/* QA11 item 19: a field's own FAQ attaches to the field's visual group
   rather than reading as a new section. Tight top spacing (within-group,
   not the section gap an <h3> otherwise brings) and a quiet question so it
   sits just under the field's explanation. The reusable proximity pattern
   for a field-level FAQ across the stamp and billing sections. */
.field-faq { margin-top: var(--s3); }
.field-faq h3 {
  margin: 0 0 var(--s1);
  font-size: 0.95rem;
  font-weight: 650;
  color: var(--ink-soft);
}

/* The stage's arrival (section 3). It slides in rather than appearing —
   the script adds the class for one frame and takes it off, so a reader
   with the script blocked simply has the widget, already in place. */
.stamp-widget-arriving {
  opacity: 0;
  transform: translateY(var(--s5));
}
.stamp-widget {
  transition: opacity 220ms ease-out, transform 220ms ease-out;
}
@media (prefers-reduced-motion: reduce) {
  .stamp-widget { transition: none; }
  .stamp-widget-arriving { opacity: 1; transform: none; }
}

/* ==================================================================
   THE ACCOUNT PAGE'S PINNED INDEX (owner order, section 14)

   One chip per section, pinned to the top as the page scrolls, the chip
   of whatever section is in view lit. On a phone the row scrolls
   sideways rather than wrapping into a block that would take half the
   screen before the settings begin. Without the script it is a row of
   ordinary anchor links, which is what it must remain.
   ================================================================== */

.settings-index {
  position: sticky;
  top: 0;
  z-index: 3;
  display: flex;
  gap: var(--s2);
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scrollbar-width: thin;
  background: var(--paper);
  border-bottom: 1px solid var(--line);
  padding: var(--s2) 0;
}
.settings-index > a {
  flex: 0 0 auto;
  padding: var(--s1) var(--s3);
  border: 1px solid var(--line-strong);
  border-radius: var(--radius);
  background: var(--panel);
  color: var(--ink-soft);
  text-decoration: none;
  white-space: nowrap;
}
.settings-index > a:hover { color: var(--ink); }
.settings-index > a.is-active {
  background: var(--accent-soft);
  border-color: var(--accent);
  color: var(--accent);
  font-weight: 600;
}
/* A pinned bar and an anchor jump disagree by exactly the bar's own
   height, so every section it points at reserves that much scroll
   margin. Stated once, on the sections themselves, rather than as a
   magic offset inside the script. */
.settings-index ~ * :target,
.wrap > h2[id],
.wrap > section[id],
.wrap > div[id] { scroll-margin-top: var(--s8); }

/* ===================================================================
   THE JOB PAGE, OPTION E (JOBPAGE_SPEC.md sections 15-19, owner
   12.09.2026): the maximised preview IS the page. A pinned top bar of
   facts, the sheet on a stage with the neighbouring sheets as ghost
   tiles either side, and the always-visible right column: 3D
   navigator, cue line, parts list, download dock. The stage and the
   column reuse every `.viewer*` rule the maximised dialog had; what
   differs is stated here and only here: the stage is a grid cell, not
   a fixed overlay, and the column is the grid's second track, whose
   width is the one lane variable (`--viewer-side`) the arrows' law
   reads.
   =================================================================== */
/* the job page uses the whole width of the screen (owner 12.09.) */
.wrap-wide { width: calc(100% - 2 * var(--s3)); margin-inline: auto; }

/* the top bar (15.1): one line of facts, pinned under the site header */
.jobtop {
  position: sticky; top: var(--header-offset); z-index: 6;
  background: var(--paper); padding-block: var(--s2) var(--s1);
  border-bottom: 1px solid var(--line);
}
.jobtop-line {
  display: flex; flex-wrap: wrap; align-items: center; gap: var(--s2) var(--s4);
}
.jobtop h1 { margin: 0; font-size: 1.1rem; }
/* home-9 A: the sample's own line above the job bar - what the page is,
   the house, the day it was drawn, the free files, and the reader's own
   upload as the one strong action */
.sample-top {
  background: var(--accent-soft);
  border-bottom: 1px solid var(--line);
  padding-block: var(--s2);
}
.sample-top-line {
  display: flex; flex-wrap: wrap; align-items: center; gap: var(--s2) var(--s3);
}
.sample-top-text { flex: 1 1 24rem; margin: 0; }
.sample-badge {
  display: inline-block;
  padding: 0 var(--s2);
  border-radius: 999px;
  background: var(--accent);
  color: var(--paper);
  font-weight: 600;
  font-size: var(--fs-small);
}
.sample-top-help { margin: var(--s1) auto 0; }
.dock-sample-price > [hidden] { display: none; }
.meta-inline { display: flex; flex-wrap: wrap; gap: var(--s1) var(--s4); margin: 0; }
.meta-inline > div { display: flex; align-items: center; gap: var(--s1); margin: 0; }
.meta-inline dt { color: var(--ink-faint); font-size: 0.8rem; font-weight: 500; }
.meta-inline dd { margin: 0; font-size: 0.85rem; }
.meta-inline .job-id-full { font-family: var(--mono); font-size: 0.8rem; }
.meta-inline .copy-button { padding: 0 var(--s2); min-height: 1.6rem; font-size: 0.75rem; }
/* C.74: "Jetzt löschen" beside the deletion line — the site's destructive
   class at the size of the line it stands in, and "Gelöscht." in its
   spot once the job is gone */
.meta-inline .job-delete-button { padding: 0 var(--s2); min-height: 1.6rem; font-size: 0.75rem; margin: 0; }
.meta-deletion dd { display: flex; align-items: center; gap: var(--s1); flex-wrap: wrap; }
.job-delete-result { font-size: 0.75rem; font-weight: 600; color: var(--ink-soft); padding: 0 var(--s2); }
.job-progress-line { margin: 0 0 0 auto; color: var(--ink-soft); font-size: 0.9rem; }
.jobtop .meta-forms { margin-top: var(--s2); }

/* JOB PAGE 9 — THE JOB BAR (scope 1.1, J1/J5/J6): one line at a desk
   width - the title, the pill, the sentence with the next line under it,
   the deletion moment while it is near, and „Mehr" at the right. The
   menu is the kit's (`data-menu`, law 21): its body lies over the page
   and moves nothing. */
@media (min-width: 60.0625rem) {
  /* one line at a desk width (J6); narrower, the line wraps as before, so
     a phone never meets a line wider than its glass */
  .jobtop-line { flex-wrap: nowrap; }
}
.jobtop .jobbar-title { flex: none; white-space: nowrap; }
.jobtop #job-status { flex: none; }
.jobbar-words {
  display: flex; flex-direction: column; min-width: 0; flex: 1 1 auto;
  line-height: 1.25;
}
.jobbar-words .job-progress-line { margin: 0; color: var(--ink); font-size: 0.9rem; }
.jobbar-words .job-next-line { margin: 0; font-size: 0.8rem; color: var(--ink-soft); }
/* the bar's one line at a desk width (J6): where the sentence or the next
   line is cut, its whole words are its title (job.js, every frame);
   narrower, both wrap */
@media (min-width: 60.0625rem) {
  .jobbar-words .job-progress-line { white-space: nowrap; overflow: hidden; text-overflow: ellipsis; }
  .jobbar-words .job-next-line { white-space: nowrap; overflow: hidden; text-overflow: ellipsis; }
}
.jobbar-words .job-next-line[hidden] { display: none; }
.jobbar-deletion { flex: none; font-size: 0.8rem; color: var(--ink-soft); white-space: nowrap; }
.jobbar-menu { flex: none; margin-left: auto; }
.jobbar-menu > summary {
  list-style: none; cursor: pointer; display: inline-flex; align-items: center; gap: var(--s1);
  min-height: 2rem; padding: 0 var(--s3);
}
.jobbar-menu > summary::-webkit-details-marker { display: none; }
.jobbar-menu > summary .kit-icon, .jobbar-menu > summary svg { width: 1rem; height: 1rem; }
.jobbar-menu-body {
  width: min(24rem, calc(100vw - 2 * var(--s3)));
  display: grid; gap: var(--s2); padding: var(--s3);
  background: var(--paper); border: 1px solid var(--line);
  border-radius: var(--radius); box-shadow: var(--shadow);
}
.jobbar-menu-body .meta-inline { flex-direction: column; flex-wrap: nowrap; align-items: stretch; gap: var(--s2); }
.jobbar-menu-body .meta-inline > div { justify-content: space-between; flex-wrap: wrap; }
.jobbar-menu-body .meta-inline dt { display: inline; }
.jobbar-links, .jobbar-actions {
  display: flex; flex-wrap: wrap; gap: var(--s2);
  border-top: 1px solid var(--line); padding-top: var(--s2);
}
.jobbar-actions .jobbar-disabled { display: grid; gap: var(--s1); }
.jobbar-actions .jobbar-why { margin: 0; font-size: 0.75rem; }
.jobbar-item { min-height: 2rem; }
.jobtop { --jobbar-progress-h: 3px; }
.jobtop .jobbar-progress {
  height: var(--jobbar-progress-h); margin-top: var(--s1); border-radius: 0; background: var(--line);
}
.jobtop .jobbar-progress[hidden] { display: none; }
/* the line stands down, its place stays: gone from the flow it lifted the
   whole stage by its 7 px at the finish, under the reader's eye (a finished
   batch never moves the reader; round 7, 03.11.2026). The page's one
   [hidden] rule outranks everything, so the line above keeps the room */
.jobtop-line:has(+ .jobbar-progress[hidden]) { padding-bottom: calc(var(--jobbar-progress-h) + var(--s1)); }

/* JOB PAGE 9 — THE STAGE WHILE IT WAITS (scope 1.4): the model large in
   its host over the stage, the stage's now-sentence and the reading's
   results at its foot, the first-sheet chip, and the check strip at the
   stage's head */
.viewer-stage { position: relative; }
.stage-model-host { position: absolute; inset: 0; z-index: 2; display: flex; }
.stage-model-host[hidden] { display: none; }
/* the id outranks the panel's own sizing of the inset (.stagework
   .assembly-inset, a 290 px flex basis): in the stage the model fills */
#stage-model-host > .assembly-inset {
  flex: 1 1 auto; width: 100%; height: 100%; max-height: none; min-height: 0; margin: 0;
}
.stage-wait {
  /* owner law 13.11.2026: the 3D view stays in the side panel while the
     stage waits, so the waiting words and the guide stand in the middle
     of the empty drawing area, at a reading measure */
  position: absolute; left: 50%; top: 50%; transform: translate(-50%, -50%);
  z-index: 3; width: max-content; max-width: min(34rem, calc(100% - 2 * var(--s4)));
  text-align: center; pointer-events: none;
  display: grid; gap: var(--s1);
  padding: var(--s1) var(--s3); border-radius: var(--radius-sm);
  background: rgba(15, 20, 28, 0.72);
}
.stage-wait[hidden] { display: none; }
.stage-wait .stage-now { margin: 0; color: var(--th-ink, var(--ink)); font-size: 0.95rem; }
.stage-wait .stage-results { margin: 0; color: var(--th-faint, var(--ink-soft)); font-size: 0.85rem; }
.stage-wait .stage-results[hidden] { display: none; }
.stage-wait .stage-guide { margin: 0; color: var(--th-soft, var(--ink-soft)); font-size: 0.85rem; line-height: 1.45; }
/* owner 13.11.2026: „Weitere Zeichnungen folgen" - one quiet line at the
   drawing area's top while more drawings follow */
.stage-more {
  position: absolute; left: 50%; top: var(--s2); transform: translateX(-50%); z-index: 3;
  /* prose is never cut: in a narrow drawing area the line wraps inside its
     box (no nowrap/ellipsis); the 1em radius stays a pill on one line and
     a soft box on two */
  margin: 0; max-width: calc(100% - 2 * var(--s4)); width: max-content; text-align: center;
  padding: 2px var(--s3); border-radius: 1em; pointer-events: none;
  background: rgba(15, 20, 28, 0.72); color: var(--th-ink, var(--ink)); font-size: 0.8rem;
}
.stage-more[hidden] { display: none; }
/* owner 13.11.2026: a drawing that arrives in the empty drawing area
   fades in with a brief soft ring, so the eye notices it; with reduced
   motion it simply stands (abbundo.js arrive) */
@media (prefers-reduced-motion: no-preference) {
  .viewer-body.is-arriving { animation: stage-arrive 900ms ease-out; }
}
@keyframes stage-arrive {
  from { opacity: 0; box-shadow: inset 0 0 0 3px var(--accent); }
  50% { opacity: 1; }
  to { opacity: 1; box-shadow: inset 0 0 0 3px transparent; }
}
/* while no drawing exists the guide is the drawing area's one text: the
   part placeholder's word would stand behind it */
.stagework[data-sheets="false"] .viewer-placeholder { visibility: hidden; }
.viewer.stage .viewer-panel > .stage-check,
.stage-check {
  display: flex; align-items: center; gap: var(--s3); margin: 0;
  padding: var(--s1) var(--s3); font-size: 0.85rem;
  background: var(--th-bar, var(--paper)); color: var(--th-ink, var(--ink));
  border-bottom: 1px solid var(--th-line, var(--line));
}
.stage-check[hidden] { display: none; }
.stage-check .stage-check-go { min-height: 1.8rem; padding: 0 var(--s3); }
/* the model holds the large place: the sheet's own page-turn and part
   steps belong to the sheet and stand down with it */
.stagework.is-model-large .viewer-stage > .ghost,
.stagework.is-model-large .viewer-stage > .part-step,
.stagework.is-model-large .viewer-zoom-controls,
.stagework.is-model-large .viewer-zoom-hint { display: none; }
/* the small drawing at the panel's head (J12) */
.side-sheet { flex: none; height: 12rem; overflow: hidden; border-radius: var(--radius-sm); }
.side-sheet[hidden] { display: none; }
.side-sheet > .viewer-body { height: 100%; padding: var(--s1); display: flex; align-items: center; justify-content: center; }
.side-sheet > .viewer-body img { max-width: 100%; max-height: 100%; }
/* J10: a generated part name („p_12") reads as generated - the faint ink */
.part-name.is-generated { color: var(--ink-faint); font-style: italic; }
.stagework .part-name.is-generated { color: var(--th-faint); }
/* J4: the include control's slot on a row whose drawing does not exist yet */
.keep-slot { display: inline-block; flex: none; width: 1.55rem; height: 1.55rem; }

/* JOB PAGE 9 — THE SPLIT (scope 1.4a, J11/J12): the kit's handle fills
   the grid's gap between the stage and the panel - a 1 px line in an
   8 px grip zone - with the swap button at its middle. It is laid out of
   the grid (absolute) and moves with the panel's width. */
.stagework[data-split-host] { position: relative; }
.split-handle {
  position: absolute; top: var(--s2); bottom: var(--s2); z-index: 8;
  right: calc(var(--s2) + var(--viewer-side)); width: var(--s2);
  cursor: col-resize; touch-action: none;
  transition: right var(--rail-ms) var(--rail-ease);
}
.split-handle::before {
  content: ""; position: absolute; top: 0; bottom: 0; left: 50%; width: 1px;
  background: var(--th-line-strong, var(--line));
}
.split-handle:hover::before, .split-handle:focus-visible::before,
.stagework.is-splitting .split-handle::before { width: 2px; background: var(--accent); }
.split-handle:focus-visible { outline: 2px solid var(--accent); outline-offset: 2px; }
.stagework.is-splitting { transition: none; user-select: none; }
.stagework.is-splitting .split-handle { transition: none; }
.split-swap {
  position: absolute; top: 50%; left: 50%; transform: translate(-50%, -50%);
  width: 1.75rem; height: 1.75rem; border-radius: 50%; padding: 0;
  border: 1px solid var(--th-line-strong, var(--line));
  background: var(--stage-button-bg, var(--paper)); color: var(--th-ink, var(--ink));
  font: inherit; font-size: 0.95rem; line-height: 1; cursor: pointer;
}
.split-swap:disabled { opacity: 0.45; cursor: default; }
/* JOB PAGE 9 round 4 (SKETCH_D7B 2.1): while the card stands, the handle
   stands at the left edge of the block card plus panel - in the 8 px the
   card keeps from the stage - and dragging it still sets the panel's
   width; the card keeps its own */
@media (min-width: 60.001rem) {
  body.kind-card-open .split-handle {
    right: calc(var(--viewer-side) + var(--kind-card-w));
  }
}
.split-swap[aria-pressed="true"] { border-color: var(--accent); color: var(--accent); }
@media (prefers-reduced-motion: reduce) {
  .split-handle { transition: none; }
}
.jobnotices { display: grid; gap: var(--s2); margin-block: var(--s2); }
.jobnotices:empty { display: none; }
.jobnotices .notice-box { margin: 0; }

/* the honest state badge's five tones (spec 8) */
.pill[data-tone="wait"] { background: var(--wait-soft); color: var(--ink-soft); }
.pill[data-tone="info"] { background: var(--accent-soft); color: var(--accent); }
.pill[data-tone="ready"] { background: var(--good-soft); color: var(--good); }
.pill[data-tone="done"] { background: var(--good-soft); color: var(--good); opacity: 0.85; }
.pill[data-tone="bad"] { background: var(--bad-soft); color: var(--bad); }

/* the pencils (spec 2) */
.meta-editable dd { position: relative; display: flex; align-items: center; gap: var(--s1); flex-wrap: wrap; }
.pencil {
  margin: 0; padding: 0 var(--s1); min-width: 1.5rem; min-height: 1.5rem;
  border: 0; background: transparent; color: var(--ink-faint);
  font: inherit; font-size: 0.9rem; line-height: 1; cursor: pointer;
  border-radius: var(--radius-sm);
}
.pencil:hover { color: var(--accent); background: var(--accent-soft); filter: none; }
.meta-saved { color: var(--good); font-size: 0.8rem; opacity: 0; transition: opacity 400ms ease; }
.meta-saved.is-shown { opacity: 1; }
/* C.195: a choice the server refused says so where the value stands */
.meta-saved.is-refused { color: var(--bad); }
.meta-forms.js-hidden { display: none; }
.pencil-menu {
  position: absolute; left: 0; top: 100%; z-index: 7;
  margin: var(--s1) 0 0; padding: var(--s1); list-style: none; min-width: 12rem;
  background: var(--panel); border: 1px solid var(--line);
  border-radius: var(--radius-sm); box-shadow: var(--shadow-lift);
}
.pencil-menu li { margin: 0; }
.pencil-menu button {
  display: block; width: 100%; margin: 0; padding: var(--s2) var(--s3);
  border: 0; border-radius: var(--radius-sm); background: transparent;
  color: inherit; font: inherit; text-align: left; cursor: pointer;
}
.pencil-menu button:hover { background: var(--panel-sunken); filter: none; }
.pencil-menu button[aria-current="true"] { font-weight: 650; color: var(--accent); }

/* THE STAGE GRID (15.2, 15.3). The column's width is the lane; hovering
   ANY part of the column widens it by layout (14.2), the stage narrows,
   nothing is covered. */
.stagework {
  display: grid; grid-template-columns: minmax(0, 1fr) var(--viewer-side);
  gap: var(--s3); align-items: stretch;
  /* C.24 (owner 14.09.2026) — THE RAIL'S ONE CLOCK. The lane's width,
     the navigator's own size, every widget height that changes with the
     width and the cross-fade of a line that re-wraps all run on these
     two values, and job.js READS them off this element instead of
     carrying a second copy of the number, so nothing can lag behind or
     overshoot the movement it belongs to. */
  /* job page 9 round 4 (S8): the clock is the hover intent's own token
     pair (the token set's --hover-move and --hover-ease) */
  --rail-ms: var(--hover-move); --rail-ease: var(--hover-ease);
  /* c248: the stage ends at the window's foot WHEN THE PAGE OPENS. Its
     height is the window less everything that stands above it, measured
     (--stage-top, job.js: the stage's own top in the page). The pinned
     stack alone (header, top bar, notices) missed every row that scrolls
     away above it - the sample page's strip - and the sheet opened with
     its lower edge under the window's foot. The floor is the phone
     stage's: the rail's body scrolls inside itself, it needs no taller
     stage. The pinned-stack sum stays as the no-script fallback. */
  height: calc(100vh - var(--stage-top, calc(var(--header-offset) + var(--jobtop-h, 0px) + var(--notices-h, 0px))) - var(--s3));
  height: calc(100dvh - var(--stage-top, calc(var(--header-offset) + var(--jobtop-h, 0px) + var(--notices-h, 0px))) - var(--s3));
  min-height: 20rem;
  transition: grid-template-columns var(--rail-ms) var(--rail-ease);
}
.viewer.stage {
  position: relative; inset: auto; margin: 0; width: auto; max-width: none;
  /* owner 13.09.: the section's height is the grid row's, DEFINITE, so
     its panel is capped by it and the sheet is sized to what is really
     there — with `auto` the panel grew past the section on a 1080-high
     window and the section clipped the chip, the zoom and the block */
  height: 100%; max-height: 100%; display: flex; padding: 0;
  background: var(--panel-sunken); border: 1px solid var(--line);
  border-radius: var(--radius); overflow: hidden; min-width: 0;
}
.viewer.stage .viewer-panel { position: relative; flex: 1 1 auto; min-width: 0; min-height: 0; height: 100%; max-height: 100%; display: flex; flex-direction: column; overflow: hidden; }
.viewer.stage .viewer-bar { flex: none; }
/* owner 13.09.: the icon-button needs no 9rem slot on the stage (that
   width was for the old dialog's worded box) — the bar's spacing is even */
.viewer.stage .viewer-slot.viewer-keep { min-width: var(--tap); }
.viewer.stage .viewer-stage {
  position: relative; flex: 1 1 auto; min-height: 0;
  display: grid; grid-template-columns: minmax(3rem, 12%) minmax(0, 1fr) minmax(3rem, 12%);
  align-items: stretch;
}
.viewer.stage .viewer-body { min-height: 0; height: 100%; max-height: 100%; grid-column: 2; overflow: hidden; }
.viewer.stage .viewer-stage { overflow: hidden; }
.viewer.stage .ghost-prev { grid-column: 1; }
.viewer.stage .ghost-next { grid-column: 3; }
/* the ghosts (15.2): a faded neighbour that IS the step control */
.ghost {
  position: relative; margin: 0; padding: 0; border: 0; background: transparent;
  cursor: pointer; overflow: hidden; min-width: 0;
}
.ghost[hidden] { visibility: hidden; }
.viewer .ghost .ghost-img {
  position: absolute; top: 10%; height: 80%; width: auto; max-width: none;
  opacity: 0.35; filter: saturate(0.6);
  transition: opacity 200ms ease, transform 200ms ease;
}
.viewer .ghost-prev .ghost-img { right: 0; -webkit-mask-image: linear-gradient(to left, #000, transparent 85%); mask-image: linear-gradient(to left, #000, transparent 85%); }
.viewer .ghost-next .ghost-img { left: 0; -webkit-mask-image: linear-gradient(to right, #000, transparent 85%); mask-image: linear-gradient(to right, #000, transparent 85%); }
.viewer .ghost:hover .ghost-img { opacity: 0.6; }
.ghost-arrow {
  position: absolute; top: 50%; transform: translateY(-50%);
  display: flex; align-items: center; justify-content: center;
  width: var(--tap); height: var(--tap); border-radius: 50%;
  background: var(--panel); border: 1px solid var(--line-strong); color: var(--ink);
  box-shadow: var(--shadow); font-size: 1.2rem;
}
.ghost-prev .ghost-arrow { left: var(--s2); }
.ghost-next .ghost-arrow { right: var(--s2); }
.ghost:hover .ghost-arrow { color: var(--accent); }
/* THE STAGE NOTES (owner 12.09.): the batch's progress as a thin line
   under the stage bar, and the queue/progress words in the stage itself
   while the shown part has no drawing yet — the boxes above the stage
   are gone */
.viewer.stage .stage-progress { flex: none; height: 3px; border-radius: 0; background: rgba(255, 255, 255, 0.12); }
.viewer.stage .stage-progress[hidden] { display: none; }
.viewer.stage .viewer-body { position: relative; }
/* ...and the body stacks while it is saying them, because the body is a
   centring flex row for the sheet and a row would set the lines BESIDE
   the placeholder instead of under it. Asked of the same state, on the
   same element, as the rule above. */
.viewer.stage .viewer-body:has(> .viewer-placeholder:not([hidden])) { flex-direction: column; }
.extras-facts { margin-bottom: var(--s3); }

/* the glide (owner 12.09.): a copy of the clicked ghost flown over the
   stage onto the drawing's place, and one of the old drawing flown out
   to the opposite ghost — both removed the moment they land */
.viewer.stage .ghost-fly {
  position: absolute; z-index: 3; pointer-events: none; max-width: none;
  border: 1px solid #cfc9bd; border-radius: var(--radius-sm); background: #fff;
  transition: left 320ms ease, top 320ms ease, width 320ms ease, height 320ms ease, opacity 320ms ease, transform 360ms ease-in;
}
/* the page-turn (owner 12.09.): the copy of the sheet turns away about
   its edge like a page of a book; the next page is already underneath */
.viewer.stage .ghost-fly.ghost-turn { z-index: 4; box-shadow: 0 0 24px rgba(0, 0, 0, 0.35); }
/* the part chips at the stage's top and bottom edge */
/* owner 13.09.: the chips stand in the LEFT lane's corners, beside the
   sheet, never over it — nothing on the paper is covered */
.part-step {
  position: absolute; z-index: 2; left: var(--s2);
  display: inline-flex; align-items: center; gap: var(--s1);
  margin: 0; padding: 0.2rem 0.6rem; max-width: calc(12% - var(--s2));
  border-radius: 999px; font-size: 0.78rem; cursor: pointer;
  background: rgba(255, 255, 255, 0.08); border: 1px solid var(--th-line-strong); color: var(--th-ink);
}
.part-step[hidden] { display: none; }
.part-step:hover { background: rgba(255, 255, 255, 0.18); filter: none; }
.part-step-prev { top: var(--s2); }
.part-step-next { bottom: var(--s2); }
/* owner review 28.10.2026: no cut word - the step is its arrow alone,
   named for a screen reader by its own aria-label (job_next_part) */
.part-step-name { display: none; }
.viewer.stage .viewer-zoom-controls { position: absolute; right: var(--s3); bottom: var(--s3); }
/* `transform: none` is the whole of a defect the round's own screenshots
   caught: the base rule centres this hint with `left: 50%` AND a
   `translateX(-50%)`, and a rule that moves it to a corner has to undo
   both halves. Moving only the `left` left the shift standing, so on the
   stage the hint was drawn half its own width further left than the
   stage begins — clipped by the page to "…ngern zoomen", and over the
   "Nächstes Teil" chip on a dark page. A pair like this is one
   declaration and not two: whoever writes the second must take the
   first with it.
   c248: AND THE HINT NEVER LIES ON THE SHEET. Laid over the stage's foot
   it covered the opened sheet's lower edge - the title block - until the
   first zoom, while the fit had measured the whole stage. It stands in
   its own row under the stage, as the start page's hint stands under its
   frame, so the frame the sheet is fitted to (.viewer-body) is what is
   left above it. Its band is held while it is hidden or faded, so the
   sheet never jumps when the hint comes or goes. */
.viewer.stage .viewer-zoom-hint {
  position: static; flex: none; align-self: center;
  left: auto; bottom: auto; transform: none;
  margin: var(--s1) calc(max(3rem, 12%) + var(--s2)) var(--s2);
}
.viewer.stage .viewer-zoom-hint[hidden] { display: block; visibility: hidden; }
/* the large model takes the stage's room: no hint and no band (the rule
   that says so stated again at this rule's weight) */
.stagework.is-model-large .viewer.stage .viewer-zoom-hint { display: none; }
/* audit 01.11.2026 (K2): a card that narrows the stage takes the hint away */
@media (min-width: 60.001rem) {
  body.kind-card-open .viewer.stage .viewer-zoom-hint { display: none; }
}
/* audit 01.11.2026: the isolate toggle greyed while no part is chosen */
.assembly-solo:disabled { opacity: 0.4; cursor: default; }
.viewer-single { white-space: nowrap; }

/* THE COLUMN (15.3): the grid's second track, never fixed */
.stagework .viewer-side {
  position: relative; inset: auto; width: auto; z-index: auto;
  border: 1px solid var(--line); border-radius: var(--radius);
  box-shadow: none; min-width: 0;
}
.stagework .viewer-side-body { height: 100%; }
/* C.93 RAIL HEIGHT LAW (owner 27.09.2026): the parts list takes every
   pixel between the navigator and the foot, the foot is only as tall as
   its content, nothing in the rail leaves dead space. The list is the
   one row that grows; every other row is its content's height; the
   space between rows is the body's gap token alone (a paragraph's own
   margin would be a second, unread number); and a window shorter than
   the rows' minimum content scrolls the body rather than clipping the
   foot under the rail's edge. The gate (rail-height) reads the gap off
   this element and measures the edges. */
.stagework .viewer-side-body { overflow: hidden auto; }
.stagework .viewer-side-body > p { margin: 0; flex: none; }
.stagework .viewer-tree { flex: 2 1 8rem; min-height: 5.5rem; }
.viewer-side .cues { flex: none; font-size: 0.78rem; }
.viewer-side .listnote { margin: 0 0 var(--s2); font-size: 0.78rem; }

/* the file picker (16) */
.file-picker { flex: none; display: flex; flex-wrap: wrap; gap: var(--s1); }
.file-pick {
  margin: 0; padding: var(--s1) var(--s2); max-width: 100%;
  border: 1px solid var(--line); border-radius: 999px; background: var(--panel);
  color: var(--ink-soft); font: inherit; font-size: 0.78rem; cursor: pointer;
  overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
.file-pick:hover { color: var(--accent); filter: none; }
.file-pick[aria-pressed="true"] { background: var(--accent); color: var(--panel); border-color: var(--accent); }

/* the navigator in the column (16): mode toggle, labels, hint */
.assembly-inset { position: relative; }
.assembly-inset .assembly-solo { top: auto; bottom: calc(var(--s2) + 1.8rem); }
.explode-labels { position: absolute; inset: 0; pointer-events: none; overflow: hidden; }
.explode-label {
  position: absolute; transform: translate(-50%, -50%);
  padding: 0 0.3em; border-radius: 3px;
  /* owner 13.09.: a dark box with white figures, the same in light and
     dark mode — the light box read white-on-white in dark mode */
  background: rgb(18 26 38 / 82%); color: #fff; border: 1px solid rgb(255 255 255 / 35%);
  font-size: 0.7rem; font-weight: 650; line-height: 1.3;
}
/* the software-renderer note (owner 13.09.): shown only when the viewer
   dressed its container with that renderer's name */
.assembly-softnote { display: none; position: absolute; left: var(--s2); right: var(--s2); top: 2.6rem; margin: 0; font-size: 0.66rem; color: #d3e0f5; background: rgba(20, 32, 52, 0.55); border-radius: var(--radius-sm); padding: 0.15rem 0.4rem; text-align: center; }
[data-renderer="canvas2d"] .assembly-softnote { display: block; }
/* the retention menu's red last item (owner 13.09.): the delete door */
/* the selected part's label (owner 13.09.): the selection's accent */
.explode-label.is-current { background: var(--accent); border-color: #fff; }
/* a cluster tag: a stacked look says "several, zoom in" (owner 13.09.) */
.explode-label.is-cluster {
  font-weight: 700; padding: 0 0.45em;
  box-shadow: 2px 2px 0 rgb(18 26 38 / 82%), 2px 2px 0 1px rgb(255 255 255 / 35%);
}
.coachmark { position: absolute; inset: 0; pointer-events: none; z-index: 2; }
/* owner review 28.10.2026: the first-run hint never covers the legend or
   a control - it stands at the model's foot, above the foot's buttons */
#navigator-coach .coachmark-bubble { top: auto; bottom: 3rem; }
.coachmark-ring {
  position: absolute; left: 50%; top: 45%; width: 2.6rem; height: 2.6rem;
  margin: -1.3rem 0 0 -1.3rem; border-radius: 50%; border: 2px solid var(--accent);
  animation: coach-pulse 1.6s ease-out infinite;
}
.coachmark-bubble {
  position: absolute; left: var(--s3); right: var(--s3); top: 3rem;
  display: flex; align-items: center; gap: var(--s2);
  padding: var(--s2) var(--s3); pointer-events: auto;
  background: var(--panel); border: 1px solid var(--line);
  border-radius: var(--radius-sm); box-shadow: var(--shadow-lift); font-size: 0.8rem;
}
.coachmark-hand { font-size: 1.1rem; animation: coach-tap 1.6s ease-in-out infinite; }
.coachmark-close {
  margin: 0 0 0 auto; padding: 0 var(--s1); border: 0; background: transparent;
  color: var(--ink-faint); font: inherit; font-size: 1rem; line-height: 1; cursor: pointer;
}
.coachmark-close:hover { color: var(--ink); filter: none; }
/* owner 13.09.: the first-run bubble sits on the theatre — dark paint,
   light text, in both colour schemes, never the page's panel colour */
.stagework .coachmark-bubble {
  background: var(--stage-file-head); color: var(--stage-file-head-ink); border-color: var(--th-line-strong);
}
/* C.104: the part-colour hint stands at the model's foot, clear of the
   first-run hint's place and of the arrangement control at the top */
.paint-hint .coachmark-bubble { top: auto; bottom: 3rem; }
.stagework .coachmark-close { color: var(--th-soft); }
.stagework .coachmark-close:hover { color: var(--stage-sel-ink); }
@keyframes coach-pulse { 0% { transform: scale(0.6); opacity: 0.9; } 100% { transform: scale(1.6); opacity: 0; } }
@keyframes coach-tap { 0%, 100% { transform: translateY(0); } 50% { transform: translateY(3px) scale(0.92); } }

/* the cue line (16, 14.4) */
.cues {
  display: flex; flex-wrap: wrap; align-items: center; gap: var(--s1) var(--s2);
  margin: 0; color: var(--ink-soft); font-size: 0.8rem;
}
.cues > span { display: inline-flex; align-items: center; gap: 0.3em; cursor: default; }
.cues svg { flex: none; }
.cue-sep { color: var(--ink-faint); }
/* the cue words name the gesture the reader really has: mouse or finger */
.cue-touch { display: none; }
@media (hover: none) and (pointer: coarse) {
  .cue-mouse { display: none; }
  .cue-touch { display: inline; }
}

/* THE PARTS LIST (17): number, icon-button, name, coloured state */
.viewer-tree .file-row { border: 0; border-radius: 0; background: transparent; }
.viewer-tree .file-row > summary { padding: var(--s1) 0; min-height: 0; cursor: pointer; list-style: none; }
.viewer-tree .file-row > summary::-webkit-details-marker { display: none; }
.viewer-tree .file-row > summary::before {
  content: ""; flex: none; width: 0.5rem; height: 0.5rem;
  border-right: 2px solid var(--ink-faint); border-bottom: 2px solid var(--ink-faint);
  transform: rotate(45deg); margin-right: var(--s1); transition: transform 200ms ease;
}
.viewer-tree .file-row:not([open]) > summary::before { transform: rotate(-45deg); }
/* one line at every count: the file's name gives way by its ellipsis (its
   whole text stands in the row's title). The page's wrapping file row put
   the extras on a second line once the pill had grown by a digit, and the
   finish pushed every row of the list down by 26 px (round 7, 03.11.2026) */
.viewer-tree .side-file > .file-row > .file-name > .pill,
.viewer-tree .side-file > .file-row > .file-name > .file-extras { flex: none; white-space: nowrap; }
.viewer-tree .side-file > .file-row > .file-name {
  display: flex; flex-wrap: nowrap; align-items: center; gap: var(--s2);
  position: sticky; top: 0; z-index: 1; background: var(--panel);
  padding: var(--s1) 0; border-bottom: 1px solid var(--line);
}
.viewer-tree .file-name-text { flex: 1 1 auto; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.viewer-tree .file-parts { color: var(--ink-faint); font-size: 0.72rem; font-weight: 400; }
.viewer-tree .file-note { color: var(--bad); font-size: 0.8rem; margin: 0; }
.viewer-tree .partlist { list-style: none; margin: 0; padding: 0; }
.viewer-tree { scroll-padding-top: 2.2rem; }
.viewer-tree li { scroll-margin-top: 2.2rem; }
.viewer-tree li { align-items: center; gap: var(--s1); border-radius: var(--radius-sm); padding-right: var(--s1); }
.viewer-tree li[data-state="failed"] .part-name { color: var(--bad); }
.viewer-tree li[data-state="skipped"] .part-name { color: var(--ink-faint); text-decoration: line-through; }
.viewer-tree .part-twin { flex: none; color: var(--ink-faint); font-size: 0.72rem; }
/* C.178b: the source note of a part read from a mesh - the twin
   marker's quiet look, never a warning colour (T.12 decision 2) */
.viewer-tree .part-source { flex: none; color: var(--ink-faint); font-size: 0.72rem; }
/* C.211-B4: the small "being drawn again" symbol of a row whose plate
   changed - the twin marker's quiet look; the row's pill says the word */
.viewer-tree .part-redraw { flex: none; display: inline-flex; color: var(--ink-faint); }
.viewer-tree .part-redraw[hidden] { display: none; }
/* C.211-B2b: a plate row's two small symbols (Sichtseite, Maserung) and
   its "Bitte prüfen" marker - the twin marker's quiet look, the marker
   in the check outline's yellow family (kindcard.row_marks) */
.viewer-tree .part-kind-marks { flex: none; display: inline-flex; gap: 2px; color: var(--ink-faint); }
.viewer-tree .part-kind-marks[hidden] { display: none; }
.viewer-tree .part-kind-mark { display: inline-flex; }
.viewer-tree .part-kind-mark .kit-icon { width: 1em; height: 1em; }
.viewer-tree .part-kind-check { color: var(--ink-soft); }

/* JOB PAGE 9 round 4 (SKETCH_D7B K1-K3, K9; owner amendment 01.11.2026):
   THE PLATE CARD IS A COLUMN of the work grid, between the stage and the
   side panel. It takes its room from the stage and never lies over the
   drawing: the stage narrows by the card's width and the sheet fits itself
   into what is left. It shares the panel's surface and edge - its right
   edge IS the panel's left edge, no gap, one seam line - and runs the
   panel's full height, so it rides with the panel's edge whenever the
   panel widens. It stands while a part is selected and goes only when the
   selection is cleared: there is no fold and no tab. Its rows keep the
   page kit's 8 px rhythm and it never scrolls inside itself at 1280 x 800
   (a shorter window scrolls it rather than clipping a control). */
.stagework { --kind-card-w: min(24rem, 30vw); }
@media (min-width: 60.001rem) {
  body.kind-card-open .stagework {
    grid-template-columns: minmax(0, 1fr) var(--kind-card-w) var(--viewer-side);
    column-gap: 0;
  }
}
/* CARD REDESIGN 01.11.2026 (SLATLYN_OWNER\plans\job9\
   CARD_REDESIGN_2026-11-01.md section 3): the card's numbers are its
   tokens - a 16 px padding, a 96 px label column with a 16 px gutter (so
   two left edges: the content edge and the control edge), one control
   height (32 px for a fine pointer, the kit's tap height for a coarse
   one), the help gap between a control and its one line, and the type
   ladder (title 16/24, body and labels 14/20, help and reasons 13/20).
   The kit's own controls stand in it on the stage's dark ground: the
   card names the kit's tokens in the stage's colours, as the side note
   does, so the primary, the secondaries, the quiet way out and the
   segmented choices are the kit's (law 12), never a card's own. */
/* round 6 (02.11.2026): between a choice and the server's member answers
   the head names the new part; the lines under it still belong to the part
   chosen before, so they keep their place (no jump) but are not shown and
   cannot be pressed (kindcard.js choose sets data-kind-drawing, render clears it; a press keeps its own aria-busy and its lines) */
.kind-card[data-kind-drawing] > :not(.kind-card-head) { visibility: hidden; }
.kind-card {
  --kind-pad: var(--s4);
  --kind-label: 6rem;
  --kind-gutter: var(--s4);
  --kind-control: 2rem;
  --kind-help-gap: var(--s1);
  --kind-fs: 0.875rem;
  --kind-lh: 1.25rem;
  --kind-fs-help: 0.8125rem;
  --ink: var(--th-ink);
  --ink-soft: var(--th-soft);
  --line: var(--th-line);
  --line-strong: var(--th-line-strong);
  --panel: transparent;
  --accent: var(--stage-hover-line);
  --accent-ink: var(--th-rail);
  --accent-soft: var(--th-sel);
  position: relative; z-index: 1; min-width: 0; min-height: 0;
  box-sizing: border-box; height: 100%; max-height: 100%; overflow: auto;
  margin-left: var(--s2);
  display: flex; flex-direction: column; gap: var(--s4);
  padding: var(--kind-pad);
  border: 1px solid var(--th-line); border-right: 0;
  border-radius: var(--radius-sm) 0 0 var(--radius-sm);
  background: var(--th-rail);
  color: var(--th-ink);
  font-size: var(--kind-fs); line-height: var(--kind-lh);
  box-shadow: none;
}
@media (pointer: coarse) { .kind-card { --kind-control: var(--tap); } }
/* the panel's own left corners meet the card's seam: square while the
   card stands, so card and panel read as one surface */
@media (min-width: 60.001rem) {
  body.kind-card-open .stagework .viewer-side { border-top-left-radius: 0; border-bottom-left-radius: 0; }
}
.kind-card[hidden] { display: none; }
.kind-card[aria-busy="true"] { opacity: 0.85; }
.kind-card :where(p) { margin: 0; }
.kind-card .help, .kind-card .muted { color: var(--th-soft); font-size: var(--kind-fs-help); line-height: var(--kind-lh); }
/* D5: the head in two lines - title and the quiet way out, then the size */
.kind-card-head {
  /* round 6 (D13): the part menu's „⋯" after the quiet way out. The title never gives up a line to the controls
     (CR7): where the title and both controls do not fit one row, the controls take the next row, at the right edge */
  display: flex; flex-wrap: wrap; align-items: center; column-gap: var(--s2);
}
.kind-card-title { margin: 0; flex: 1 0 auto; max-width: 100%; font-size: 1rem; line-height: 1.5rem; font-weight: 600; }
.kind-card-head > .kit-button { flex: none; }
.kind-card-head > .kit-button:first-of-type { margin-left: auto; }
.kind-card-size {
  flex: 0 0 100%; color: var(--th-soft);
  font-variant-numeric: tabular-nums; white-space: nowrap;
}
.kind-card-size:empty { display: none; }
/* owner finding 10.11.2026: the card's picture of its part's drawing,
   on a phone only (the desk shows the drawing beside the card); a tap
   lays the stage's sheet over the glass („Nur Blatt", jobphone.js) */
.kind-card-sheet { display: none; }
/* every control of the card: one height, its words on one line (CR3) */
.kind-card .kit-button {
  min-height: var(--kind-control); padding-block: 0; padding-inline: var(--s3);
  font-size: var(--kind-fs); line-height: var(--kind-lh); white-space: nowrap;
}
.kind-card .kit-button-secondary { background: transparent; font-weight: 500; }
.kind-card .kit-button-secondary:hover:not([disabled]) { background: var(--stage-button-hover); }
.kind-card .kit-button-primary { font-weight: 600; }
.kind-card .kit-button-quiet { padding-inline: 0; }
.kind-card .kit-button[disabled], .kind-card .kit-button[aria-disabled="true"] {
  background: transparent; color: var(--th-faint); border-color: var(--th-line); opacity: 1;
}
.kind-card .kit-button[aria-pressed="true"] { border-color: var(--stage-hover-line); box-shadow: inset 0 0 0 1px var(--stage-hover-line); }
.kind-card .kit-choice, .kind-card .kit-choice.kit-choice-unheaded { margin: 0; }
.kind-card .kit-choice-option[hidden] { display: none; }
/* the track's hairline is part of the control's one height */
.kind-card .kit-choice-segment .kit-choice-option {
  min-height: calc(var(--kind-control) - 2 * var(--hairline)); color: var(--th-ink);
}
.kind-card .kit-choice-segment .kit-choice-option.is-chosen,
.kind-card .kit-choice-segment .kit-choice-option:has(input:checked) { color: var(--stage-sel-ink); }
/* the scope: segments, then the one help line at the help gap (CR10) */
.kind-card-scope[hidden] { display: none; }
.kind-card-scope .kit-choice-help { margin: var(--kind-help-gap) 0 0; }
.kind-card-files { margin-top: var(--kind-help-gap); }
.kind-card-files[hidden] { display: none; }
/* exactly two hairlines: after the head or scope, before the foot (CR6) */
.kind-card-rule { border: 0; border-top: 1px solid var(--th-line); margin: 0; width: 100%; }
.kind-card-rule[hidden] { display: none; }
/* the stage the card narrows keeps its sheet clear: the sheet viewer's
   long hint steps aside while the card stands (K2 - nothing over the
   drawing); the zoom buttons stay */
@media (min-width: 60.001rem) {
  body.kind-card-open .viewer.stage .viewer-zoom-hint { display: none; }
}
/* the card of a part without facts: the line, its help, the way on */
.kind-card-none { display: flex; flex-direction: column; align-items: flex-start; gap: var(--s2); }
/* THE GROUP: its header, the rows and „Warum?", 8 px apart */
.kind-card-group { display: flex; flex-direction: column; gap: var(--s2); }
.kind-card-group[hidden] { display: none; }
.kind-card-group-head { display: flex; align-items: center; justify-content: space-between; gap: var(--s2); }
.kind-card-group-head[hidden] { display: none; }
.kind-card-check-text { display: inline-flex; align-items: center; gap: var(--gap-icon-label); min-width: 0; }
/* THE ROW: label | control, the one line under the control (CR4, CR5) */
.kind-card-line {
  display: grid; grid-template-columns: var(--kind-label) minmax(0, 1fr);
  column-gap: var(--kind-gutter); row-gap: var(--kind-help-gap); align-items: start;
}
.kind-card-line[hidden] { display: none; }
.kind-card-label {
  display: flex; align-items: center; min-height: var(--kind-control);
  font-weight: 400; color: var(--th-soft);
}
.kind-card-control { display: flex; flex-wrap: wrap; gap: var(--s2); align-items: center; min-width: 0; }
.kind-card-control [hidden] { display: none; }
.kind-card-reason { grid-column: 2; color: var(--th-soft); font-size: var(--kind-fs-help); }
.kind-card-reason[hidden] { display: none; }
/* round 6: the quiet line of a selection from several surfaces, on the
   control edge under the Maserung row (CR4) */
.kind-card .kind-card-pick-mixed { margin-left: calc(var(--kind-label) + var(--kind-gutter)); }
.kind-card-pick-mixed[hidden] { display: none; }
/* D10, CR9: a row a mark asks about wears the one check style - the 3D
   view's dashed --check-outline at its width (partstyle.js), no fill -
   with 8 px of inner space that reaches into the card's padding, so its
   label stays on the content edge */
.kind-card-line.is-check-target {
  outline: var(--check-px) dashed var(--check-outline); outline-offset: 0; border-radius: 2px;
  background: transparent;
  margin: calc(-1 * var(--s1)) calc(-1 * var(--s2)); padding: var(--s1) var(--s2);
}
/* „Warum?": quiet, and its reasons in the card's own grid */
.kind-card-whys summary {
  cursor: pointer; color: var(--accent); width: max-content;
  min-height: var(--kind-control); display: flex; align-items: center;
}
.kind-card-whys summary:hover, .kind-card-whys summary:focus-visible { text-decoration: underline; }
.kind-card-whys[hidden] { display: none; }
.kind-card-whys dl {
  display: grid; grid-template-columns: var(--kind-label) minmax(0, 1fr);
  column-gap: var(--kind-gutter); row-gap: var(--s2); margin: var(--s2) 0 0;
}
.kind-card-whys dt { color: var(--th-soft); }
.kind-card-whys dd { margin: 0; }
.kind-card-whys [hidden] { display: none; }
/* THE FOOT: „Rückgängig" on the content edge, „Nächste prüfen" on the
   right edge, one line (CR13); the undo line at the help gap */
.kind-card-footer { display: flex; flex-direction: column; }
.kind-card-footer > .kind-card-rule { margin-bottom: var(--s4); }
.kind-card-foot { display: flex; align-items: center; justify-content: space-between; gap: var(--s2); }
.kind-card-foot [data-kind-next] { margin-left: auto; }
.kind-card-foot [hidden] { display: none; }
.kind-card-undo-line, .kind-card-status { margin-top: var(--kind-help-gap); }
.kind-card-undo-line[hidden], .kind-card-status:empty { display: none; }
/* M1: THE PICK BAR at the top of the 3D view */
.kind-pickbar {
  position: absolute; z-index: 6; top: var(--s2); left: var(--s2); right: var(--s2);
  display: flex; align-items: center; gap: var(--s2); flex-wrap: wrap;
  padding: var(--s1) var(--s2); border-radius: var(--radius-sm);
  background: var(--stage-file-head); color: var(--stage-file-head-ink, var(--th-ink));
  border: 1px solid var(--stage-hover-line); font-size: 0.78rem;
}
.kind-pickbar[hidden] { display: none; }
.kind-pickbar-text { flex: 1 1 12rem; }
/* owner law 13.11.2026: after the first click over several plates the bar
   says three short things, one line each (kindcard.js pickbarWords) */
.kind-pickbar-line { display: block; }
.kind-pickbar-line + .kind-pickbar-line { margin-top: 2px; }
.kind-pickbar .kind-pickbar-cancel { flex: none; }
/* it stands at the 3D view's foot where its top place would cover the
   plates it talks about (kindcard.js placePickbar) */
.kind-pickbar[data-place="foot"] { top: auto; bottom: var(--s2); }
/* the brief highlight once the first click is saved; none with reduced
   motion - the new words and the primary button say it */
@media (prefers-reduced-motion: no-preference) {
  .kind-pickbar.is-news { animation: pickbar-news 900ms ease-out; }
}
@keyframes pickbar-news {
  from { box-shadow: 0 0 0 3px var(--accent); }
  to { box-shadow: 0 0 0 3px transparent; }
}
@media (hover: none) { .kind-pickbar-key { display: none; } }
.kind-pickbar-key { font: inherit; font-size: 0.72rem; color: var(--th-soft); border: 1px solid var(--th-line); border-radius: 3px; padding: 0 0.3em; }
/* C5: the chosen scope's chip at its parts' centre */
.kind-scope-chip {
  position: absolute; z-index: 3; transform: translate(-50%, -50%); pointer-events: none;
  padding: 0.1rem var(--s2); border-radius: 999px; white-space: nowrap;
  background: var(--stage-file-head); color: var(--th-ink); border: 1px solid var(--stage-hover-line);
  font-size: 0.72rem; font-weight: 600;
}
.kind-scope-chip[hidden] { display: none; }
/* M3: the grain pick's two arrows, each a press */
.kind-grain-arrows { position: absolute; inset: 0; z-index: 7; pointer-events: none; }
/* during a pick the first-run hints step aside: the model is the task */
body[data-kind-picking] .assembly-inset .coachmark { display: none; }
.kind-grain-arrows[hidden] { display: none; }
.kind-grain-arrow {
  position: absolute; left: 0; top: 0; height: 1.6rem; margin: 0; padding: 0;
  transform-origin: 0 0; border: 0; background: transparent; cursor: pointer; pointer-events: auto;
  color: var(--stage-hover-line);
}
.kind-grain-arrow svg { display: block; width: 100%; height: 100%; fill: none; opacity: 0.75; }
.kind-grain-arrow:hover svg, .kind-grain-arrow:focus-visible svg { opacity: 1; filter: drop-shadow(0 0 3px var(--stage-hover-line)); }
/* audit 01.11.2026 (design note): during a pick the model is the task -
   the 3D view takes the panel's height the list leaves, and at rest it
   keeps a floor so the grain arrows and faces are big enough to hit */
.stagework .viewer-side .assembly-inset { min-height: 15rem; }
/* S5 (law 19): the 3D view keeps its height when a file of the list
   folds or opens, so the file's header stays where the eye has it; the
   list takes what is left and the panel body scrolls where it runs out */
.stagework .viewer-side .assembly-inset { flex-shrink: 0; }
/* law 19 and C.93: in the widened panel the 3D view takes only the room
   the list leaves above its least height, growing and on its way back,
   so the list is never pushed down whole (its rows would slide under the
   eye where it stands at its end) and the foot never leaves the panel */
.stagework .viewer-side.is-3d .assembly-inset,
.stagework .viewer-side.is-list .assembly-inset { flex-shrink: 1; }
body[data-kind-picking] .stagework .viewer-side .assembly-inset { flex: 1 0 60%; max-height: none; }
/* M2 and decision 11: the legend is inert during a pick, its reason as a
   tooltip (kindcard.js writes it) */
body[data-kind-picking] .model-legend { opacity: 0.6; cursor: not-allowed; }
/* owner feedback E: a small 3D view keeps its model clear - no arrangement
   slider, the legend's controls only under the pointer or the focus */
.assembly-inset[data-view-small] .explode-control { display: none; }
/* where the slider stands down, the solo bar takes the top line */
.assembly-inset[data-view-small] .solo-bar { top: var(--s2); }
/* the folded legend is its one chip: its name and the total */
.model-legend .legend-total { display: none; color: var(--stage-soft, var(--ink-soft)); font-weight: 400; }
.model-legend:not([open]) .legend-total { display: inline; }
.model-legend.is-compact:not([open]) .legend-title { display: inline; }
/* F: the isolation's own bar at the top of the 3D view */
/* owner look 01.11.2026 (round 6): THE VIEW'S ONE STATE BAR - the same bar
   for every mode that restricts the 3D view (assembly3d.js
   viewStateFollows); out of the flow over the model, so it never changes
   the canvas's size; its sentence may take a second line where the view is
   narrow, its button is the kit's quiet action in the stage's ink */
.solo-bar {
  position: absolute; z-index: 6; top: calc(var(--s2) + 2.6rem); left: 50%; transform: translateX(-50%);
  display: flex; align-items: center; gap: var(--s2); max-width: calc(100% - 2 * var(--s2));
  width: max-content; box-sizing: border-box;
  padding: 2px var(--s2); border-radius: var(--radius-sm);
  background: var(--stage-file-head); color: var(--th-ink); border: 1px solid var(--stage-hover-line);
  font-size: 0.78rem;
}
.solo-bar[hidden] { display: none; }
.solo-bar .solo-bar-text { min-width: 0; text-wrap: balance; }
.solo-bar .kit-button-quiet {
  flex: none; min-height: 1.5rem; padding-block: 0; color: var(--stage-hover-line); white-space: nowrap;
}
/* on a phone the bar's button is a finger's control: the kit's tap size */
body.phone-job .solo-bar .kit-button-quiet { min-height: var(--tap); }
/* round 6: a part hidden from the 3D view - its list row dimmed as a
   legend entry outside the shown set is (.model-legend-list li.is-dimmed),
   with its own „Einblenden", the kit's quiet action, at full strength */
.viewer-tree li[data-partrow][data-view-hidden="true"] > .partrow-button { opacity: 0.5; }
.viewer-tree .row-unhide {
  flex: none; min-height: 1.5rem; padding-block: 0; margin-inline-start: var(--s1);
  color: var(--stage-hover-line, var(--accent)); white-space: nowrap;
}
body.phone-job .viewer-tree .row-unhide { min-height: var(--tap); }
.stagework .assembly-solo[aria-pressed="true"] {
  border-color: var(--stage-hover-line); color: var(--stage-sel-ink);
  box-shadow: inset 0 0 0 1px var(--stage-hover-line); background: rgba(123, 176, 240, 0.25);
}
/* decision 14: on a phone the card's sheet steps aside while the thumb
   picks in the model, and comes back when the pick ends */
@media (max-width: 60rem) {
  body.phone-job[data-kind-picking] .kind-card { display: none; }
}
/* the side panel's checkbox word and its sentence (Nach Dateistruktur gruppieren) */
.stagework .kit-switch-word { color: var(--th-ink); }
.stagework .kit-switch-note { color: var(--th-soft); }
/* C.223: the open Plankopf's pill on the stage's dock: white on the
   light theme's amber fill read 3.6:1; on the dark ground it takes the
   stage's own attention pair */
.stagework .stamp-state { background: var(--stage-attention-soft); color: var(--stage-attention); box-shadow: inset 0 0 0 1px var(--stage-attention); }
/* C.211-B5: on a phone (the job page's own phone frame, 60rem) the card is
   a SHEET FROM THE FOOT: the glass's full width, at most half its height,
   rounded top corners, scrolling inside itself. It never covers a control:
   while it is open kindcard.js writes its height into --kind-sheet-h and
   marks the body, and the frame's main gives that room up as bottom
   padding - the sheet pane, the 3D view with its controls and the thumb bar
   all stand above the sheet, none beneath it. */
@media (max-width: 60rem) {
  body.phone-job .kind-card {
    --kind-control: var(--tap);
    position: fixed; top: auto; right: 0; bottom: 0; left: 0; z-index: 41;
    width: auto; max-height: 45vh; max-height: 45dvh;
    padding-bottom: calc(var(--kind-pad) + var(--safe-foot));
    border-width: 1px 0 0; border-radius: 16px 16px 0 0;
    overscroll-behavior: contain;
    box-shadow: 0 -8px 24px rgba(0, 0, 0, 0.28);
  }
  body.phone-job .kind-card { height: auto; margin-left: 0; }
  body.phone-job .kind-card-sheet:not([hidden]) {
    display: block; flex: 0 0 100%; box-sizing: border-box;
    margin: var(--s2) 0 0; padding: var(--s1); min-height: var(--tap);
    background: var(--panel); border: 1px solid var(--th-line); border-radius: var(--radius-sm);
    cursor: pointer;
  }
  body.phone-job .kind-card-sheet img {
    /* low enough that the card's head, its scope and its check header
       with the answer still stand in the opened sheet (law CR15) */
    display: block; width: 100%; height: 4.5rem; object-fit: contain;
  }
  /* CARD REDESIGN 4.6 (CR15): the same order, grid and words as on the
     desk, the controls at the tap height; the foot sticks to the card's
     bottom on its own ground and reserves its room (law 15, kit
     stickyfoot), so it covers no line the card scrolls under it */
  body.phone-job .kind-card-footer {
    position: sticky; bottom: calc(-1 * (var(--kind-pad) + var(--safe-foot)));
    padding-bottom: calc(var(--kind-pad) + var(--safe-foot));
    margin-bottom: calc(-1 * (var(--kind-pad) + var(--safe-foot)));
    /* its ground reaches the card's side edges, over a check row's
       outline that runs into the padding */
    margin-inline: calc(-1 * var(--kind-pad)); padding-inline: var(--kind-pad);
    background: var(--th-rail); z-index: 1;
  }
  /* a phone layer the reader opens over the frame (Mehr, Info, the
     finder) is the reader's latest act and stands whole: the card's sheet
     steps aside while it is open and comes back as it was when it closes
     (batch 39e: the sheet covered the layer's own controls). Its height
     falls to nothing meanwhile, so kindcard.js gives the frame its room
     back on the same resize it always answers. */
  body.phone-job[data-phone-layer]:not([data-phone-layer="header"]) .kind-card { display: none; }
  body.phone-job.kind-sheet-open > main { padding-bottom: var(--kind-sheet-h, 0px); box-sizing: border-box; }
  html body.phone-job.phone-sheet-only.kind-sheet-open .stagework > #viewer { bottom: var(--kind-sheet-h, 0px); }
  /* the frame's grid takes exactly the room the sheet leaves (a zero flex
     basis, so its rows are definite and cannot outgrow it): the sheet pane,
     the model with its corner controls and legend, the foot line and the
     thumb bar all stand above the sheet; the sheet pane gives way first */
  body.phone-job.kind-sheet-open .stagework { flex: 1 1 0; height: 0; min-height: 0; }
}
/* the card is about the 3D selection: while it is open the drawing-sheet
   pane gives its room up (back as it was, on its page, when the card
   closes) and the 3D view takes all the room above the sheet; the drawing
   itself never leaves the reader's sight - the card shows the part's own
   drawing at its head (owner finding 10.11.2026, .kind-card-sheet), and
   a tap on it is the sheet-only view, which lies over the glass on its
   own and keeps its pane */
@media (max-width: 60rem) and (orientation: portrait) {
  /* the pane folds to a point (no box, nothing painted), whichever box the
     card stands in */
  body.phone-job.kind-sheet-open:not(.phone-sheet-only) .stagework > #viewer {
    position: absolute; width: 0; height: 0; min-height: 0; margin: 0; padding: 0;
    border: 0; overflow: visible; visibility: hidden;
  }
  body.phone-job.kind-sheet-open:not(.phone-sheet-only) .stagework {
    grid-template-rows: minmax(0, 1fr) auto auto;
    grid-template-areas: "model" "foot" "bar";
  }
  /* the foot line's words wait (the strip says the same count) and the bar
     hugs its tap-size controls, so the 3D view keeps its share */
  body.phone-job.kind-sheet-open:not(.phone-sheet-only) .phone-foot { display: none; }
  /* the 3D view's share of a phone with the card open: the panel's padding
     gives it 16 px back (measured 07.11.2026: 328 px of an 844 px window in
     some runs, the sheet's law asks 40 %) */
  body.phone-job.kind-sheet-open:not(.phone-sheet-only) .stagework .viewer-side { padding-block: var(--s1); }
  html body.phone-job.kind-sheet-open .phone-bar { min-height: 0; padding-block: 2px calc(2px + var(--safe-foot)); }
}
/* the page's side gutter: no control of the thumb bar touches the glass's edge */
@media (max-width: 60rem) {
  html body.phone-job .phone-bar { padding-inline: var(--s4); }
}
/* C.178b: the list grouped by the file's own structure - a level is a
   block with its name over its indented rows; the name stands exactly
   as the file writes it, spaces included */
.viewer-tree li.partgroup { display: block; padding-right: 0; }
.viewer-tree .partgroup-name {
  display: block; padding: var(--s1) var(--s2) 0; color: var(--ink-faint);
  font-size: 0.78rem; white-space: pre-wrap; overflow-wrap: anywhere;
}
.viewer-tree .partgroup-list { list-style: none; margin: 0; padding: 0 0 0 var(--s3); }
.viewer-tree .tree-structure { padding: 0 var(--s2) var(--s2); }
/* C.178b: the upload help fold at the entry form's foot keeps a whole
   number of pixels in height (a line in rem, not a factor of the font),
   so what stands below it on the page is laid out on the same pixel
   rows as before the fold arrived */
.kit-entry-form > [data-kit-accordion="upload-help"] .kit-acc-q { line-height: 1.5rem; }
.viewer-tree .tree-part { min-height: 1.75rem; padding: 2px var(--s2); }
.viewer-tree .pill { font-size: 0.68rem; }
.viewer-tree .keep { flex: none; margin: 0; display: flex; }
.viewer-tree .keep .keep-apply { display: none; }
/* C.14: the group question, at the row and on its own LINE under it —
   a list item of its own, never an extra item inside the part's row.
   Measured, and the measurement is why: making the row a wrapping flex
   line let every row wrap, and each of the six rows of the lab's batch
   went from 30 px to 62 px whether it held a question or not. A row is
   one line at every rail width (owner 13.09.), so the question gets a
   line instead of taking one. */
.viewer-tree li.keep-group-line { display: block; padding: 0 var(--s1); }
.keep-group {
  display: flex; flex-wrap: wrap; align-items: center;
  gap: var(--s1); margin: 0 0 var(--s1); padding: var(--s1) var(--s2);
  border-radius: var(--radius-sm); background: var(--panel-sunken);
}
.keep-group-q { flex: 1 1 10rem; font-size: 0.72rem; color: var(--ink-soft); }
.keep-group .button-ghost {
  flex: none; font-size: 0.72rem; min-height: 1.5rem; padding: 2px var(--s2);
}
.stagework .keep-group { background: rgba(255, 255, 255, 0.07); }
.stagework .keep-group-q { color: var(--th-ink); }
.stagework .keep-group .button-ghost {
  color: var(--th-ink); border-color: var(--th-line-strong); background: transparent;
}
/* owner 13.09.: "Ja" is the answer that acts on several parts — it is the
   filled button, readable in both schemes; the base button paint had
   shown through as a light box with light text */
.keep-group .keep-group-yes, .stagework .keep-group .keep-group-yes {
  background: #1d4e89; color: #fff; border-color: #1d4e89;
}
.keep-group .keep-group-yes:hover, .stagework .keep-group .keep-group-yes:hover {
  background: #2a63a8; color: #fff; border-color: #2a63a8; filter: none;
}
.dl-toggle {
  position: relative; display: inline-flex; align-items: center; justify-content: center;
  width: 1.7rem; height: 1.7rem; margin: 0; padding: 0;
  border: 1px solid var(--line-strong); border-radius: 50%;
  background: transparent; color: var(--ink-faint); cursor: pointer;
  transition: background 220ms ease, color 220ms ease, transform 220ms ease, border-color 220ms ease;
}
.dl-toggle.is-on { background: var(--accent); color: var(--panel); border-color: var(--accent); }
.dl-toggle:hover { transform: scale(1.12); filter: none; }
.dl-toggle.is-locked { cursor: default; opacity: 0.9; }
/* C.21, owner 13.09.2026 17:25: THE GREEN MARK MEANS PAID, and it says
   so on its own class rather than by riding the lock. It used to be
   `.is-locked.is-on`, which conflated two facts: a part was green
   because it could not be switched, so the moment a paid part became
   switchable again the mark would have gone with the lock — and the
   owner's order is that the customer keeps seeing what he paid for. A
   paid part in the next package is filled green; one switched OUT of
   the next package keeps the green as an outline, because it is still
   paid and the diagonal above already says it is left out. */
.dl-toggle.is-billed.is-on {
  background: var(--good); color: var(--panel); border-color: var(--good);
}
.dl-toggle.is-billed:not(.is-on) { border-color: var(--good); color: var(--good); }
/* owner 13.09.: a part left OUT wears a white diagonal across its icon */
.dl-toggle { position: relative; }
.dl-toggle:not(.is-on)::after {
  content: ""; position: absolute; left: 0; right: 0; top: 50%; height: 2px; margin-top: -1px;
  background: #fff; border-radius: 1px; transform: rotate(-45deg); pointer-events: none;
}
/* owner 13.09.: a twin's lock is not a delivery — it looks like any included part */
.dl-toggle.is-locked.is-twin.is-on { background: var(--accent); border-color: var(--accent); opacity: 1; }
/* and a twin that HAS been paid for is green like any other paid part:
   sharing a sheet is not a reason to hide what the reader was charged */
.dl-toggle.is-billed.is-twin.is-on {
  background: var(--good); border-color: var(--good); opacity: 1;
}
.dl-toggle.is-locked:hover { transform: none; }
.dl-toggle.is-pop { animation: dl-pop 320ms ease; }
@keyframes dl-pop { 0% { transform: scale(1); } 50% { transform: scale(1.35); } 100% { transform: scale(1); } }
/* the state word carries a thin bar while the part draws */
.viewer-tree .pill { position: relative; overflow: visible; }
.viewer-tree .row-progress { display: none; }
/* C.88: the navigator's wait line carries the same bar, under its words */
.nav-wait { position: relative; padding-bottom: var(--s2); }
.nav-wait[hidden] { display: none; }
/* C.88: the sliding segment is painted INTO the bar (a gradient two and a
   half bars long, moved across it), not a second box slid past a clipped
   edge - so the bar cuts nothing and needs no clipping at all. The track
   colour is a token so a dark surface re-colours the track alone. */
.nav-wait .row-progress,
.viewer-tree li[data-paint="run"] .row-progress {
  display: block; position: absolute; left: 0.6rem; right: 0.4rem; bottom: -3px;
  height: 2px; border-radius: 2px;
  background: var(--row-track, var(--accent-soft));
}
/* C.187 (traced 18.10.2026): the segment is the bar's own child box, moved
   by transform from the bar's start to its end and back, always inside the
   bar - nothing is clipped, and the browser moves it without styling or
   painting anything again. Moved as the bar's background, it had every
   running row - 260 in the owner's batch - styled and painted anew in
   every frame (50 to 60 ms of each frame at four-fold slowdown). */
.nav-wait .row-progress::before,
.viewer-tree li[data-paint="run"] .row-progress::before {
  content: ""; position: absolute; top: 0; bottom: 0; left: 0; width: 40%;
  border-radius: inherit;
  background: var(--row-segment, var(--accent));
  animation: row-slide 1.2s ease-in-out infinite alternate;
}
@keyframes row-slide { from { transform: translateX(0); } to { transform: translateX(150%); } }
/* C.187 (measured 18.10.2026): on the phone a burst sets a whole list
   running at once, and twenty bars sliding together cost every frame of
   it 20 to 40 ms at four-fold slowdown. There the reader's own row (the
   part on the sheet) slides; every other running row holds its segment
   still in the middle, the reduced-motion picture, and still says
   "running". */
body.phone-job .viewer-tree li[data-paint="run"]:not([aria-current="true"]) .row-progress::before {
  animation: none; transform: translateX(75%);
}
/* the error marks: red circle critical, amber triangle fixable */
.mark {
  flex: none; display: inline-flex; align-items: center; justify-content: center;
  width: 1.3rem; height: 1.3rem; margin: 0; padding: 0;
  border: 0; border-radius: 50%; color: #fff; background: var(--bad);
  font: inherit; font-size: 0.75rem; font-weight: 700; line-height: 1; cursor: pointer;
}
.mark.mark-fixable { background: #b7791f; border-radius: 3px; }
.viewer-tree li > .mark { margin-left: var(--s1); }
.mark:hover { filter: brightness(1.1); }
/* owner 13.11.2026: the mark's note is a LAYER OVER THE PAGE (job.js
   placeMarkPop), out of every scroll box, as wide as its words up to the
   kit's measure and inside the glass's gutter - never squeezed into its
   row; on a phone it stands at the glass's foot (kit-term's place) */
.mark-pop {
  position: fixed; z-index: 50; left: var(--s4); top: var(--s4);
  width: max-content; max-width: min(calc(18 * var(--s4)), calc(100vw - 2 * var(--s4)));
  padding: var(--s2) var(--s3); box-sizing: border-box;
  background: var(--panel); color: var(--ink); border: 1px solid var(--line); border-radius: var(--radius-sm);
  box-shadow: var(--shadow-lift); font-size: 0.8rem; line-height: 1.4;
  white-space: normal; overflow-wrap: break-word; text-align: left;
}
.mark-pop p { margin: 0; }
.mark-pop > * + * { margin-top: var(--s2); }
.mark-pop.is-stage { background: var(--stage-field); color: var(--stage-ink); border-color: var(--stage-line-strong); }
.mark-pop.is-foot {
  left: var(--s4); right: var(--s4); top: auto; bottom: calc(var(--s4) + var(--safe-foot, 0px));
  width: auto; max-width: none;
}
.viewer-tree li { position: relative; }

/* THE DOCK (5, 5a, 7, 14.1, 18) */
.download-dock, .download-dock * { box-sizing: border-box; }
.download-dock {
  flex: none; display: grid; grid-template-columns: minmax(0, 1fr); gap: var(--s1); padding: var(--s2) var(--s3); margin: 0;
  max-width: 100%; min-width: 0;
  background: var(--panel); border-top: 1px solid var(--line);
}
/* C.93 RAIL HEIGHT LAW: the dock's rows are spaced by its gap token
   alone - a paragraph's own margin (the guest note wore the help
   line's 8 px) was a second number and 8 px of dead space above the
   foot's first row */
.download-dock > * { min-width: 0; max-width: 100%; margin: 0; }
.dock-summary {
  margin: 0; padding: var(--s1) var(--s2);
  min-height: calc(2 * 1.4em + 2 * var(--s1));
  background: var(--good-soft); border-radius: var(--radius-sm);
  font-size: 0.8rem; line-height: 1.4; color: var(--ink);
}
.download-dock[data-dock-state="drawing"] .dock-summary,
.download-dock[data-dock-state="anonymous"] .dock-summary { background: var(--panel-sunken); }
.dock-primary { display: grid; gap: var(--s1); }
.dock-primary .download-dock-action { margin: 0; width: 100%; text-align: center; }
/* C.145: the action and the "?" to the manual's ZIP fold, one row */
.dock-action-row { display: flex; align-items: center; gap: var(--s1); }
.dock-action-row > .download-dock-action,
.dock-action-row > .download-dock-preparing,
.dock-action-row > .dock-continue { flex: 1 1 auto; min-width: 0; }
/* C.165 (owner law 10.10.2026): the package's preparation in the dock -
   its step and share on one line, the page's own progress bar
   (.progress-track) under it, a fair estimate when there is one */
.dock-progress { display: grid; gap: var(--s1); justify-items: stretch; width: 100%; }
.dock-progress-line { display: inline-flex; align-items: center; justify-content: center; gap: var(--s2); }
.dock-progress-track { width: 100%; }
.dock-progress-eta { font-size: 0.75rem; text-align: center; }
/* C.186 (owner 12.10.2026: "'Making the files' and its spinner shall be
   much more obvious"): the package's progress is the dock's card while
   it is made - framed in the in-progress paint of the parts (--part-run,
   the same answer the list and the model give), the step in the ink of
   the page and set larger, the share large beside it, a broad bar under
   both and the estimate under the bar. Nothing of it wraps into a
   column of single words: step and share keep their own tracks. The
   card's one column is the card's whole width: the centring the plain
   preparing line and the thumb bar give .download-dock-preparing would
   otherwise size it by the step's words, and the bar with it. */
.download-dock-preparing.dock-progress {
  display: grid; grid-template-columns: minmax(0, 1fr);
  gap: var(--s2); justify-items: stretch; box-sizing: border-box;
  padding: var(--s2) var(--s3); min-height: 0;
  border: 2px solid var(--part-run); border-left-width: 6px; border-radius: var(--radius);
}
.dock-progress .dock-progress-line {
  display: grid; grid-template-columns: auto minmax(0, 1fr) auto; align-items: center;
  justify-content: stretch; gap: var(--s2); text-align: left;
}
.dock-progress [data-dock-step] { font-size: var(--fs-lead); font-weight: 600; line-height: 1.3; color: var(--ink); }
.stagework .dock-progress [data-dock-step] { color: var(--th-ink, inherit); }
.dock-progress .dock-pct { font-size: 1.4rem; font-weight: 700; }
.dock-progress .download-dock-spinner { width: 1.4rem; height: 1.4rem; border-width: 3px; color: var(--part-run); }
.dock-progress .dock-progress-track { height: 0.875rem; }
.dock-progress .dock-progress-eta { font-size: var(--fs-small); }
/* C.186: the pay page says from its first paint that Paddle's window is
   being opened (the packaging status's own form, larger); without a
   script it gives way to the noscript line */
.download-dock-preparing.pay-opening { justify-content: flex-start; font-size: var(--fs-lead); color: var(--ink); }
.pay-opening .download-dock-spinner { width: 1.4rem; height: 1.4rem; border-width: 3px; color: var(--accent); }
@media (scripting: none) { .pay-opening { display: none; } }
/* C.165: the notice after the payment keeps its cross in its corner, in
   both of the notice box's layouts */
.pay-notice { position: relative; padding-right: calc(var(--tap) + var(--s2)); }
.pay-notice > .coachmark-close { position: absolute; top: var(--s2); right: var(--s2); min-width: var(--tap); min-height: var(--tap); }
/* C.165: "Bezahlung fortsetzen" is a form's button; the form takes the
   action's place in the row, and the button its whole width */
.dock-continue { display: flex; margin: 0; }
.dock-action-row > .kit-help { margin-left: 0; }
.dock-reason { margin: 0; min-height: 1.2em; font-size: 0.74rem; line-height: 1.2; }
.dock-prepared { margin: 0; font-size: 0.75rem; color: var(--ink-faint); }
.download-dock[data-dock-state="ready"] .download-dock-action { animation: dock-breathe 2.2s ease-in-out infinite; }
.download-dock[data-dock-state="ready"] .dl-arrow { display: inline-block; animation: dock-nudge 1.2s ease-in-out infinite; }
@keyframes dock-breathe { 0%, 100% { box-shadow: 0 0 0 0 rgb(29 78 137 / 45%); } 50% { box-shadow: 0 0 0 8px rgb(29 78 137 / 0%); } }
@keyframes dock-nudge { 0%, 100% { transform: translateY(0); } 50% { transform: translateY(3px); } }
.download-dock-preparing { display: inline-flex; align-items: center; justify-content: center; gap: var(--s2); min-height: var(--tap); color: var(--ink-soft); font-size: 0.95rem; }
.dock-pct { font-variant-numeric: tabular-nums; color: var(--ink); }
.stagework .dock-pct { color: var(--th-ink, inherit); }
.download-dock-spinner {
  display: inline-block; width: 1em; height: 1em;
  border: 2px solid currentColor; border-top-color: transparent;
  border-radius: 50%; animation: button-spin 0.8s linear infinite;
}
.dock-secondary { display: flex; flex-wrap: wrap; gap: var(--s2); }
.dock-secondary > * {
  display: block; flex: 1 1 4.5rem; min-width: 0; margin: 0; padding: var(--s1) var(--s2); min-height: 0;
  overflow: hidden; text-overflow: ellipsis; white-space: nowrap; text-align: center;
  font-size: 0.76rem;
}
.dock-stamp-dot { display: inline-block; width: 0.5rem; height: 0.5rem; margin-right: 0.35em; border-radius: 50%; background: #b7791f; vertical-align: middle; }
/* owner 13.09.: the open Plankopf is SAID on the button, not only tinted */
.dock-stamp.is-incomplete { border-color: #b7791f; border-width: 2px; }
.stamp-state { display: inline-block; margin-left: 0.4em; padding: 0 0.45em; border-radius: 999px; font-size: 0.72em; font-weight: 600; background: #b7791f; color: #fff; vertical-align: middle; }
.prepare-stamp { display: flex; flex-wrap: wrap; align-items: center; gap: var(--s2); }
/* C.95: the guest notice carries the action now (the lead line is folded
   into it) and the job's address, which must wrap on a phone */
.dock-anon-note { margin: 0; font-size: 0.85rem; }
.dock-anon-note a { overflow-wrap: anywhere; }
/* C.58j (owner 28.09.2026): the doors share one row at one height, and
   a door's label never wraps on a desktop - the labels are short, and
   the notice above says what they are for */
.dock-anon-doors { display: flex; gap: var(--s2); align-items: stretch; }
.dock-anon-doors form { flex: 1 1 0; min-width: 0; margin: 0; display: flex; }
.dock-anon-doors .button, .dock-anon-doors .button-ghost { width: 100%; height: 100%; margin: 0; padding-inline: var(--s2); text-align: center; white-space: nowrap; }
.dock-anon-retention { margin: 0; font-size: 0.78rem; }
.dock-guest-count { margin: 0; }
/* c254 (owner 01.11.2026): the price box - parts, drawings, price in one
   line with the price large, the rule of the price below it, and the fold
   "Preis-Details" beside the link to the counting answer */
.price-box { margin: 0; display: grid; gap: var(--s1); font-size: 0.85rem; }
.price-box[hidden] { display: none; }
.pb-line { display: flex; flex-wrap: wrap; align-items: baseline; column-gap: var(--s2); row-gap: 0.15rem; }
/* b39h: the arrows and the link's mark are the kit's icons (kit-icons),
   drawn at the text's size; the steps and the price wrap like any prose
   (no-clipped-text) - the line's own flex-wrap moves a whole step to the
   next row before a step breaks */
.pb-arrow { color: var(--th-faint); display: inline-flex; align-self: center; }
.pb-arrow .kit-icon { width: 1em; height: 1em; }
.pb-link-mark.kit-icon { width: 0.9em; height: 0.9em; margin-right: 0.25em; vertical-align: -0.1em; }
.pb-price { font-size: 1.5rem; line-height: 1.2; font-variant-numeric: tabular-nums; }
.pb-vat { font-size: 0.75rem; color: var(--th-faint); }
.pb-min { font-size: 0.85rem; font-weight: 600; }
.pb-min[hidden] { display: none; }
.pb-text { margin: 0; }
.pb-text[hidden], .pb-details[hidden] { display: none; }
.pb-more { display: flex; flex-wrap: wrap; align-items: baseline; column-gap: var(--s3, 1rem); row-gap: 0.2rem; }
.pb-details > summary { cursor: pointer; }
.pb-details[open] { flex: 1 0 100%; order: 3; }
.pb-details[open] .pb-detail { margin-top: 0.3rem; }
.pb-link { color: inherit; }

.sheet-handle { display: none; }
/* SPEC 20: on a desktop the page is one viewport and never scrolls */
@media (min-width: 60.01rem) {
  html.has-stagework, body.has-stagework { height: 100%; overflow: hidden; }
  body.has-stagework .site-footer { display: none; }
}
/* the extras panel (spec 20): a native details whose content overlays the
   stage. C.38 (owner screenshot c38_faq_empty_anon.png): `inset` pinned
   all four edges, top AND bottom, so the box was always exactly the
   viewport's height regardless of what was inside it — on an anonymous
   job, whose FAQ section then rendered nothing (job.html), that fixed
   frame was the "full-height empty white page" itself, not only the
   missing rows. `bottom` is gone; `max-height` keeps the same ceiling
   the fixed box had, but the box now sizes to its own content below it. */
.extras > summary { list-style: none; }
.extras > summary::-webkit-details-marker { display: none; }
.extras-panel {
  position: fixed; top: calc(var(--header-offset) + 1rem); left: 6vw; right: 6vw;
  max-height: calc(100vh - var(--header-offset) - 3rem); z-index: 30;
  overflow: auto; overscroll-behavior: contain;
  background: var(--paper); border: 1px solid var(--line); border-radius: var(--radius);
  box-shadow: var(--shadow-lift); padding: var(--s4) var(--s5);
}
.extras-close { position: sticky; top: 0; float: right; z-index: 1; min-width: var(--tap); min-height: var(--tap); font-size: 1.2rem; background: var(--paper); margin: 0 0 var(--s2) var(--s2); }
.jobmore { padding-block: var(--s3); }
.jobmore .job-life { margin: var(--s3) 0 0; }

@media (max-width: 60rem) {
  /* the phone (spec 10, first shape): the top bar scrolls away and keeps
     only the short facts; the sheet takes most of the screen; the column
     follows; the dock sticks to the bottom */
  .jobtop { position: static; }
  .jobtop h1 { font-size: 1rem; }
  .meta-inline { gap: var(--s1) var(--s3); }
  .meta-inline dt { display: none; }
  .job-progress-line { margin-left: 0; }
  .stagework { display: block; height: auto; }
  /* c248: the stage (the stage's own top measured, as on a desk; 12rem
     only without the script) ends at the window's foot when the page opens */
  .viewer.stage { height: calc(100dvh - var(--stage-top, 12rem) - var(--s3)); min-height: 20rem; }
  .viewer.stage .viewer-bar { flex-wrap: wrap; }
  /* job page 9: the facts stand in the „Mehr" menu, or at phone width in
     the (i) layer, each with its label */
  .meta-inline dt { display: inline; }
  .viewer.stage .viewer-stage { grid-template-columns: 2.5rem minmax(0, 1fr) 2.5rem; }
  /* C.96: the bottom sheet of spec 10 is retired. With the script the
     page is the phone frame (the C.96 block at the end of this file);
     without it every part of the page stands in the flow and the page
     scrolls, which is the one arrangement that needs no script. */
  .stagework .viewer-side { position: static; margin-top: var(--s2); }
  .jobmore { padding-bottom: var(--s5); }
}
@media (prefers-reduced-motion: reduce) {
  .stagework, .ghost-img, .ghost-fly, .dl-toggle { transition: none; }
  .coachmark-ring, .coachmark-hand, .download-dock[data-dock-state="ready"] .download-dock-action,
  .dl-arrow, .dl-toggle.is-pop, .row-progress, .row-progress::before,
  .stamp-widget .submit-row button[type="submit"].is-dirty,
  .stamp-foot-part button[type="submit"].is-dirty,
  .start-pop-save.is-dirty { animation: none; }
  /* the still bar shows its segment in the middle rather than off its end */
  .row-progress::before { transform: translateX(75%); }
  /* ...and the unsaved mark does not go with the motion. A reader who
     has asked their system to cut animation still has to be able to see
     that something is unsaved, so the pulse becomes a steady ring —
     a REPLACEMENT for the movement, not the loss of the meaning. */
  .stamp-widget .submit-row button[type="submit"].is-dirty,
  .start-pop-save.is-dirty {
    box-shadow: 0 0 0 0.28rem rgba(37, 99, 168, 0.4);
  }
  /* The same trade for the arrival mark (owner, 14.09.2026, 15:55): a
     reader who has asked for less motion is not a reader who may be
     left wondering whether the upload took. The button stops moving
     and answers in colour and ring instead — brighter than its own
     ready state, and held for the same two seconds, so the arrival is
     still unmistakable at a glance. */
  .kit-draw-mirror.is-fresh,
  #submitbutton.is-fresh {
    animation: none;
    transform: none;
    background: var(--accent);
    box-shadow: 0 0 0 0.35rem var(--accent-soft),
                0 0 0 0.5rem rgba(37, 99, 168, 0.55);
  }
}

/* ===================================================================
   THE THEATRE — the D mockup's maximised view is the model (owner,
   12.09.2026 evening): a dark stage and a dark rail under the light
   site header and top bar; the rail 300 px at rest and 560 px when
   hovered; the navigator 210 px, 340 px when hovered; compact rows of
   light text; the file header a dark sticky strip; the dock's buttons
   in one row at the rail's foot. Colours are the mockup's own.
   =================================================================== */
.stagework {
  --viewer-side-rest: 26.25rem; /* owner 13.09.: the rail at rest 40 % wider than the mockup's 300 px */
  --viewer-side: var(--viewer-side-rest);
  /* the least the stage keeps of the window while the card and a widened
     panel stand beside it (01.11.2026) */
  --stage-keep: 28rem;
  --th-bg: var(--stage-bg); --th-bar: var(--stage-bar); --th-rail: var(--stage-rail); --th-head: var(--stage-head);
  --th-ink: var(--stage-ink); --th-soft: var(--stage-soft); --th-faint: var(--stage-faint); --th-sep: var(--stage-sep);
  --th-line: var(--stage-line); --th-line-strong: var(--stage-line-strong);
  --th-sel: var(--stage-sel);
  background: var(--th-bg); border-radius: var(--radius); padding: var(--s2); gap: var(--s2);
  color: var(--th-soft);
}
/* the panel's hover area also holds the docked plate card, a press
   that began in the panel (a drag or zoom in the 3D view runs on past the
   panel's edge) and the card's keyboard focus: ONE rule, no second timer */
/* job page 9 (DECISIONS_CONFLICTS A1): the width the reader dragged
   (kit/split.js, `--viewer-side-rest`) is the resting width; the hover
   only ever widens beyond it, never narrows it, and a drag on the split
   handle holds every hover change still */
/* job page 9 round 4 (scope 3, S8; SKETCH_D7B P1): the widening is the
   kit's hover intent (kit/hoverintent.js) - the class comes after the
   pointer rested in the panel and goes a while after it left; the docked
   card counts as the panel and holds the width either way */
.stagework.is-rail-wide:not(.is-splitting) { --viewer-side: max(var(--viewer-side-rest), min(50vw, 60rem)); }
/* 01.11.2026 (gate plate-card-browser at 1280 x 800 and 1024 x 768): while
   the card stands beside the panel, the widening never takes the stage
   below --stage-keep - at those windows the panel then keeps its resting
   width and the sheet's bar keeps every control in its box */
body.kind-card-open .stagework.is-rail-wide:not(.is-splitting) {
  --viewer-side: max(var(--viewer-side-rest), min(50vw, 60rem, calc(100vw - var(--kind-card-w) - var(--stage-keep))));
}
@media (prefers-reduced-motion: reduce) {
  .stagework { --rail-ms: 0ms; }
}
/* job page 9 round 4 (scope 3, S8a): THE EDGE PREVIEW - a pointer in the
   zone around the panel's edge eases the edge out by at most
   --edge-preview-offset, as a transform only (no layout moves), and
   lights a thin accent line in the split handle's own 8 px; moving away
   fades both back; reduced motion keeps the line and drops the movement.
   The transform stands only while the preview does, so at rest the panel
   is no containing block for anything fixed inside it. */
@media (min-width: 60.001rem) {
  .stagework .viewer-side { transition: transform var(--edge-preview-fade) var(--hover-ease); }
  .stagework[data-edge-preview] .viewer-side {
    transform: translateX(calc(-1 * var(--edge-preview-offset) * var(--edge-t, 0)));
  }
  .split-handle::after {
    content: ""; position: absolute; top: 0; bottom: 0; right: 0;
    width: var(--edge-preview-line); background: var(--accent);
    opacity: 0; pointer-events: none;
    transition: opacity var(--edge-preview-fade) var(--hover-ease);
  }
  .stagework[data-edge-preview] .split-handle::after { opacity: var(--edge-t, 0); }
}
@media (min-width: 60.001rem) and (prefers-reduced-motion: reduce) {
  .stagework[data-edge-preview] .viewer-side { transform: none; }
}
.viewer.stage { background: var(--th-bg); border: 0; }
.viewer.stage .viewer-bar {
  background: var(--th-bar); color: var(--th-ink);
  border-bottom: 1px solid var(--th-line); padding: var(--s2) var(--s3); gap: var(--s3);
}
.viewer.stage .viewer-bar strong { color: var(--th-ink); flex: 0 1 auto; }
/* the controls stand at the bar's right; the counter and the name keep
   the left edge whatever the rail does (owner 13.09.) */
.viewer.stage .viewer-bar .viewer-slot.viewer-sheet-group { margin-left: auto; }
/* round 6 (02.11.2026, gate plate-card-browser at 1024 x 768): the docked
   card takes 30vw and the panel keeps its resting width, so the stage can
   be narrower than the bar's fixed controls - the sheet group keeps its
   room while invisible (#174) - and the bar pushed its download link out
   of its own box under the card. While the card stands, the bar takes a
   second line instead: the name fills the first line and shortens as
   before (its basis 0, so it never wraps the bar by itself), and the
   controls stay at the bar's right. */
body.kind-card-open .viewer.stage .viewer-bar { flex-wrap: wrap; justify-content: flex-end; }
body.kind-card-open .viewer.stage .viewer-bar strong { flex: 1 1 0; }
.viewer.stage .viewer-count, .viewer.stage .viewer-bar .muted { color: var(--th-faint); font-size: 0.82rem; }
.viewer.stage .viewer-bar a, .viewer.stage .viewer-bar .button-ghost {
  color: var(--th-ink); border: 1px solid var(--th-line-strong); background: var(--stage-button-bg);
  border-radius: var(--radius-sm); padding: 0.25rem 0.5rem; font-size: 0.8rem; text-decoration: none;
}
.viewer.stage .viewer-bar a:hover, .viewer.stage .viewer-bar .button-ghost:hover { background: var(--stage-button-hover); filter: none; }
/* owner 13.09.: no white box for a note on the dark stage — the words
   stand on the stage's own ground; their colour stays the warning colour */
.viewer.stage .viewer-notes { color: var(--th-soft); background: transparent; border: 0; padding: var(--s1) var(--s3); }
.viewer.stage .viewer-notes .readability-note { background: transparent; border: 0; padding: 0; margin: 0; box-shadow: none; }
.viewer.stage .viewer-stage { background: var(--th-bg); }
/* owner 13.09.: the sheet lies on the stage's dark ground, no box around it */
.viewer.stage .viewer-body { padding: var(--s3); background: var(--th-bg); border: 0; box-shadow: none; }
.viewer.stage .viewer-body img { border: 1px solid #cfc9bd; border-radius: var(--radius-sm); }
.viewer.stage .viewer-placeholder { color: var(--th-faint); }
/* SKETCH_D7B R1: while the file is read the stage says nothing - an empty
   sentence takes no box; the file's own row shows no running word, and
   the 3D help line waits for the model */
.stage-now:empty { display: none; }
.viewer-tree .file-name .pill[data-status="pending"],
.viewer-tree .file-name .pill[data-status="running"] { display: none; }
.viewer-side-body:has(> #viewer-assembly[hidden]) > .cues { display: none; }
.viewer .ghost-arrow { background: var(--stage-button-bg); border-color: var(--th-line-strong); color: var(--th-ink); box-shadow: none; }
.viewer .ghost:hover .ghost-arrow { background: var(--stage-button-hover); color: var(--stage-sel-ink); }
.viewer.stage .viewer-zoom-btn, .viewer.stage .viewer-zoom-reset { background: var(--stage-button-bg); border-color: var(--th-line-strong); color: var(--th-ink); }

/* the rail */
.stagework .viewer-side { background: var(--th-rail); border: 1px solid var(--th-line); color: var(--th-soft); border-radius: var(--radius-sm); }
.stagework .viewer-side-body { gap: var(--s2); padding: var(--s2); }
.stagework .file-picker { gap: 0.3rem; }
.stagework .file-pick { background: var(--stage-field); color: var(--th-soft); border-color: var(--th-line-strong); font-size: 0.74rem; }
.stagework .file-pick[aria-pressed="true"] { background: var(--th-sel); color: var(--stage-sel-ink); border-color: var(--th-sel); }
.stagework .assembly-inset {
  flex: 0 1 290px; min-height: 6rem; max-height: none; display: block;
  background: radial-gradient(circle at 50% 40%, #33507a, #1a2c46);
  border: 1px solid rgba(159, 182, 214, 0.35); border-radius: var(--radius-sm); overflow: hidden;
  /* C.24: the navigator's growth is the rail's own movement seen from
     inside, so it runs on the rail's clock and not on a second one */
  transition: flex-basis var(--rail-ms) var(--rail-ease);
}
/* owner 13.09.: with the rail wide, the pair is decided by which of the
   two the pointer ENTERED last (job.js sets is-3d / is-list on the rail):
   a sticky choice, so the boundary moving under the cursor cannot flip
   it back and forth; leaving the rail puts both back to rest */
/* the sizes come from the widgets' own rest sizes: the 3D at rest is
   290 px tall on a 26.25rem rail (its proportions), so hovered it keeps
   those proportions at the wider rail; hovered list — the 3D keeps its
   rest height and the list gains width only */
.stagework .viewer-side.is-3d .assembly-inset { flex-basis: calc(var(--viewer-side) * 0.69); flex-grow: 0; max-height: none; }
.stagework .viewer-side.is-list .assembly-inset { flex-basis: var(--inset-rest-h, 290px); flex-grow: 0; max-height: none; }
.stagework .assembly-inset .assembly-canvas { background: transparent; border: 0; border-radius: 0;
  /* the viewer clears and shades with these, read where the canvas stands: the theatre's navy and a light timber grey */
  --panel-sunken: #1f3452; --line-strong: #c9c2b4; --accent: #7bb0f0; }
/* owner 13.09.: the arrangement is ONE slider in the toggle's pill —
   assembled at its left end (zero), exploded at its right end */
.explode-control {
  position: absolute; z-index: 1; top: var(--s2); right: var(--s2);
  display: inline-flex; align-items: center; gap: 0.45rem; padding: 0.3rem 0.65rem;
  background: rgba(20, 32, 52, 0.6); border: 1px solid rgba(159, 182, 214, 0.45); border-radius: 999px;
  color: var(--th-soft, var(--ink));
}
.explode-end { display: inline-flex; align-items: center; }
.explode-range { display: flex; align-items: center; width: 8rem; margin: 0; }
.explode-range input {
  width: 100%; margin: 0; cursor: pointer; -webkit-appearance: none; appearance: none;
  height: 1.2rem; background: transparent;
}
.explode-range input::-webkit-slider-runnable-track {
  height: 4px; border-radius: 2px; background: rgba(159, 182, 214, 0.55);
}
.explode-range input::-moz-range-track {
  height: 4px; border-radius: 2px; background: rgba(159, 182, 214, 0.55);
}
.explode-range input::-webkit-slider-thumb {
  -webkit-appearance: none; appearance: none; width: 14px; height: 14px; margin-top: -5px;
  border-radius: 50%; background: #7bb0f0; border: 2px solid var(--stage-file-head-ink);
  box-shadow: 0 0 0 0 rgba(123, 176, 240, 0.7);
}
.explode-range input::-moz-range-thumb {
  width: 14px; height: 14px; border-radius: 50%; background: #7bb0f0; border: 2px solid var(--stage-file-head-ink);
  box-shadow: 0 0 0 0 rgba(123, 176, 240, 0.7);
}
/* owner 14.09.: the handle pulses until the reader has used the slider
   once (job.js drops is-idle on the first input); a ring breathes out
   of the thumb so the control is found without a word */
.explode-range { position: relative; }
.explode-pulse {
  position: absolute; left: 7px; top: 50%; width: 14px; height: 14px; margin: -7px 0 0 -7px;
  border-radius: 50%; pointer-events: none; display: none;
  box-shadow: 0 0 0 0 rgba(123, 176, 240, 0.75);
}
.explode-control.is-idle .explode-pulse { display: block; animation: explode-pulse 1.5s ease-out infinite; }
/* finding 10 (owner 13.11.2026): after the first-sight intro the ring
   pulses three times and stands still (job.js explode intro) */
.explode-control.is-intro-pulse .explode-pulse { display: block; animation: explode-pulse 1.5s ease-out 3; }
@keyframes explode-pulse {
  0% { box-shadow: 0 0 0 0 rgba(123, 176, 240, 0.75); }
  70% { box-shadow: 0 0 0 9px rgba(123, 176, 240, 0); }
  100% { box-shadow: 0 0 0 0 rgba(123, 176, 240, 0); }
}
.stagework .assembly-reset, .stagework .assembly-solo {
  background: rgba(20, 32, 52, 0.6); color: var(--th-soft); border-color: rgba(159, 182, 214, 0.45); opacity: 1;
}
.stagework .assembly-reset { top: auto; bottom: var(--s2); right: var(--s2); }
/* JOB PAGE 9 round 6 (D6): THE VIEW CUBE in the 3D view's right edge,
   under the arrangement slider; it turns with the camera, the face that
   looks at the reader lit */
.view-cube {
  position: absolute; z-index: 2; right: var(--s2); top: calc(var(--s2) + 2.6rem);
  width: 2.75rem; height: 2.75rem; perspective: 10rem;
}
.view-cube[hidden] { display: none; }
.view-cube-body {
  position: absolute; inset: 0; transform-style: preserve-3d;
  transition: transform 80ms linear;
}
.view-cube-face {
  position: absolute; inset: 0; margin: 0; padding: 0;
  display: flex; align-items: center; justify-content: center;
  border: 1px solid rgba(159, 182, 214, 0.55); border-radius: 2px;
  background: rgba(20, 32, 52, 0.85); color: var(--th-soft, #d3e0f5);
  font: inherit; font-size: 0.5rem; font-weight: 650; text-transform: uppercase; letter-spacing: 0.02em;
  backface-visibility: hidden; cursor: pointer;
}
.view-cube-face[data-facing="true"] { background: rgba(123, 176, 240, 0.35); color: #fff; border-color: var(--stage-hover-line, #7bb0f0); }
.view-cube-face:hover, .view-cube-face:focus-visible { color: #fff; border-color: var(--stage-hover-line, #7bb0f0); }
.view-cube-face[data-face="front"] { transform: translateZ(1.375rem); }
.view-cube-face[data-face="back"] { transform: rotateY(180deg) translateZ(1.375rem); }
.view-cube-face[data-face="right"] { transform: rotateY(90deg) translateZ(1.375rem); }
.view-cube-face[data-face="left"] { transform: rotateY(-90deg) translateZ(1.375rem); }
.view-cube-face[data-face="top"] { transform: rotateX(90deg) translateZ(1.375rem); }
.view-cube-face[data-face="bottom"] { transform: rotateX(-90deg) translateZ(1.375rem); }
@media (prefers-reduced-motion: reduce) { .view-cube-body { transition: none; } }
/* D7: the neighbours' button beside the isolate button, same make */
.stagework .assembly-neighbours {
  position: absolute; z-index: 1; top: auto; bottom: var(--s2);
  left: calc(2 * var(--s2) + var(--tap));
  display: flex; align-items: center; justify-content: center; gap: 1px;
  min-width: 2rem; min-height: 2rem; margin: 0; padding: var(--s1) var(--s2);
  border: 1px solid rgba(159, 182, 214, 0.45); border-radius: var(--radius-sm);
  background: rgba(20, 32, 52, 0.6); color: var(--th-soft); cursor: pointer;
}
.stagework .assembly-neighbours:disabled { opacity: 0.4; cursor: default; }
.stagework .assembly-neighbours[aria-pressed="true"] { border-color: var(--stage-hover-line); color: var(--stage-sel-ink); }
.assembly-neighbours-plus { display: inline-flex; line-height: 1; }
.assembly-neighbours-plus svg { width: 0.8rem; height: 0.8rem; }
/* D13: THE PART MENU - the kit menu, its body at the pointer inside the
   3D view; after a finger's long press a sheet from the foot */
.part-menu { position: absolute; inset: 0; z-index: 9; pointer-events: none; }
.part-menu > summary { list-style: none; }
.part-menu-body {
  position: absolute; pointer-events: auto; min-width: 12rem; padding: var(--s1);
  display: flex; flex-direction: column; gap: 2px;
  background: var(--stage-file-head, var(--panel)); color: var(--th-ink, var(--ink));
  border: 1px solid var(--th-line-strong, var(--line)); border-radius: var(--radius-sm);
  box-shadow: var(--shadow-lift);
}
.part-menu-item {
  margin: 0; padding: var(--s1) var(--s2); min-height: 2rem; text-align: left;
  border: 0; border-radius: var(--radius-sm); background: transparent; color: inherit; font: inherit; cursor: pointer;
}
.part-menu-item[hidden] { display: none; }
/* owner 01.11.2026 (menu stretched over the whole view, at its left edge):
   the kit's dropdown rule `[data-menu]:not([data-menu-in-flow]) >
   [data-menu-body]` (right: 0) outranked the plain class rule, so the
   body spanned from the pointer to the view's right edge and viewtools.js
   measured that width and pushed it to the left. The part menu sits AT
   THE POINTER, sized to its words, at most 20rem: the same attributes
   lifted into this rule so it wins by specificity, not by order. */
.part-menu[data-menu]:not([data-menu-in-flow]) > .part-menu-body[data-menu-body] {
  right: auto; top: auto; width: max-content; max-width: min(20rem, calc(100% - 8px));
}
.part-menu.is-sheet[data-menu]:not([data-menu-in-flow]) > .part-menu-body[data-menu-body] {
  right: 0; width: auto; max-width: none;
}
.part-menu-item { display: flex; justify-content: flex-start; width: 100%; }
.part-menu-item:hover, .part-menu-item:focus-visible { background: var(--stage-button-hover, var(--accent-soft)); }
/* job page 9 round 6 (measured at 390 x 844): the menu's own z-index 9
   is the stacking level its fixed body is painted at, so the phone card
   (a fixed sheet from the foot at 41) lay over every item of the sheet
   the long press opened beside it, and the lifting finger's click went to
   the card. As a sheet the menu stands on the kit's menu layer (70, the
   `[data-menu-body]` rule above), over the card and the dock. */
.part-menu.is-sheet { z-index: 70; }
.part-menu.is-sheet .part-menu-body {
  position: fixed; left: 0; right: 0; bottom: 0; top: auto; min-width: 0;
  padding: var(--s2) var(--s3) calc(var(--s3) + var(--safe-foot, 0px));
  border-radius: 16px 16px 0 0;
}
.part-menu.is-sheet .part-menu-item { min-height: var(--tap); }
/* the card's „⋯" opener of the same menu */
/* the card's „⋯" opener of the same menu: the kit's quiet kind (card law
   CR2), only its glyph a little larger and its box square */
.kind-card .kind-card-more { min-width: var(--kind-control); padding-inline: var(--s1); font-size: 1.1rem; }
/* JOB PAGE 9 round 5 (D4): the help's „?" beside the reset, same make */
.assembly-help {
  position: absolute; z-index: 1; top: auto; bottom: var(--s2);
  right: calc(2 * var(--s2) + var(--tap));
  display: flex; align-items: center; justify-content: center;
  min-width: 2rem; min-height: 2rem; margin: 0; padding: var(--s1) var(--s2);
  font: inherit; font-size: 0.95rem; font-weight: 650; line-height: 1;
  border: 1px solid rgba(159, 182, 214, 0.45); border-radius: var(--radius-sm);
  background: rgba(20, 32, 52, 0.6); color: var(--th-soft, var(--ink-soft)); cursor: pointer;
}
.assembly-help:hover, .assembly-help:focus-visible { color: var(--stage-sel-ink, var(--accent)); }
/* under a finger the corner controls keep the tap size; the view cube's
   side faces are foreshortened below it whatever the cube's size, so a
   phone turns the model with one finger and goes without the cube */
@media (pointer: coarse) {
  .stagework .assembly-neighbours, .assembly-help { min-width: var(--tap); min-height: var(--tap); }
}
body.phone-job .view-cube { display: none; }
.help3d .cues { display: flex; flex-direction: column; align-items: flex-start; gap: var(--s1); font-size: 0.9rem; }
.help3d .cue-sep { display: none; }
.help3d-lines { margin: var(--s2) 0 0; padding-left: 1.2em; display: grid; gap: var(--s1); }
.stagework .assembly-solo { top: auto; bottom: var(--s2); left: var(--s2); }
/* job page 9 round 4 (SKETCH_D7B L3): the 3D view's one hint stands at
   its foot, between the corner buttons, never over the legend - and,
   since round 6 (D7), right of the isolate AND the neighbours buttons
   (an earlier rule for the neighbours stood above this one and lost to
   it, so the hint covered the neighbours button; 01.11.2026) */
.stagework #navigator-coach .coachmark-bubble,
.stagework .paint-hint .coachmark-bubble {
  top: auto; bottom: var(--s2);
  left: calc(3 * var(--s2) + 2 * var(--tap)); right: calc(3 * var(--s2) + 2 * var(--tap));
}
/* five cues wrap onto two rows in the rail (owner 13.09.: the Shift
   gesture joined them); the icons separate the pairs, so the dots go —
   a dot left dangling at a row's end was the only thing they added */
.stagework .cues { color: var(--th-faint); font-size: 0.68rem; gap: 0.15rem 0.85rem; }
.stagework .cues .cue-sep { display: none; }
.stagework .cue-sep { color: var(--th-sep); }

/* the list */
.stagework .viewer-tree { border: 1px solid var(--th-line); border-radius: var(--radius-sm); font-size: 0.78rem; }
.stagework .viewer-tree .file-row > summary {
  /* owner 13.09.: a lighter ground for contrast, and room at both ends so
     the chevron and the state word stand clear of the borders */
  background: var(--stage-file-head); color: var(--stage-file-head-ink); border-bottom: 1px solid var(--stage-button-hover);
  font-size: 0.74rem; padding: 0.35rem 0.75rem 0.35rem 0.7rem; border-radius: 0; gap: 0.45rem;
}
/* the header carries the class file-name too, and the base sheet paints
   that class with the panel colour at a higher specificity — this rule
   outranks it, so the theatre header is really dark with light text */
.stagework .viewer-tree .side-file > .file-row > .file-name { background: var(--stage-file-head); color: var(--stage-file-head-ink); }
.stagework .viewer-tree .file-row > summary::before { border-color: var(--th-faint); }
.stagework .viewer-tree .file-name-text { color: var(--stage-file-ink); }
.stagework .viewer-tree .file-parts { color: var(--th-faint); }
/* the header's live pill already counts the parts; the second count stays for the scripts, unseen */
.stagework .viewer-tree .file-row > summary .file-parts { position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0 0 0 0); }
.stagework .viewer-tree .file-row > summary .pill { background: transparent; color: var(--th-faint); padding: 0; font-size: 0.66rem; }
.stagework .viewer-tree li {
  border-top: 0; border-bottom: 1px solid var(--stage-file-bg); border-radius: 0;
  color: var(--th-soft); padding: 0 0.4rem 0 0.3rem; gap: 0.4rem; scroll-margin-top: 1.9rem;
}
.stagework .viewer-tree li:hover { background: var(--stage-file-bg); }
/* C.104: in the list the state keeps the row's ground and the selection
   is two rings - the stage's accent outside, the finished row's ink
   inside - with the name bold, so a chosen finished row stays green */
.stagework .viewer-tree li[aria-current="true"],
.stagework .viewer-tree li[data-kind-chosen="true"] {
  background: transparent; color: var(--th-soft);
  box-shadow: inset 0 0 0 2px var(--stage-hover-line), inset 0 0 0 4px var(--part-done-ink);
}
.stagework .viewer-tree li[data-paint="done"][aria-current="true"],
.stagework .viewer-tree li[data-paint="done"][data-kind-chosen="true"] {
  background: var(--part-done); color: var(--part-done-ink);
}
.stagework .viewer-tree li[aria-current="true"] .partrow-button,
.stagework .viewer-tree li[data-kind-chosen="true"] .partrow-button { font-weight: 600; }
/* owner 13.09.: a row is ONE line at every rail width, so widening the
   rail never re-wraps the list (the name ellipsises; its whole text is
   on the row's title) — nothing jumps while the rail animates */
.stagework .viewer-tree .partrow-button { flex-wrap: nowrap; }
.stagework .viewer-tree .partrow-button .part-name { flex: 1 1 auto; min-width: 0; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; }
.stagework .viewer-tree .tree-part { color: inherit; padding: 0.25rem 0.1rem; min-height: 0; gap: 0.4rem; }
.stagework .viewer-tree .tree-part:hover { background: transparent; }
.stagework .viewer-tree .part-n { color: var(--th-faint); width: 1.6rem; flex: none; font-size: 0.78rem; }
.stagework .viewer-tree .part-name { color: inherit; font-family: var(--font); }
.stagework .viewer-tree li[data-paint="left"] .part-name { color: var(--th-faint); }
/* owner 13.09.: no "= Pos. N" beside the name — the icon's tooltip names the twin */
.stagework .viewer-tree .part-twin { display: none; }
.stagework .viewer-tree .pill { background: transparent; color: var(--th-faint); font-size: 0.66rem; padding: 0; gap: 0.3rem; }
/* owner 13.09.: one quiet colour for every state word but failure — the
   list is not a christmas tree; the icon is the one accent it carries */
.stagework .viewer-tree .pill[data-status="failed"] { color: var(--stage-fault); }
.stagework .viewer-tree li > .mark { align-self: center; width: 1.3rem; height: 1.3rem; min-height: 0; max-height: 1.3rem; }
.stagework .viewer-tree .file-note { color: var(--stage-fault); }
.stagework .dl-toggle { border-color: var(--th-line-strong); color: var(--th-faint); width: 1.55rem; height: 1.55rem; }
.stagework .dl-toggle.is-on { background: var(--accent); border-color: var(--accent); color: var(--stage-sel-ink); }
.stagework .dl-toggle.is-locked.is-on { background: var(--good); border-color: var(--good); }
.stagework .dl-toggle.is-locked.is-twin.is-on { background: var(--accent); border-color: var(--accent); }
/* C.21: the paid mark in the stage column too, on its own class */
.stagework .dl-toggle.is-billed.is-on { background: var(--good); border-color: var(--good); color: var(--stage-sel-ink); }
.stagework .dl-toggle.is-billed:not(.is-on) { border-color: var(--good); color: var(--good); }
.stagework .viewer-tree .row-progress { --row-track: rgba(255, 255, 255, 0.15); }
/* C.104, THE ROWS IN THEIR PAINT (pipeline.part_paint, the row's own
   data-paint): the list has exactly one ground colour, and it means
   finished - the one green with near-black words and a drawn tick before
   the state word. Every other state stays a word, a mark or the thin bar
   under the word: a part in progress slides the green segment, a part
   not drawn says so in the problem red, a part left out is faint. Hover
   lightens a row and never changes its paint. */
.viewer-tree li[data-paint="run"] { --row-segment: var(--part-run); }
.viewer-tree li[data-paint="done"],
.stagework .viewer-tree li[data-paint="done"] { background: var(--part-done); color: var(--part-done-ink); }
.stagework .viewer-tree li[data-paint="done"]:hover {
  background: linear-gradient(var(--stage-hover-bg), var(--stage-hover-bg)), var(--part-done);
}
.viewer-tree li[data-paint="done"] .part-n,
.viewer-tree li[data-paint="done"] .part-name,
.viewer-tree li[data-paint="done"] .partrow-button,
.viewer-tree li[data-paint="done"] .pill { color: var(--part-done-ink); }
.viewer-tree li[data-paint="done"] .pill::before {
  width: 0.3rem; height: 0.55rem; border-radius: 0; background: transparent;
  border: solid var(--part-done-ink); border-width: 0 2px 2px 0;
  transform: translateY(-0.1rem) rotate(45deg);
}
/* the download mark on a green row: a ring of the row's ink, so the
   circle reads on the green as it reads on the rail */
.viewer-tree li[data-paint="done"] .dl-toggle { box-shadow: 0 0 0 2px var(--part-done-ink); }
/* C.223 (owner 27.10.2026): a finished row is no loud full green. On the
   stage it keeps the normal row ground and says it with the kit's quiet
   done style: a small tick and the state word in the stage's ready ink */
.stagework .viewer-tree li[data-paint="done"],
.stagework .viewer-tree li[data-paint="done"][aria-current="true"],
.stagework .viewer-tree li[data-paint="done"][data-kind-chosen="true"] { background: transparent; color: var(--th-soft); }
.stagework .viewer-tree li[data-paint="done"]:hover { background: var(--stage-hover-bg); }
.stagework .viewer-tree li[data-paint="done"] .part-n { color: var(--th-faint); }
.stagework .viewer-tree li[data-paint="done"] .part-name,
.stagework .viewer-tree li[data-paint="done"] .partrow-button { color: inherit; }
.stagework .viewer-tree li[data-paint="done"] .pill { color: var(--stage-ready-ink); }
.stagework .viewer-tree li[data-paint="done"] .pill::before { border-color: var(--stage-ready-ink); }
.stagework .viewer-tree li[data-paint="done"] .dl-toggle { box-shadow: none; }
/* C.223: the part under a pointer, in the 3D view or in the list: the
   selection's ring at a lighter strength, its identical siblings quieter */
.stagework .viewer-tree li[data-hover="part"] { box-shadow: inset 0 0 0 calc(var(--hairline) * 2) var(--stage-hover-line); }
/* owner 29.10.2026: the row of the part under the pointer in the 3D view
   is lit CLEARLY - the list row's own hover ground under the ring - and
   the list never scrolls to it. A chosen row is lit the same way: its
   ground is a plain row's, so without this the part under the pointer read
   as unlit exactly where the reader had just chosen it; it keeps its two
   rings, which say it is chosen */
.stagework .viewer-tree li[data-hover="part"],
.stagework .viewer-tree li[data-hover="part"][aria-current="true"],
.stagework .viewer-tree li[data-hover="part"][data-kind-chosen="true"],
.stagework .viewer-tree li[data-hover="part"][data-paint="done"][aria-current="true"],
.stagework .viewer-tree li[data-hover="part"][data-paint="done"][data-kind-chosen="true"] { background: var(--stage-file-bg); }
.stagework .viewer-tree li[data-hover="part"][aria-current="true"],
.stagework .viewer-tree li[data-hover="part"][data-kind-chosen="true"] {
  box-shadow: inset 0 0 0 2px var(--stage-hover-line), inset 0 0 0 4px var(--part-done-ink);
}
.stagework .viewer-tree li[data-hover="twin"] { box-shadow: inset 0 0 0 1px var(--th-line-strong); }
/* C.104: the legend under the navigator (job.js shows the paints the rows
   carry) and the swatch it shares with the finder's chips - each swatch
   drawn from the paint's own token and its second cue (data-pattern,
   pipeline.PAINT_PATTERN), as the navigator draws the part */
.paint-legend {
  display: flex; flex-wrap: wrap; gap: var(--s1) var(--s3);
  margin: 0; padding: 0 var(--s1); list-style: none;
  color: var(--th-soft, var(--ink-soft)); font-size: 0.72rem;
}
.paint-legend li { display: inline-flex; align-items: center; gap: var(--gap-icon-label); margin: 0; }
.paint-swatch {
  flex: none; display: inline-block; width: 0.8rem; height: 0.8rem;
  border-radius: 2px; background: var(--part-todo);
}
[data-paint="done"] > .paint-swatch, .paint-swatch[data-paint="done"] { background: var(--part-done); }
[data-paint="todo"] > .paint-swatch, .paint-swatch[data-paint="todo"] { background: var(--part-todo); }
[data-pattern="stripes"] > .paint-swatch, .paint-swatch[data-pattern="stripes"] {
  background: repeating-linear-gradient(135deg, var(--part-run) 0 calc(var(--part-stripe) / 2),
                                        var(--part-todo) 0 var(--part-stripe));
}
[data-pattern="hatch"] > .paint-swatch, .paint-swatch[data-pattern="hatch"] {
  background:
    repeating-linear-gradient(45deg, var(--part-done-ink) 0 1px, transparent 0 calc(var(--part-hatch) / 2)),
    repeating-linear-gradient(135deg, var(--part-done-ink) 0 1px, transparent 0 calc(var(--part-hatch) / 2)),
    var(--part-fail);
}
[data-pattern="faint"] > .paint-swatch, .paint-swatch[data-pattern="faint"] {
  background: var(--part-left); opacity: var(--part-left-alpha);
}
.finder-chip .paint-swatch { margin-right: var(--gap-icon-label); vertical-align: -0.1em; }
/* C.211-B2a (owner 26.10.2026): while the 3D view's kind switch is on,
   a skipped part is orange and a failed one red, fully coloured - the
   two paints follow on every view of the page that reads them (rows,
   legend, chips, the model), so the page keeps one paint per state */
body[data-kinds-3d] {
  --part-left: var(--kind-skipped);
  --part-fail: var(--kind-failed);
  --part-left-alpha: 1;
}
/* C.211-B2a: THE MODEL'S LEGEND, which is also its filter - one entry
   per class the model holds (the two kinds, the part paints with the
   paint legend's own swatches and words, "Bitte prüfen") with its
   swatch and its count; an entry pressed off hides its class in the 3D
   view, "Alle zeigen" brings every class back. Over the model's top
   left corner, out of the page flow (a menu takes no space); folded on
   a phone until opened. It carries the paint key itself, so the paint
   legend under the model stands aside while it is there. */
body[data-kinds-3d] #paint-legend { display: none; }
.model-legend {
  /* owner review 28.10.2026: above every overlay of the 3D view (the
     Sichtseite arrow, the labels), and no wider than its widest row */
  position: absolute; z-index: 4; top: var(--s2); left: var(--s2);
  width: max-content; max-width: calc(100% - 2 * var(--s2));
  background: rgba(20, 32, 52, 0.72); border: 1px solid var(--stage-line, rgba(159, 182, 214, 0.35));
  border-radius: var(--radius-sm); color: var(--stage-soft, var(--ink-soft));
  font-size: 0.66rem; line-height: 1.2;
  /* assembly3d.js (fitLegend) keeps it clear of every control of the
     pane: below the explosion control where they would meet, and no
     lower than the controls at the pane's foot, scrolling inside */
  overflow: auto; overscroll-behavior: contain;
}
.model-legend > summary {
  display: flex; align-items: center; gap: var(--gap-icon-label);
  min-height: 1.4rem; padding: 0 var(--s2); cursor: pointer; list-style: none;
  color: var(--stage-ink, var(--ink));
  /* C.211-B5: the legend's title stays at the top of its own box while the
     compact legend scrolls inside (a short panel at 1024 x 768 with a
     part chosen): the button that folds it is never scrolled away */
  position: sticky; top: 0; z-index: 1;
  background: rgba(20, 32, 52, 0.96);
}
/* folded: the title alone, a small button that opens it */
.model-legend:not([open]) > summary { padding: 0 var(--s2); }
/* round 6: the folded legend's entries take no box at all - a display of
   their own (the symbols column's flex) otherwise lays them out unseen
   below the chip, where a measure finds them cut by it */
#model-legend:not([open]) > :not(summary) { display: none; }
/* owner 29.10.2026: on a desk the title folds the legend to its SYMBOLS
   (`is-compact`, assembly3d.js) - the swatches, the Sichtseite marks and
   the eyes in a narrow column, the title a small arrow that opens it
   again; an entry under the pointer or the keyboard's focus shows its
   words beside its symbols. The fold arrows are a desk's only. */
.model-legend .legend-fold { flex: none; width: 0.8rem; height: 0.8rem; opacity: 0.8; }
.model-legend .legend-fold-out,
.model-legend.is-compact .legend-fold-in,
body.phone-job .model-legend:not(.is-compact) .legend-fold { display: none; }
.model-legend.is-compact .legend-fold-out { display: inline-block; }
.model-legend.is-compact .legend-title,
.model-legend.is-compact .legend-group,
.model-legend.is-compact .legend-view-only,
.model-legend.is-compact .legend-shown,
.model-legend.is-compact .legend-entry .legend-word,
.model-legend.is-compact .legend-symbol { display: none; }
.model-legend.is-compact > summary { justify-content: center; padding: 0 var(--s1); }
/* OWNER LOOK 01.11.2026 (round 6, replacing round 4's one wrapping row):
   THE SYMBOLS FORM IS ONE COLUMN, taller than wide - per entry its swatch
   and its two buttons (the eye, „nur diese zeigen"), the same elements as
   the worded form, side by side and never over each other; no words and
   no counts (an entry's words and count stand in its tooltip and its
   accessible name), the chevron that opens it again at its head; the
   Sichtseite key, the group headings and the drawing group's chip fold
   away with the words, a group the reader opened keeps its entries under
   a hairline */
.model-legend.is-compact > summary { position: static; background: transparent; }
.model-legend.is-compact .model-legend-list { display: flex; flex-direction: column; padding: 0 0 2px; }
.model-legend.is-compact .model-legend-list ~ .model-legend-list:not([hidden]):not([data-legend-folded="true"]) {
  border-top: 1px solid var(--stage-line, var(--line)); padding-top: 2px;
}
.model-legend.is-compact .model-legend-list[hidden] { display: none; }
.model-legend.is-compact .model-legend-list li[hidden] { display: none; }
.model-legend.is-compact .legend-entry { width: auto; flex: none; padding: 0 2px 0 var(--s1); }
.model-legend > summary[aria-disabled="true"] { cursor: default; opacity: 0.55; }
/* manager 01.11.2026: the shown file's name in the legend's head; owner
   look 01.11.2026 (round 6): a label, so the symbols column folds it away
   with the words */
.model-legend .legend-file {
  min-width: 0; max-width: 12rem; overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
  color: var(--stage-soft, var(--ink-soft)); font-weight: 400;
}
.model-legend .legend-file[hidden],
.model-legend.is-compact .legend-file { display: none; }
/* JOB PAGE 9 round 5 (D5): a folded group stands as its chevron chip */
.model-legend .model-legend-list[data-legend-folded="true"] { display: none; }
.legend-group-fold {
  display: inline-flex; align-items: center; gap: 2px; margin: 0; padding: 0 var(--s1);
  min-height: 1.4rem; border: 1px solid var(--stage-line, var(--line)); border-radius: 999px;
  background: transparent; color: inherit; font: inherit; letter-spacing: inherit; text-transform: inherit; cursor: pointer;
}
.legend-group-fold[aria-expanded="true"] .legend-fold-chev { transform: rotate(90deg); }
.model-legend .legend-fold-chev { width: 0.7rem; height: 0.7rem; }
/* D5a: each entry's solo icon - on hover and keyboard focus, always on a
   touch screen; a marked entry wears the accent, the others dim */
.model-legend-list li { display: flex; align-items: center; }
/* audit 01.11.2026: the solo icon always stands - quiet at rest, full on
   hover and focus - so a key and a finger reach it in every legend form */
.legend-solo {
  display: inline-flex; opacity: 0.4; flex: none; align-items: center; justify-content: center;
  width: 1.5rem; min-height: 1.5rem; margin: 0; padding: 0; border: 0; border-radius: 2px;
  background: transparent; color: inherit; cursor: pointer;
}
.legend-solo .kit-icon { width: 0.85rem; height: 0.85rem; }
.model-legend-list li:hover > .legend-solo,
.model-legend-list li:focus-within > .legend-solo,
.model-legend-list li.is-solo > .legend-solo { opacity: 1; }
@media (hover: none) { .model-legend-list li > .legend-solo { opacity: 1; } }
.model-legend-list li.is-solo > .legend-entry { box-shadow: inset 0 0 0 1px var(--stage-hover-line, var(--accent)); }
.model-legend-list li.is-solo > .legend-solo { color: var(--stage-hover-line, var(--accent)); }
.model-legend-list li.is-dimmed { opacity: 0.5; }
/* on a phone the title is a finger's control: the kit's tap size (P5) */
body.phone-job .model-legend > summary { min-height: var(--tap); min-width: var(--tap); box-sizing: border-box; }
.model-legend > summary::-webkit-details-marker { display: none; }
.model-legend-list {
  display: flex; flex-direction: column; gap: 0; margin: 0; padding: 0 var(--s1) var(--s1); list-style: none;
}
.model-legend-list li { margin: 0; }
.legend-entry {
  display: flex; align-items: center; justify-content: flex-start; gap: var(--gap-icon-label); width: 100%;
  /* the eye's target at least 24 px at a desk (owner 28.10.2026) */
  min-height: 1.5rem; padding: 0 var(--s1); margin: 0;
  border: 0; border-radius: 2px; background: transparent; color: inherit;
  font: inherit; text-align: left; cursor: pointer;
}
.legend-entry:hover { background: var(--stage-button-hover, rgba(123, 176, 240, 0.12)); }
/* a class pressed off: its words dimmed and a crossed eye - never struck
   through, which reads as "left out of the download" (owner 26.10.2026) */
.legend-entry[aria-pressed="false"] { color: var(--stage-faint, var(--ink-faint)); }
.legend-entry .legend-word { flex: 1 1 auto; }
.model-legend .legend-eye { flex: none; width: 0.9rem; height: 0.9rem; opacity: 0.8; }
.legend-entry[aria-pressed="true"] .legend-eye-off,
.legend-entry[aria-pressed="false"] .legend-eye-on { display: none; }
/* the legend's own group line, never a page paragraph: the page's rhythm
   for a paragraph that holds a button (p:has(> button), 32 px above and
   below) stood the drawing group's chip 64 px taller than its words and
   held the worded legend back where it fits (round 7, 03.11.2026) */
.model-legend .legend-group {
  margin: var(--s1) var(--s2) 0; font-size: 0.6rem; letter-spacing: 0.04em;
  text-transform: uppercase; color: var(--stage-faint, var(--ink-faint));
}
.legend-view-only { margin: var(--s1) var(--s2) 0; color: var(--stage-ink, var(--ink)); }
/* the quiet dot between the two symbols of the key row, drawn, no character */
.legend-sep {
  flex: none; width: 3px; height: 3px; margin: 0 2px; border-radius: 50%;
  background: var(--stage-faint, var(--ink-faint));
}
.legend-shown { margin: 0 var(--s2); color: var(--stage-soft, var(--ink-soft)); }
/* the key to the Sichtseite symbol: not a filter, the symbol as the
   model draws it on a selected plate (.kind-arrow) */
.legend-symbol {
  display: flex; align-items: center; gap: var(--gap-icon-label);
  min-height: 1.15rem; padding: 0 var(--s1);
}
.model-legend .legend-side {
  flex: none; width: 0.85rem; height: 0.85rem; color: var(--select-outline);
  filter: drop-shadow(0 0 1px var(--select-halo));
}
.legend-entry[aria-pressed="false"] .paint-swatch { opacity: 0.35; }
/* each legend class's swatch, as the model draws it: the kinds in their
   tones, drawn as half beam and half plate in full tone, not drawn yet
   the same faded, skipped and failed in their paints, "Bitte prüfen" as
   its dashed outline */
.paint-swatch[data-legend="beams"] { background: var(--kind-beam); }
.paint-swatch[data-legend="plates"] {
  background: repeating-linear-gradient(90deg, var(--kind-plate) 0 3px, var(--kind-beam) 3px 4px);
}
/* owner 01.11.2026: the „Bitte prüfen" symbol IS the 3D view's style - the
   dashed --check-outline at the width, dash and strength partstyle.js
   hands over (--check-px, --check-dash-px, --check-alpha): each edge one
   dash-and-gap period of the view's own dash, centred on the edge, so the
   small square reads as a dashed outline with open corners */
.paint-swatch[data-legend="check"] {
  --check-dash-x: linear-gradient(90deg, transparent 0 calc(var(--check-dash-px) / 2), var(--check-outline) 0 calc(var(--check-dash-px) * 1.5), transparent 0);
  --check-dash-y: linear-gradient(180deg, transparent 0 calc(var(--check-dash-px) / 2), var(--check-outline) 0 calc(var(--check-dash-px) * 1.5), transparent 0);
  background:
    var(--check-dash-x) center top / calc(2 * var(--check-dash-px)) var(--check-px) repeat-x,
    var(--check-dash-x) center bottom / calc(2 * var(--check-dash-px)) var(--check-px) repeat-x,
    var(--check-dash-y) left center / var(--check-px) calc(2 * var(--check-dash-px)) repeat-y,
    var(--check-dash-y) right center / var(--check-px) calc(2 * var(--check-dash-px)) repeat-y;
  opacity: var(--check-alpha);
}
.paint-swatch[data-legend="drawn"] {
  background: linear-gradient(90deg, var(--kind-beam) 50%, var(--kind-plate) 50%);
}
.paint-swatch[data-legend="not_drawn"] {
  background: linear-gradient(90deg,
    color-mix(in srgb, var(--kind-beam), var(--kind-pending) calc(var(--kind-pending-mix) * 100%)) 50%,
    color-mix(in srgb, var(--kind-plate), var(--kind-pending) calc(var(--kind-pending-mix) * 100%)) 50%);
}
.paint-swatch[data-legend="skipped"] { background: var(--kind-skipped); }
.paint-swatch[data-legend="failed"] {
  background:
    repeating-linear-gradient(45deg, var(--part-done-ink) 0 1px, transparent 0 calc(var(--part-hatch) / 2)),
    repeating-linear-gradient(135deg, var(--part-done-ink) 0 1px, transparent 0 calc(var(--part-hatch) / 2)),
    var(--kind-failed);
}
/* C.211-B2a: the "Sichtseite" arrow over the model - drawn by
   assembly3d.js from the plate facts, never in the page flow, never a
   target for the pointer; neutral like the selection it belongs to,
   held off every ground by the selection's dark halo */
.kind-arrow {
  position: absolute; left: 0; top: 0; overflow: visible; pointer-events: none; z-index: 1;
  filter: drop-shadow(0 0 1px var(--select-halo)) drop-shadow(0 0 1.5px var(--select-halo));
}
.kind-arrow line, .kind-arrow circle.ring { stroke: var(--select-outline); stroke-width: 2.5; fill: none; }
.kind-arrow polygon, .kind-arrow circle.dot { fill: var(--select-outline); }
/* the arrow's foot: a disc lying in the face it leaves (owner 26.10.2026) */
.kind-arrow polygon.foot {
  fill: var(--select-outline); fill-opacity: 0.35;
  stroke: var(--select-outline); stroke-width: 1.5; stroke-linejoin: round;
}
.kind-arrow text {
  fill: var(--select-outline); font-size: 12px; font-family: var(--font);
  paint-order: stroke; stroke: var(--select-halo); stroke-width: 3px;
}
/* the one-time hint on the part colours speaks of the state colours the
   model no longer wears while it shows the kinds; its legend says it */
body[data-kinds-3d] #paint-hint { display: none; }
/* on a phone the legend stands at the model pane's foot only while work
   is owed or held; the finder's chips carry the key the rest of the time */
body.phone-job .paint-legend { flex: none; padding: var(--s1) var(--s2); }
body.phone-job .paint-legend[data-live="false"] { display: none; }
.stagework .listnote, .stagework #live-note { color: var(--th-faint); font-size: 0.72rem; }

/* the dock at the rail's foot */
.stagework .download-dock { background: transparent; border: 0; border-top: 1px solid var(--th-line); border-radius: 0; box-shadow: none; padding: var(--s2) 0 0; color: var(--th-soft); }
.stagework .dock-summary { background: rgba(47, 107, 61, 0.28); color: var(--stage-file-ink); font-size: 0.76rem; }
.stagework .download-dock[data-dock-state="drawing"] .dock-summary,
.stagework .download-dock[data-dock-state="anonymous"] .dock-summary { background: rgba(255, 255, 255, 0.07); }
.stagework .dock-reason, .stagework .dock-prepared, .stagework .dock-cost, .stagework .dock-anon-retention, .stagework .dock-guest-count { color: var(--th-faint); }
.stagework .price-box { color: var(--th-ink); }
.stagework .pb-link { color: var(--stage-sel-soft); }
.stagework .dock-reason a, .stagework .dock-existing { color: var(--stage-sel-soft); }
.stagework .dock-anon-note { color: var(--th-ink); }
.stagework .dock-anon-note a { color: var(--stage-sel-soft); }
.stagework .dock-secondary > * { background: var(--stage-button-bg); color: var(--th-ink); border: 1px solid var(--th-line-strong); font-weight: 600; font-size: 0.78rem; padding: 0.4rem 0.5rem; }
.stagework .dock-secondary > *:hover { background: var(--stage-button-hover); filter: none; }
.stagework .dock-stamp.is-incomplete { border-color: #c08a5a; }
.stagework .dock-stamp-dot { background: #c9a227; }
.stagework .dock-secondary > .button-destructive { border-color: var(--stage-fault); color: var(--stage-fault); }
/* C.78: the result of the stop stands where its control stood - a line
   of words, not a chip */
.stagework .dock-secondary > .dock-result { background: none; border: 0; color: var(--th-soft); font-weight: 400; padding: 0.4rem 0; }
.stagework .download-dock-preparing { color: var(--th-soft); }
.stagework .download-dock-action { font-size: 0.92rem; padding: 0.55rem 0.6rem; }
.stagework .dock-cost, .stagework .dock-prepared { font-size: 0.72rem; line-height: 1.3; }
.stagework .dock-anon-doors .button-ghost { background: var(--stage-button-bg); color: var(--th-ink); border-color: var(--th-line-strong); }

/* ===================================================================
   THE RAIL REFLOW (C.24, owner 14.09.2026: "rows with multiple
   sub-rows collapse to single rows ... this causes height jumps of
   some widgets in the right menu which look unprofessional. Can those
   also adapt their height in animation and rearrange their content in
   animation too? It is important that the expansion of the right menu
   remains fluid".)

   THE CAUSE, named rather than worked around: what animates is the
   lane's WIDTH, and every sentence in the rail is sized by that width,
   so the browser re-wrapped the rail's whole content at each
   intermediate width. A line that is two rows narrow and one row wide
   fell to one row somewhere in the middle of the movement, and that
   fall is the jump. Measured on the owner's 68-part batch before this
   round: the cue line 36,1 -> 16,8 px in ONE frame at 150 ms, the
   dock's reason sentence 28,4 -> 14,2 px at 124 ms, the cost line
   another 14,9 px at 78 ms, and the parts list stepping three times
   behind them as it absorbed what they gave up.

   THE CURE, three parts on the one clock above:

   (1) job.js pins the rail's INNER box to the width the rail is going
       to have, for the movement's duration. The content is laid out
       ONCE, at the target, from the first frame; the lane's own box
       then only reveals it, because `.viewer-side` already clips. No
       text is measured again per frame, which is also what keeps the
       frame rate: the layout is paid for once instead of once a frame.
   (2) every box whose height really differs between the two widths
       carries `.rail-flip` for the duration — its height is set to the
       MEASURED old value and transitions to the MEASURED new one, then
       is released to `auto`. Nothing steps.
   (3) the wrapping that is being replaced stays on screen as
       `.rail-ghost`, a copy of the box at its old width lying over the
       new one, and fades out on the same clock, so the rearrangement
       of the content is a dissolve and not a snap.

   Under `prefers-reduced-motion` none of it runs: job.js takes the
   final state at once, which is this page's existing rule.
   =================================================================== */
/* the target width, MEASURED and never copied into the script: a
   custom property does not transition, so `--viewer-side` already
   stands at its new value the moment the pointer arrives while the
   grid track is still on its way — this box is therefore what the rail
   is going to be, and job.js reads it off the page */
.rail-probe {
  position: absolute; left: 0; top: 0; height: 0;
  width: var(--viewer-side); visibility: hidden; pointer-events: none;
}
/* BOTH ways the inner box, already at the width the rail is going to
   have, hangs on the rail's fixed right edge and does not travel: the
   lane's moving edge sweeps outward and reveals content that is already
   where it will stay, or sweeps back over empty ground and closes onto
   content that never moved. C.74 (PAGE_DESIGN_LAWS section 19, the C.78
   finding): on the way OUT the box used to hang on the moving LEFT edge,
   so everything in the rail travelled left with it the moment the
   pointer entered — the stop control's place was taken by the Plankopf
   chip under a pointer that had not moved. `unsafe` because the box is
   wider than the rail while it opens, and it must overflow to the left,
   under the clip, not to the right. */
.viewer-side.is-reflowing .viewer-side-body { align-self: flex-end; align-self: unsafe flex-end; }
/* ...and the dock's CONTROL rows keep the rail's REST width at the
   rail's right edge, so no control moves while the lane opens and
   closes (C.74: the Plankopf chip took the stop control's place under a
   pointer that had not moved). C.93 (owner finding 27.09.2026 17:40,
   RAIL HEIGHT LAW): the dock itself is as wide as the rail — its WORDS
   re-wrap to the wide lane, so the foot is only as tall as its content
   and the parts list takes the room the shorter foot gives back; a foot
   frozen at the rest width left a third of the wide rail dead. The
   control width is the rest token less the rail's own frame, read as
   the difference between the lane's token and the box the dock stands
   in — no padding number is copied here. */
@media (min-width: 60.001rem) {
  .stagework .download-dock > .dock-primary,
  .stagework .download-dock > .dock-anon-doors,
  .stagework .download-dock > .dock-attach,
  .stagework .download-dock > .dock-secondary {
    justify-self: end;
    width: calc(var(--viewer-side-rest) - var(--viewer-side) + 100%);
  }
}
.rail-flip {
  position: relative; overflow: hidden; will-change: height;
  transition: height var(--rail-ms) var(--rail-ease);
}
.rail-ghost {
  position: absolute; left: 0; top: 0; z-index: 1; margin: 0;
  pointer-events: none; opacity: 1;
  transition: opacity var(--rail-ms) var(--rail-ease);
}
.rail-ghost.is-gone { opacity: 0; }

/* reduced motion: the idle handle wears a steady ring instead of the
   pulse, and the rail's reflow does not animate at all — job.js takes
   the final state at once and these two rules are the second lock on
   it, so a height or a ghost that was left behind cannot glide */
@media (prefers-reduced-motion: reduce) {
  .explode-control.is-idle .explode-pulse {
    animation: none; box-shadow: 0 0 0 4px rgba(123, 176, 240, 0.45);
  }
  .stagework .assembly-inset, .rail-flip, .rail-ghost { transition: none; }
}

/* THE SETTINGS PANEL (C.46): one popup, three tabs — Plankopf, Zeichnung,
   Papier — on the start page, the job page and the account page. The
   strip is the kit's tabs (C.58j: kit/kit.css draws them, kit/popup.js
   makes them tabs); the kit marks a wired group, and each pane's own
   heading folds away there, because the tab names the pane. Without the
   script the panes stand one under the other with their headings. The
   strip stands in the panel's flow, so it takes the panel's edges and
   not the popup head's inset. */
[data-settings-panel] .settings-tabs { padding-inline: 0; margin: 0 0 var(--rhythm-within); }
.settings-pane[hidden] { display: none; }
.settings-pane-heading { margin: var(--rhythm-between) 0 var(--rhythm-within); }
[data-kit-tabs-wired] .settings-pane-heading { display: none; }
/* C.196 (owner complaint 19.10.2026, the first paint is the page): where
   the scripts will run (kit/scripted.js marks the document before its
   first paint) the panel paints as the kit will leave it - the pane the
   server opened (`data-settings-active`, written by panel_attrs) without
   its heading - before the kit has wired it; until C.196 every pane and
   heading painted first and two of them went a moment later. */
.kit-scripted [data-settings-panel]:not([data-kit-tabs-wired]) .settings-pane-heading { display: none; }
.kit-scripted [data-settings-active="plankopf"]:not([data-kit-tabs-wired]) .settings-pane:not([data-pane="plankopf"]),
.kit-scripted [data-settings-active="zeichnung"]:not([data-kit-tabs-wired]) .settings-pane:not([data-pane="zeichnung"]),
.kit-scripted [data-settings-active="papier"]:not([data-kit-tabs-wired]) .settings-pane:not([data-pane="papier"]) { display: none; }
.settings-subheading {
  margin: var(--rhythm-between) 0 var(--rhythm-within);
  font-size: 0.95rem; font-weight: 650; color: var(--ink-soft);
}
.settings-fieldset { border: 0; padding: 0; margin: 0; min-width: 0; }
.settings-fieldset:disabled { opacity: 0.6; }
.settings-not-ready { font-weight: 600; color: var(--ink); }
.settings-mount-note { margin: 0 0 var(--rhythm-within); }
/* C.158: while typing, the note about where the settings apply gives its
   room to the field, its save and the preview (kit/keyboard.js) */
:root[data-kb] .kit-pop[open] .settings-mount-note { display: none; }
.scales-allowed {
  display: flex; flex-wrap: wrap; gap: var(--s2); margin: 0 0 var(--s2);
}
.scales-allowed .viewset-option small { color: var(--ink-faint); font-size: 0.75em; }
.settings-defaults { display: inline-flex; align-items: center; gap: var(--s2); flex-wrap: wrap; }
.settings-defaults-status { display: none; margin: 0; }
.settings-defaults-status.is-shown { display: inline; color: var(--accent); font-weight: 600; }
/* C.195: a refused or failed save is said beside its button, in the
   refusal's ink */
.settings-defaults-status.is-shown.is-refused { color: var(--bad); }
.settings-defaults-signin { margin: 0; }
.settings-redraw-actions { display: flex; flex-wrap: wrap; gap: var(--s2); align-items: center; }
.settings-popup .font-controls { margin-bottom: var(--rhythm-within); }

/* the start page's action bar: one settings button and the line that
   says what this upload will be drawn as (C.46) */
.start-settings-summary {
  flex: 1 1 12rem; min-width: 0; font-size: 0.85rem; color: var(--ink-soft);
  line-height: 1.3; align-self: center;
}
.start-settings-summary .stamp-state { font-size: inherit; }
@media (max-width: 40rem) {
  .start-settings-summary { flex-basis: 100%; }
}


/* THE SECOND LOOK (owner 22.09.2026): sections, rows, swatches, folds */
/* THE GROUP'S OWN AIR (PAGE_DESIGN_LAWS 1): 16 px above the header,
   8 px under it, the help line 8 px under the controls it explains —
   the rhythm token for "to what it belongs to" — and 24 px down to the
   hairline that ends the group. Every one of them a token, because a
   length typed here is a length that drifts. */
.settings-section { padding: var(--s4) 0 var(--s5); border-top: 1px solid var(--line); }
/* the first group keeps the air above its header — the hairline is
   what it does not need (PAGE_DESIGN_LAWS 1) */
.settings-section:first-child { border-top: 0; }
.settings-section-heading {
  margin: 0 0 var(--s2); font-size: 0.9rem; font-weight: 650; color: var(--ink);
}
.settings-section > .help { margin: var(--s2) 0 0; }
.settings-row { display: flex; flex-wrap: wrap; gap: var(--s2) var(--s4); align-items: center; }
.settings-row .check { margin: 0; }
.settings-compact select { min-width: 9rem; }
.settings-grid { display: grid; gap: var(--s3) var(--s4); grid-template-columns: repeat(2, minmax(0, 1fr)); }
.settings-grid .span-2 { grid-column: 1 / -1; }
.settings-readonly { margin: 0; }
.settings-readonly > span:first-child { display: block; font-weight: 600; font-size: 0.85rem; color: var(--ink-soft); }
.settings-value { margin: 0; }
.field-label { display: block; font-weight: 600; font-size: 0.85rem; color: var(--ink-soft); margin-bottom: var(--s1); }
.swatch-cell { min-width: 0; }
.swatch-cell abbundo-color-picker { display: block; }
.swatch-switch { margin-left: auto; }
/* THE PAGE BEHIND A POPUP DOES NOT MOVE (PAGE_DESIGN_LAWS 5 and 6).
   Nothing in this site scrolls it — measured, with every scroll call
   in the page instrumented — and it moved anyway: a dialog stands in
   the top layer but its content is still the document's, so the
   browser's own scroll anchoring re-aimed the page behind at the
   question that had just opened inside the popup, a thousand pixels
   away. A dialog's content is never the page's anchor. */
dialog, dialog * { overflow-anchor: none; }

/* THE QUESTIONS (PAGE_DESIGN_LAWS 6): the section stands open, each
   question is a row that opens on its own, and nothing here clips or
   fixes a height — an opened answer makes the page taller, which is
   what lets a reader scroll on to the next question at once. */
.faq-fold { margin-top: var(--rhythm-between); border-top: 1px solid var(--line); padding-top: var(--s3); }
/* C.145b: a tab's questions in one closed fold - the fold's own row
   carries the rule, so the section draws no second one above it */
.faq-fold:has(> .kit-acc > [data-faq-fold]) { border-top: 0; padding-top: 0; }
.faq-heading { margin: 0 0 var(--s2); font-size: 1rem; font-weight: 650; }
.faq-row { border-top: 1px solid var(--line); }
.faq-row:first-of-type { border-top: 0; }
.faq-question { font-weight: 600; cursor: pointer; padding: var(--s2) 0; }
.faq-answer { margin: 0 0 var(--s3); color: var(--ink-soft); }
.stamp-advanced { margin-top: var(--rhythm-between); border-top: 1px solid var(--line); padding-top: var(--s3); }
.stamp-advanced > summary { font-weight: 650; cursor: pointer; }
.stamp-advanced > .stack { margin-top: var(--s3); }
.stamp-logo-setting .stamp-logo-drop { margin: var(--s2) 0; }
/* The lettering comparison's two frames (owner 22.09.2026): the crop is
   a real picture now, at the size the server cut it, so the button is
   no longer a fixed window onto a zoomed background and simply takes
   the height of what is in it. It cut what it held until the C.45/46
   close — an "overflow: hidden" kept from the zoomed-window days, when
   the box had a fixed height and something had to give. A box that
   grows cuts nothing, and nothing that grows in here may be cut: the
   caption under it is prose. */
.font-preview-detail { height: auto; background: #fff; }
.font-preview-crop {
  display: block; width: 100%; height: auto;
  border-radius: calc(var(--radius-sm) - 1px);
}
@media (max-width: 40rem) {
  .settings-grid { grid-template-columns: 1fr; }
  .swatch-switch { margin-left: 0; }
}

/* THE TOAST (owner 22.09.2026): a confirmation that overlays the page
   and inserts no height, so nothing under it moves. */
.saved-toast {
  position: fixed; left: 50%; bottom: 1.25rem; transform: translateX(-50%);
  z-index: 60; padding: var(--s2) var(--s4);
  background: var(--ink); color: var(--paper); border-radius: var(--radius);
  box-shadow: var(--shadow); font-weight: 600; pointer-events: none;
  opacity: 0; transition: opacity 0.2s ease;
}
.saved-toast.is-shown { opacity: 1; }
/* the save's own word, beside the control that saved (design law 7) */
.saved-status { margin-left: var(--s2); font-weight: 600; color: var(--good, var(--ink)); }
.saved-status:empty { display: none; }
/* the colour's note under its own tile, greyed with the tile */
.swatch-cell .depends-note { display: block; margin-top: var(--s1); }
.check-state { margin-left: var(--s2); }
/* a lettering tile at work: a spinner over the picture until it lands */
.font-preview-detail { position: relative; }
.font-preview-detail.is-loading img { opacity: 0.45; }
.font-preview-detail.is-loading::after {
  content: ""; position: absolute; left: 50%; top: 50%;
  width: 1.6rem; height: 1.6rem; margin: -0.8rem 0 0 -0.8rem;
  border: 3px solid var(--line); border-top-color: var(--accent, var(--ink));
  border-radius: 50%; animation: font-tile-spin 0.8s linear infinite;
}
@keyframes font-tile-spin { to { transform: rotate(360deg); } }
/* the title-block picture at work (owner's look 23.09.2026, 13:10).
   NO `position` here: the picture is `position: sticky` (C.7 above),
   which already holds the spinner's absolute layer. A `relative` on the
   same selector, later in the file, overrode the sticky one and turned
   its `top` into a shift down over the fields (owner 23.09.2026, 14:45). */
.stamp-live.is-loading img { opacity: 0.5; }
.stamp-live.is-loading::after {
  content: ""; position: absolute; left: 50%; top: 50%;
  width: 1.6rem; height: 1.6rem; margin: -0.8rem 0 0 -0.8rem;
  border: 3px solid var(--line); border-top-color: var(--accent, var(--ink));
  border-radius: 50%; animation: font-tile-spin 0.8s linear infinite;
}
@media (prefers-reduced-motion: reduce) {
  .stamp-live.is-loading::after { animation-duration: 2.4s; }
}
/* the identical-parts pair: each switch with its own line beneath it */
.parts-pair { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: var(--s3); }
.parts-switch .check-state { display: block; margin: var(--rhythm-within, var(--s1)) 0 0; }
.depends-unmet .check-state { visibility: hidden; }
@media (max-width: 40rem) { .parts-pair { grid-template-columns: 1fr; } }
@media (prefers-reduced-motion: reduce) {
  .font-preview-detail.is-loading::after { animation-duration: 2.4s; }
}

/* THE FOUR COLOUR LABELS SHARE ONE LINE (C.91, from the C.58m pictures
   of 27.09.2026: the greyed "Projektion" label stood higher than the
   other three). The row is a `.settings-row` as well, and that rule
   centres every cell on the row's cross axis — right for a row of
   controls of one height, wrong here, where the fourth cell carries the
   colour's dependency note under its swatch and is taller than its
   three neighbours: centring a taller cell lifts everything in it. The
   cells start at the top instead, so the four labels stand on one line
   whatever a cell carries beneath its swatch. The grid is stated ONCE
   (it stood twice in this file, with two different gaps). */
.swatch-row { display: grid; grid-template-columns: repeat(4, minmax(0, 1fr)); gap: var(--s2); align-items: start; }
.swatch-row .swatch-cell { min-width: 0; }
@media (max-width: 40rem) {
  .swatch-row { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}

/* AN OPEN POPUP HOLDS THE PAGE STILL (owner 23.09.2026), by
   CONTAINMENT — the viewer's instrument, never a lock on the document:
   every dialog is a scroll container that stops the chain at its own
   edge, whether it has more to show or not; fields.js answers the
   surround and the scrolling keys. */
dialog[open] { overflow-y: auto; overscroll-behavior: contain; }
/* A GROWING FIELD opens one line high (fields.js sizes it); it never
   shows a resize handle that would fight the growing */
textarea:not([data-no-grow]) { resize: none; }

/* THE PICTURE COVERS NOTHING (owner 23.09.2026, 14:45): inside a popup
   the picture stands still above the fields, which scroll in a box of
   their own directly under it (stampwidget.js sizes the box), so no
   field can ever stand under the picture. */
.stamp-pinned .stamp-live { position: static; }
/* C.160 (owner's ruling through the coordinator, 10.10.2026): where the
   popup's body still scrolls - the job's Plankopf tab, down to its
   questions - the picture is a sticky head stacked directly under the
   tab strip (`data-sticky-head`, set by stampwidget.js; kit/stickyfoot.js
   writes its `top` under the strip and lets it leave whole once its form
   ends), so the two never overlap at any scroll position. A field the
   reader brings into view stops below it (the head's reserve), and the
   saved-values list reveals its field in the band below it, never by a
   jump to the top (KitStickyFoot.reveal). */
.kit-pop-body .stamp-pinned .stamp-live[data-sticky-head] {
  position: sticky;
  top: calc(-1 * var(--s4));
  z-index: 3;
}
/* ...except while the phone's keyboard is open (kit/keyboard.js marks the
   root `data-kb`, C.158): then the strip above it has given its room
   away, and the keyboard law keeps the picture in the free band beside
   the field itself (its `data-kb-keep`); a picture still stuck at the
   top took that band and pushed the field's own controls under the foot
   (keyboard-keeps-controls, 360 x 740, job Plankopf, 11.10.2026) */
:root[data-kb] .kit-pop-body .stamp-pinned .stamp-live[data-sticky-head] {
  position: static;
}
.stamp-fields-scroll { overflow-y: auto; overscroll-behavior: contain;
  scroll-padding-top: var(--s2); }
.stamp-pinned .stamp-fields-scroll :where(input, select, textarea, .settings-value) {
  scroll-margin-top: var(--s2); }

/* C.86 THE SETTINGS FOOT (PAGE_DESIGN_LAWS sections 22 and 23): three
   actions under every tab of the job settings popup, each with the one
   line beside it that says what it does or why it waits. */
.settings-foot { border-top: 1px solid var(--line); padding-top: 16px; margin-top: 16px; }
.settings-foot-actions { display: flex; flex-wrap: wrap; gap: 16px; align-items: flex-start; }
/* C.158: while typing, the actions stand without their reason lines, so
   the foot leaves the field, its save and the preview their room */
:root[data-kb] .kit-pop[open] .settings-foot-reason { display: none; }
.settings-foot-action { display: inline-flex; flex-direction: column; gap: 8px; max-width: 18rem; }
.settings-foot-reason:empty { display: none; }
/* C.195: the server's word about a save made in place - "Gespeichert."
   in the good ink, a quoted refusal in the refusal's ink */
.settings-foot-reason.is-said { color: var(--good); }
.settings-foot-reason.is-said.is-refused { color: var(--bad); }
.settings-foot-confirm { position: sticky; top: 0; z-index: 2; }

/* ==== C.96 — THE JOB PAGE ON A PHONE, LAYOUT C (owner 28.09.2026 02:15) ====
   One frame divides the phone's height once: the site header, the status
   strip (the job bar), the sheet pane (#viewer), the model pane
   (#viewer-side), the foot line and the thumb bar. The page never
   scrolls; the layers (finder, "Mehr", "Auftrag") open over the model's
   side of the frame without resizing it. jobphone.js puts `phone-job` on
   the body at this width and moves the page's own controls into their
   phone places; every rule below is scoped to that class, so the desktop
   page and a phone with the script blocked never meet one of them.
   The laws and what their gate measures: SCOPE.md section 3 C, P1-P16
   (gate phone-job-page). */
.phone-only, .label-phone { display: none; }
/* job page 9 round 4 (scope 3, S3 and S4): THE DESK'S PARTS FINDER above
   the parts list - the phone finder's chips (one resource, finder_chips)
   and the jump field; a row the chips or the words leave out is gone from
   the list. The phone keeps its finder layer and never shows this one. */
.panel-finder { flex: none; display: flex; flex-direction: column; gap: var(--s1); }
.panel-finder[hidden] { display: none; }
.panel-finder .finder-chips { display: flex; flex-wrap: wrap; gap: var(--s1); }
.panel-finder .finder-chip {
  min-height: 1.75rem; margin: 0; padding: 0 var(--s2); border-radius: 999px;
  border: 1px solid var(--th-line-strong, var(--line)); background: transparent;
  color: var(--th-soft, var(--ink-soft)); font: inherit; font-size: 0.78rem; cursor: pointer;
}
.panel-finder .finder-chip[hidden] { display: none; }
.panel-finder .finder-chip[aria-pressed="true"]:not([data-chip="all"]) {
  background: var(--stage-search-active-soft); color: var(--stage-ink);
  border-color: var(--stage-search-active); box-shadow: inset 0 0 0 1px var(--stage-search-active);
}
.panel-finder .finder-chip[aria-pressed="true"][data-chip="all"] { color: var(--th-ink, var(--ink)); border-color: var(--th-ink, var(--ink)); }
.panel-finder .finder-search input {
  width: 100%; box-sizing: border-box; margin: 0;
  background: var(--stage-field); color: var(--stage-ink); border-color: var(--stage-field-line);
}
.panel-finder .kit-search-count { color: var(--th-soft); font-size: 0.72rem; }
.panel-finder .finder-jump-why[hidden], .panel-finder .kit-search-empty[hidden] { display: none; }
.viewer-tree li.finder-out { display: none; }
/* S5: a file header's extras - amber for the plates to check, red for the
   parts not drawn - the only coloured words besides the rows' own */
.viewer-tree .file-extras { display: inline-flex; gap: var(--s1); font-size: 0.72rem; font-weight: 400; }
.viewer-tree .file-extras [hidden] { display: none; }
.viewer-tree .file-extra-check::before, .viewer-tree .file-extra-refused::before { content: "· "; color: var(--th-faint, var(--ink-faint)); }
.viewer-tree .file-extra-check { color: var(--stage-attention); }
.viewer-tree .file-extra-refused { color: var(--stage-fault, var(--bad)); }
/* round 4 (K8, R1): a stage with no sheet has nothing to zoom */
.viewer.stage:has(#viewer-image[hidden]) .viewer-zoom-controls { display: none; }
@media (max-width: 60rem) {
  body.phone-job .panel-finder { display: none; }
}
@media (max-width: 60rem) {
  body.phone-job .label-desk { display: none; }
  body.phone-job .label-phone { display: inline; }
  /* SPEC 20 at phone width (C.96 law P1): in the phone frame the job page
     is one viewport, as on a desktop - the same document rule, asked of
     the stage grid and of the frame the script switched on */
  html.has-stagework:has(> .phone-job) { height: 100%; overflow: hidden; overscroll-behavior: none; }
  .phone-job.has-stagework { overflow: hidden; overscroll-behavior: none; }
  body.phone-job {
    height: 100vh; height: 100dvh;
    display: flex; flex-direction: column;
    /* the containing block of every absolutely placed helper (the extras
       panel's screen-reader summary), so none reaches past the glass */
    position: relative;
  }
  body.phone-job > .site-header { flex: none; position: relative; }
  body.phone-job > .site-footer { display: none; }
  body.phone-job > main {
    flex: 1 1 auto; min-height: 0; display: flex; flex-direction: column;
  }
  /* the frame's boxes clip what lies outside the glass; what a reader
     reads scrolls inside a layer, the finder's list or the zoomed sheet */
  .phone-job > main, .phone-job .stagework, .phone-job .viewer.stage,
  .phone-job .stagework .viewer-side, .phone-job .stagework .viewer-side-body { overflow: hidden; }

  /* -- the status strip: the job bar's state word and its one count, the
        stop control beside the progress it stops, and (i) -- */
  body.phone-job .jobtop {
    position: relative; top: auto; flex: none; z-index: 6;
    padding: 0; border-bottom: 1px solid var(--line); cursor: pointer;
  }
  body.phone-job .jobtop > .wrap-wide { width: 100%; padding: 0 var(--s1) 0 var(--s3); max-width: none; }
  body.phone-job .stagework.wrap-wide { width: 100%; margin: 0; max-width: none; }
  body.phone-job .jobtop-line {
    flex-wrap: wrap; align-items: center; gap: 0 var(--s2); min-height: var(--tap);
  }
  /* the state word and the count flow as one sentence in the room the
     strip's two controls leave, over two lines at most */
  body.phone-job .phone-strip-state {
    display: block; flex: 1 1 0; min-width: 0; padding-block: var(--s1);
    font-size: 0.85rem; line-height: 1.3; color: var(--ink);
  }
  body.phone-job .phone-strip-state #job-status {
    display: inline; margin: 0 var(--s1) 0 0; padding: 0; border: 0; background: none;
    font-size: inherit; font-weight: 600; color: inherit;
  }
  body.phone-job .phone-strip-state #job-status.is-said { display: none; }
  body.phone-job .phone-strip-state .job-progress-line {
    display: inline; margin: 0; padding: 0; font-size: inherit; line-height: inherit; color: var(--ink-soft);
  }
  body.phone-job .phone-strip-tools {
    display: flex; flex: none; align-items: center; gap: var(--s1); margin-left: auto;
  }
  /* job page 9: on a phone the strip is the pill and the count; the
     title, the next line, the deletion moment and the desk menu stand
     down (the menu's facts and actions are in the (i) layer), and the
     split handle with its swap is a desk control */
  body.phone-job .jobtop .jobbar-title,
  body.phone-job .jobtop .job-next-line,
  body.phone-job .jobtop .jobbar-deletion,
  body.phone-job .jobtop .jobbar-menu,
  body.phone-job .split-handle,
  body.phone-job .stage-model-host { display: none; }
  body.phone-job .jobbar-words { display: none; }
  body.phone-job .jobbar-actions { margin-bottom: var(--s3); border-top: 0; padding-top: 0; }
  body.phone-job .jobbar-actions .job-cancel-button,
  body.phone-job .jobbar-actions .job-delete-button { min-height: var(--tap); }
  body.phone-job .phone-strip-info { display: inline-flex; }
  body.phone-job .phone-strip-info, body.phone-job .phone-menu {
    align-items: center; justify-content: center; flex: none;
    width: var(--tap); height: var(--tap); margin: 0; padding: 0;
    border: 0; background: transparent; color: var(--ink-soft); font: inherit; cursor: pointer;
  }
  body.phone-job .phone-strip-info > span {
    display: inline-flex; align-items: center; justify-content: center;
    width: 1.6rem; height: 1.6rem; border: 1.5px solid currentColor; border-radius: 50%;
    font-weight: 700; font-style: italic; font-family: Georgia, serif;
  }
  /* the live frame's bar lies along the strip's lower edge: it measures
     the run the strip counts and takes no line of its own */
  body.phone-job .phone-strip-progress {
    display: block; position: absolute; left: 0; right: 0; bottom: 0; pointer-events: none;
  }
  body.phone-job .phone-strip-progress .progress-track { margin: 0; border-radius: 0; }

  /* -- the frame's grid: the sheet pane on top at the height of the
        shown sheet, the model below, the foot line and the bar -- */
  body.phone-job .stagework {
    display: grid; flex: 1 1 auto; height: auto; min-height: 0;
    padding: 0; gap: 0; border-radius: 0; transition: none;
    grid-template-columns: minmax(0, 1fr);
    grid-template-rows: var(--phone-sheet-h, 38%) minmax(0, 1fr) auto auto;
    grid-template-areas: "sheet" "model" "foot" "bar";
  }
  body.phone-job .stagework > #viewer { grid-area: sheet; }
  body.phone-job .stagework > #viewer-side { grid-area: model; }
  body.phone-job .stagework > #phone-foot { grid-area: foot; }
  body.phone-job .stagework > #phone-bar { grid-area: bar; }

  /* -- the sheet pane: the sheet edge to edge, its caption line under it
        with the part and "Nur Blatt"; pinch, double tap and swipe on it
        (abbundo.js) - so the browser's own gestures stay off it -- */
  body.phone-job .viewer.stage {
    height: auto; min-height: 0; max-height: none; border-radius: 0;
  }
  body.phone-job .viewer.stage .viewer-panel { height: 100%; }
  body.phone-job .viewer.stage .viewer-stage { order: 1; grid-template-columns: minmax(0, 1fr); }
  body.phone-job .viewer.stage .viewer-body { grid-column: 1; padding: 0; touch-action: none; }
  body.phone-job .viewer.stage .viewer-body img { border: 0; border-radius: 0; }
  body.phone-job .viewer.stage .ghost,
  body.phone-job .viewer.stage .part-step,
  body.phone-job .viewer.stage .viewer-zoom-hint,
  body.phone-job .viewer.stage .viewer-zoom-controls { display: none; }
  body.phone-job .viewer.stage .viewer-notes { order: 2; flex: none; font-size: 0.78rem; }
  body.phone-job .viewer.stage .viewer-bar {
    order: 3; flex: none; flex-wrap: nowrap; align-items: center; gap: var(--s2);
    min-height: var(--tap); padding: 0 0 0 var(--s3);
    border-bottom: 0; border-top: 1px solid var(--th-line);
  }
  body.phone-job .viewer.stage .viewer-bar .viewer-slot { display: none; }
  body.phone-job .viewer.stage .viewer-bar #viewer-title {
    flex: 1 1 auto; min-width: 0; font-size: 0.85rem; line-height: 1.25; overflow-wrap: anywhere;
  }
  body.phone-job .pane-corner {
    display: inline-flex; align-items: center; justify-content: center; flex: none;
    width: var(--tap); height: var(--tap); margin: 0 0 0 auto; padding: 0;
    border: 0; background: transparent; color: var(--th-ink); font-size: 1.2rem; cursor: pointer;
  }

  /* -- the model pane: the navigator fills it; before a model exists the
        wait line and the file rows are its content (SCOPE C1) -- */
  body.phone-job .stagework .viewer-side {
    position: relative; inset: auto; z-index: auto; min-height: 0; max-height: none;
    margin: 0; border: 0; border-top: 1px solid var(--th-line); border-radius: 0;
    box-shadow: none; display: flex; flex-direction: column;
  }
  body.phone-job .stagework .viewer-side-body {
    flex: 1 1 auto; min-height: 0; height: auto; padding: 0; gap: 0;
    display: flex; flex-direction: column;
  }
  body.phone-job .viewer-side .cues, body.phone-job #live-note,
  body.phone-job .viewer-side .rail-probe { display: none; }
  body.phone-job .viewer-side-body > .file-picker { padding: var(--s1) var(--s2); }
  body.phone-job .viewer-side-body > .file-picker .file-pick { min-height: var(--tap); }
  body.phone-job .viewer-side-body > .nav-wait { padding: var(--s2) var(--s3); }
  body.phone-job .stagework .viewer-side .assembly-inset {
    flex: 1 1 auto; min-height: 0; max-height: none; margin: 0; border: 0; border-radius: 0;
  }
  body.phone-job .assembly-inset .pane-corner { position: absolute; top: 0; right: 0; z-index: 3; }
  /* the explode control stands in the top left corner and stops short of
     the "Nur Modell" corner control on the right */
  body.phone-job .assembly-inset .explode-control {
    left: var(--s2); right: auto; max-width: calc(100% - var(--tap) - 2 * var(--s2));
  }
  body.phone-job .assembly-inset .explode-range { width: 6rem; }
  body.phone-job .assembly-inset .explode-control { min-height: var(--tap); }
  body.phone-job .assembly-inset .explode-range input[type="range"] { min-height: var(--tap); }
  body.phone-job .assembly-inset .assembly-solo,
  body.phone-job .assembly-inset .assembly-reset { min-width: var(--tap); min-height: var(--tap); }
  body.phone-job .coachmark-close { min-width: var(--tap); min-height: var(--tap); }
  /* before a model exists, the file rows are the model pane's content
     (SCOPE C1) and scroll inside it; once the navigator stands, the list
     waits in the finder */
  .viewer-side-body:where(.phone-job *) > .viewer-tree {
    display: none; flex: 1 1 auto; min-height: 0; max-height: none; overflow: auto;
    overscroll-behavior: contain; padding: 0 var(--s2);
  }
  .viewer-side-body:where(.phone-job *):not(:has(> .assembly-inset:not([hidden]))) > .viewer-tree { display: block; }
  body.phone-job .viewer-tree .file-row > summary { min-height: var(--tap); box-sizing: border-box; }

  /* -- the foot line (zero height when it has nothing to say) and the
        thumb bar: the book's arrows, the position chip, the files
        action, "Mehr" -- */
  body.phone-job .phone-foot {
    display: block; margin: 0; padding: var(--s1) var(--s2);
    font-size: 0.75rem; line-height: 1.35; color: var(--ink-soft);
    background: var(--panel); border-top: 1px solid var(--line);
  }
  body.phone-job .phone-foot:empty { display: none; }
  body.phone-job .phone-bar {
    display: flex; align-items: center; gap: var(--s1); min-height: 3.5rem;
    padding: var(--s1) var(--s1) calc(var(--s1) + var(--safe-foot));
    background: var(--panel); border-top: 1px solid var(--line);
  }
  body.phone-job .phone-bar > button, body.phone-job .phone-bar-files a,
  body.phone-job .phone-bar-files button, body.phone-job .phone-bar-files .download-dock-preparing {
    min-height: var(--tap); margin: 0; font: inherit; font-size: 0.85rem; line-height: 1.2;
  }
  body.phone-job .phone-bar-step {
    flex: none; width: var(--tap); padding: 0; font-size: 1.6rem !important;
    border: 1px solid var(--line); border-radius: var(--radius-sm); background: var(--panel); color: var(--ink);
  }
  body.phone-job .phone-bar-pos {
    flex: 0 1 auto; min-width: var(--tap); padding: 0 var(--s2);
    border: 1px solid var(--line); border-radius: var(--radius-sm); background: var(--panel);
    color: var(--ink); white-space: nowrap;
  }
  body.phone-job .phone-bar-pos[aria-expanded="true"] { border-color: var(--accent); color: var(--accent); }
  body.phone-job .phone-bar-files { display: flex; flex: 1 1 auto; min-width: 0; font-size: 0.8rem; }
  body.phone-job .phone-bar-files a, body.phone-job .phone-bar-files button { font-size: 0.8rem; }
  body.phone-job .phone-bar-files > *, body.phone-job .phone-bar-files form > .button {
    flex: 1 1 auto; min-width: 0;
  }
  body.phone-job .phone-bar-files form { display: flex; margin: 0; }
  body.phone-job .phone-bar-files .help { display: none; }
  /* C.158: signed in, not in the guest job's own browser - the line
     stands where the doors would */
  body.phone-job .phone-bar-files > .dock-attach-elsewhere { display: block; margin: 0; align-self: center; }
  body.phone-job .phone-bar-files .button, body.phone-job .phone-bar-files .download-dock-preparing {
    display: flex; align-items: center; justify-content: center; text-align: center;
    padding: var(--s1) var(--s2); white-space: normal;
  }
  body.phone-job .phone-bar-files > #progress-partial { display: none; }
  body.phone-job .phone-bar-files.offers-partial > #progress-partial:not([hidden]) { display: flex; margin: 0; }
  body.phone-job .phone-bar-files.offers-partial > .download-dock-action { display: none; }
  body.phone-job .phone-bar-more {
    flex: none; position: relative; min-width: var(--tap); padding: 0 var(--s2);
    border: 1px solid var(--line); border-radius: var(--radius-sm); background: var(--panel); color: var(--ink);
  }
  body.phone-job .phone-bar-more .dock-stamp-dot { position: absolute; top: 4px; right: 4px; }

  /* -- the layers: over the model's side of the frame, the sheet pane
        left in view; one at a time; "Schließen" in each foot -- */
  body.phone-job .phone-layer:not([hidden]) { display: flex; }
  body.phone-job .phone-layer {
    position: fixed; z-index: 25; flex-direction: column;
    left: var(--phone-layer-left, 0px); right: 0; bottom: var(--kb);
    box-shadow: var(--shadow-lift);
  }
  body.phone-job .phone-finder {
    top: var(--phone-layer-top, 50%);
    background: var(--th-rail); color: var(--th-soft); border-top: 1px solid var(--th-line-strong);
  }
  body.phone-job .phone-sheetlayer {
    top: auto; max-height: calc(100dvh - var(--phone-layer-top, 50%));
    background: var(--panel); color: var(--ink);
    border-top: 1px solid var(--line-strong); border-radius: var(--radius) var(--radius) 0 0;
  }
  body.phone-job .phone-layer-title {
    flex: none; margin: 0; padding: var(--s3) var(--s3) var(--s2); font-size: 1rem;
  }
  body.phone-job .phone-layer-body {
    flex: 1 1 auto; min-height: 0; overflow: auto; overscroll-behavior: contain;
    padding: 0 var(--s3) var(--s3);
  }
  body.phone-job .phone-layer-body .meta-inline { flex-direction: column; align-items: stretch; gap: var(--s2); }
  /* the job's facts, each as its label over its value: the reference
     with "Kopieren", the deletion day with its pencil and "Jetzt
     löschen", the drawing language with its pencil */
  body.phone-job .phone-layer-body .meta-inline > div,
  body.phone-job .phone-layer-body .meta-inline > div:first-child,
  body.phone-job .phone-layer-body #meta-language { display: grid; gap: var(--s1); }
  body.phone-job .phone-layer-body .meta-inline dt { display: block; font-size: var(--fs-small); color: var(--ink-soft); }
  body.phone-job .phone-layer-body .meta-inline dd {
    display: flex; flex-wrap: wrap; align-items: center; gap: var(--s2); margin: 0;
  }
  body.phone-job .phone-layer-body .meta-inline .copy-button,
  body.phone-job .phone-layer-body .pencil,
  body.phone-job .phone-layer-body .button,
  body.phone-job .phone-layer-body .button-ghost { min-height: var(--tap); min-width: var(--tap); }
  body.phone-job .phone-layer-body .download-dock { padding: 0; margin-top: var(--s3); border: 0; }
  body.phone-job .phone-layer-body .dock-secondary { position: static; }
  /* C.165: in the thumb bar the package's progress keeps its step, its
     share and its bar, one above the other; the estimate stays in the
     dock's layer */
  body.phone-job .phone-bar-files .dock-progress { display: grid; gap: var(--s1); padding: var(--s1) var(--s2); }
  body.phone-job .phone-bar-files .dock-progress-eta { display: none; }
  /* C.186: while the package is made its progress is the thumb bar's
     own first row, the bar's whole width, above the arrows and "Mehr" -
     in view at every scroll position, never squeezed between them */
  body.phone-job .phone-bar:has(.dock-progress) { flex-wrap: wrap; }
  body.phone-job .phone-bar-files:has(> .dock-progress) { order: -1; flex: 1 1 100%; }
  body.phone-job .phone-bar-files .dock-progress [data-dock-step] { font-size: 1rem; line-height: 1.2; }
  /* C.186: the card is the thumb bar's extra row and the glass belongs to
     the panes (P2), so on the phone it is set as tight as its words allow:
     step 16 px, bar 12 px, the share at the step's size, the spinner at
     its floor of 18 px (no taller than the line's 19 px), a thin
     frame and no air around the line */
  body.phone-job .phone-bar-files .download-dock-preparing.dock-progress {
    gap: 2px; padding: 2px var(--s2); border-width: 1px; border-left-width: 4px;
  }
  body.phone-job .phone-bar-files .dock-progress .dock-progress-line { gap: var(--s1); }
  body.phone-job .phone-bar-files .dock-progress .dock-pct { font-size: 1rem; line-height: 1.2; }
  body.phone-job .phone-bar-files .dock-progress .download-dock-spinner { width: 1.125rem; height: 1.125rem; border-width: 2px; }
  body.phone-job .phone-bar-files .dock-progress .dock-progress-track { height: 0.75rem; }
  /* C.165: on the phone the dock's action lives in the thumb bar, so the
     row it leaves behind would hold its "?" alone - an orphan control
     (page design laws 1). The row goes with its action. */
  body.phone-job .phone-layer-body .dock-action-row:not(:has(.download-dock-action, .download-dock-preparing, .dock-continue)) { display: none; }
  body.phone-job .phone-layer-body .jobnotices { padding: 0; margin: var(--s3) 0 0; }
  body.phone-job .phone-rows { display: flex; flex-direction: column; overflow: auto; }
  body.phone-job .phone-row { display: block; border-top: 1px solid var(--line); }
  body.phone-job .phone-row:empty, body.phone-job .phone-row[data-shown="false"] { display: none; }
  body.phone-job .phone-row > a, body.phone-job .phone-row > button {
    display: flex; align-items: center; justify-content: flex-start; gap: var(--s2); width: 100%; min-height: 3.5rem; margin: 0;
    padding: 0 var(--s3); border: 0; border-radius: 0; background: transparent; box-shadow: none;
    color: var(--ink); font: inherit; font-size: 0.95rem; text-align: left; text-decoration: none;
    white-space: normal; animation: none;
  }
  body.phone-job .phone-layer-foot {
    flex: none; display: flex; align-items: center; gap: var(--s2);
    padding: var(--s2) var(--s3) calc(var(--s2) + var(--safe-foot));
    border-top: 1px solid var(--line);
  }
  body.phone-job .phone-layer-foot > .button-ghost { flex: 1 1 auto; min-height: var(--tap); margin: 0; }
  body.phone-job .phone-finder .phone-layer-foot { border-top-color: var(--th-line); }
  body.phone-job .phone-finder .phone-layer-foot > .button-ghost { flex: none; padding: 0 var(--s3); color: var(--th-ink); }
  /* C.58j (owner 28.09.2026): with the screen keyboard up, the finder
     keeps its chips, a few rows and its search line inside what stays
     visible above the keyboard (kit/keyboard.js, the one keyboard resource, reads the visual viewport) */
  :root[data-kb] body.phone-job .phone-finder {
    top: max(var(--vv-top),
             min(var(--phone-layer-top, 50%), calc(100% - var(--kb) - 14rem)));
  }
  body.phone-job .finder-search { flex: 1 1 auto; min-width: 0; }
  body.phone-job .phone-finder .kit-search-empty { flex: none; padding: var(--s2) var(--s3); }
  /* the kit's search field on the dark rail: the field box keeps the
     tap size and a size that no phone zooms on */
  body.phone-job .finder-search input {
    width: 100%; min-height: var(--tap); margin: 0; font-size: 1rem;
  }
  /* the rail is dark in both schemes: the count and the field's edge
     take the stage's light readings of the two search colours, so they
     stand out against the rail as they do against a light page */
  body.phone-job .phone-finder {
    --search-none: var(--stage-search-none);
    --search-none-soft: var(--stage-search-none-soft);
    --search-active: var(--stage-search-active);
    --search-active-soft: var(--stage-search-active-soft);
    --search-ink: var(--stage-ink);
    --field-line: var(--stage-field-line);
  }
  body.phone-job .finder-search .kit-search-count { color: var(--th-soft); }
  body.phone-job .finder-search .kit-search[data-search-state="none"] .kit-search-count { color: var(--search-none); }
  body.phone-job .finder-search .kit-search[data-search-state="active"] .kit-search-count { color: var(--search-active); }
  /* the finder's field is the stage's: dark, with the stage's ink */
  body.phone-job .finder-search .kit-search[data-search-state="neutral"] .kit-search-field input {
    background: var(--stage-field); color: var(--stage-ink);
  }
  body.phone-job .finder-chips {
    flex: none; display: flex; flex-wrap: wrap; gap: var(--s1); padding: var(--s2) var(--s2) var(--s1);
  }
  body.phone-job .finder-chip {
    min-height: var(--tap); margin: 0; padding: 0 var(--s3); border-radius: 999px;
    border: 1px solid var(--th-line-strong); background: transparent; color: var(--th-soft);
    font: inherit; font-size: 0.85rem; cursor: pointer;
  }
  /* C.58j with the C.104 scope (section 5): a pressed chip other than
     "Alle" is a filtered view and wears the search field's active look;
     "Alle" pressed is the whole list and stays neutral */
  body.phone-job .finder-chip[aria-pressed="true"]:not([data-chip="all"]) {
    background: var(--search-active-soft); color: var(--stage-ink);
    border-color: var(--search-active); box-shadow: inset 0 0 0 1px var(--search-active);
  }
  body.phone-job .finder-list { flex: 1 1 auto; min-height: 0; overflow: auto; overscroll-behavior: contain; padding: 0 var(--s2); }
  body.phone-job .finder-list .viewer-tree { display: block; max-height: none; min-height: 0; overflow: visible; }
  body.phone-job .finder-list .partlist li { min-height: 3rem; }
  body.phone-job .finder-list .partrow-button,
  body.phone-job .finder-list .mark, body.phone-job .finder-list .file-name { min-height: var(--tap); }
  body.phone-job .finder-list .mark { min-width: var(--tap); }
  /* the download icon keeps its drawn circle and grows its hit box to the
     tap size around it: the fill is clipped to the circle, the ring is an
     outline drawn on the circle's edge, the diagonal spans the circle */
  body.phone-job .finder-list .dl-toggle {
    width: var(--tap); height: var(--tap); padding: calc((var(--tap) - 1.55rem) / 2);
    border-width: 0; background-clip: content-box;
    outline: 1px solid var(--th-line-strong); outline-offset: calc((1.55rem - var(--tap)) / 2 - 1px);
  }
  body.phone-job .finder-list .dl-toggle:not(.is-on)::after {
    left: calc((var(--tap) - 1.55rem) / 2); right: calc((var(--tap) - 1.55rem) / 2);
  }
  body.phone-job .finder-list li.finder-out { display: none; }

  /* -- the full views: "Nur Blatt" over the whole glass, "Nur Modell"
        with the sheet pane shrunk to its strip -- */
  body.phone-job.phone-sheet-only .stagework > #viewer {
    position: fixed; inset: 0; z-index: 40; height: auto;
  }
  body.phone-job.phone-sheet-only .viewer.stage .viewer-bar { order: 0; border-top: 0; border-bottom: 1px solid var(--th-line); }
  body.phone-job.phone-model-only .stagework { grid-template-rows: 4.5rem minmax(0, 1fr) auto auto; }
  body.phone-job.phone-model-only .viewer.stage .viewer-stage { display: none; }
  body.phone-job.phone-model-only .viewer.stage .viewer-bar { flex: 1 1 auto; cursor: pointer; }
}
/* the phone on its side: the sheet pane at the band's full height on the
   left, the model with the foot line and the bar on the right */
@media (max-width: 60rem) and (orientation: landscape) {
  /* on its side the sheet pane takes the glass's whole height on the
     left; the right column carries the strip on top, the model, the foot
     line and the bar. The strip is laid over the column's first row,
     whose height jobphone.js measures off the strip (--phone-strip-h). */
  body.phone-job > main { position: relative; }
  body.phone-job .jobtop {
    position: absolute; top: 0; right: 0; width: max(16rem, 42%);
    border-left: 1px solid var(--line);
  }
  body.phone-job.phone-model-only .jobtop { width: calc(100% - 6rem); }
  body.phone-job .stagework {
    grid-template-columns: minmax(0, 1fr) max(16rem, 42%);
    grid-template-rows: var(--phone-strip-h, 45px) minmax(0, 1fr) auto auto;
    grid-template-areas: "sheet strip" "sheet model" "sheet foot" "sheet bar";
  }
  body.phone-job.phone-model-only .stagework {
    grid-template-columns: 6rem minmax(0, 1fr);
  }
  body.phone-job .stagework .viewer-side { border-top: 0; border-left: 1px solid var(--th-line); }
  /* on its side the glass is short: the bar hugs its tap-size controls
     and the foot line is set small, so the model keeps its share */
  body.phone-job .phone-bar { min-height: 0; padding-block: 2px calc(2px + var(--safe-foot)); }
  body.phone-job .phone-foot { padding-block: 2px; font-size: 0.7rem; line-height: 1.3; }
}
/* a short window folds the site header into the strip's menu button; the
   button stands the header over the frame, with its own menus, and the
   phone's back or Escape folds it again */
@media (max-width: 60rem) and (max-height: 31.25rem) {
  body.phone-job > .site-header { display: none; }
  body.phone-job[data-phone-layer="header"] > .site-header {
    display: block; position: fixed; top: 0; left: 0; right: 0; z-index: 35; box-shadow: var(--shadow-lift);
  }
  body.phone-job .phone-menu { display: inline-flex; }
}
/* with the plate card open the 3D view needs every pixel above it: the site
   header folds into the strip's menu button exactly as on a short window */
@media (max-width: 60rem) and (orientation: portrait) {
  body.phone-job.kind-sheet-open > .site-header { display: none; }
  body.phone-job.kind-sheet-open[data-phone-layer="header"] > .site-header {
    display: block; position: fixed; top: 0; left: 0; right: 0; z-index: 35; box-shadow: var(--shadow-lift);
  }
  body.phone-job.kind-sheet-open .phone-menu { display: inline-flex; }
}
/* PAGE DESIGN LAW P16 (C.96, global): at phone width every popup opens as
   a sheet from the foot, at most 90 % of the glass high, its foot and
   "Schließen" at the bottom in the thumb's reach, and every control in it
   at least the tap size each way. The sheet itself is the kit popup's
   phone mode (kit/kit.css, "PHONE MODE" and "THE PHONE FRAME"); since
   C.58j the job page's five popups are the kit's too, and this block
   holds only what the job page's own forms add inside them: the action
   row that stays in view at the popup's foot, and the settings foot's
   three actions side by side. */
/* the settings foot's three actions stay in view at the popup's foot at
   EVERY width (C.117, manager 30.09.2026: at 1440 x 900 the job page's
   settings popup drew "Neu zeichnen" 1 000 px below the window), as every
   kit form's action row does (kit/kit.css, "THE FORM'S ACTION ROW STAYS
   AT THE FOOT"): a sticky row holds only inside its parent, so the boxes
   between it and the fragment give way (display: contents) and the row
   sticks for the whole length of the popup; the foot's notes and its
   questions follow in the flow below it. */
.kit-pop-fragment .kit-formpage-after,
.kit-pop-fragment .settings-foot { display: contents; }
.kit-pop-fragment .settings-foot-actions {
  position: sticky; bottom: 0; z-index: 2; margin: 0;
  padding-block: var(--s2); background: var(--panel); border-top: 1px solid var(--line);
}
/* C.160: a tab's own action moved into the foot (popup.js toFoot, "Als
   Standard speichern") stands as a fourth column beside the three, each
   a quarter of the row, so the foot stays one band: as a fourth flex
   item it wrapped the foot onto two rows and took the Plankopf field
   box's room (two whole fields at 1440 x 900, not four). Asked without
   :has(): toFoot puts a moved action FIRST in the foot, so a shown one
   reaches the three after it as their sibling, and four items that each
   start from nothing (flex 1 1 0) share the row in quarters and never
   wrap */
.kit-pop-fragment .settings-foot-actions > .kit-pop-foot-part {
  flex-direction: column; align-items: flex-start; gap: var(--s2); min-width: 0;
}
.kit-pop-fragment .settings-foot-actions > .kit-pop-foot-part:not([hidden]),
.kit-pop-fragment .settings-foot-actions > .kit-pop-foot-part:not([hidden]) ~ .settings-foot-action {
  flex: 1 1 0; max-width: none; min-width: 0;
}
@media (max-width: 60rem) {
  /* a question that opens (an FAQ row, the package's contents) and a
     link that stands alone on its line are controls too */
  body.phone-job .kit-pop summary { min-height: var(--tap); padding-block: var(--s2); box-sizing: border-box; }
  body.phone-job .kit-pop p > a:only-child, body.phone-job .kit-pop .settings-value > a {
    display: inline-flex; align-items: center; min-height: var(--tap);
  }
  /* the settings foot (C.46/C.86) on a phone: its three actions side by
     side, each with its reason under it, so the foot stays one short
     band at the popup's foot and the form above keeps the room */
  /* C.160: with a tab's own action moved into the foot the band holds
     four, side by side, and that action's button is drawn as the three
     are, so the band stays one row within the thumb's reach (P16): the
     grid flows along its one row, and a fourth shown item opens a fourth
     column as wide as the three (a hidden one takes no column) */
  body.phone-job .kit-pop-fragment .settings-foot-actions {
    display: grid; grid-template-columns: repeat(3, minmax(0, 1fr));
    grid-auto-flow: column; grid-auto-columns: minmax(0, 1fr);
    gap: var(--s1); align-items: start;
  }
  body.phone-job .kit-pop-fragment .settings-foot-action { min-width: 0; max-width: none; gap: var(--s1); }
  body.phone-job .kit-pop-fragment .settings-foot-actions > .kit-pop-foot-part { gap: var(--s1); }
  body.phone-job .kit-pop-fragment .settings-foot-actions > .kit-pop-foot-part .button {
    width: 100%; margin: 0; padding: var(--s1); font-size: var(--fs-small); white-space: normal;
  }
  body.phone-job .kit-pop-fragment .settings-foot-action > .button {
    width: 100%; margin: 0; padding: var(--s1); font-size: var(--fs-small); white-space: normal;
  }
  body.phone-job .kit-pop-fragment .settings-foot-reason,
  body.phone-job .kit-pop-fragment .settings-foot-note { font-size: 0.75rem; }
}

/* JOB PAGE 9, owner review 28.10.2026 */
/* a phone's stop strip button at the tap size (P5) */
body.phone-job .stage-check .stage-check-go { min-height: var(--tap); min-width: var(--tap); }
/* a row whose sheet is being drawn again says that one word, without the
   drawn tick beside it */
.viewer-tree li[data-redrawing="true"][data-paint="done"] .pill::before,
.stagework .viewer-tree li[data-redrawing="true"][data-paint="done"] .pill::before { content: none; display: none; }
/* the parts list keeps room for about six rows on a short desk window:
   the model's rest height gives way first */
@media (min-width: 60.0625rem) and (max-height: 860px) {
  .stagework .viewer-side .assembly-inset { flex-basis: 200px; }
  /* a hovered list keeps the 3D view at the height it really had at rest
     (job.js measures it as the rail opens, --inset-rest-h) */
  .stagework .viewer-side.is-list .assembly-inset { flex-basis: var(--inset-rest-h, 200px); }
}

/* b39h-f7: the answer to a guest who selects a held part. A held part has
   no sheet, so the line lies over the stage's empty place under the part's
   word and moves nothing (L-PAGES-17); its door is the stage strip's size. */
.viewer.stage .draw-next-account {
  position: absolute; inset-inline: var(--s6); top: calc(50% + 4.25rem); z-index: 3;
  align-items: center; padding: 0; text-align: center;
}
.viewer.stage .draw-next-account .reprint-note { color: var(--th-soft); }
.viewer.stage .draw-next-account form { margin: 0; }
.viewer.stage .draw-next-account .button-ghost {
  min-height: 1.8rem; margin: 0; padding: 0 var(--s3); font-size: 0.85rem;
  background: var(--stage-button-bg); color: var(--th-ink);
  border-color: var(--th-line-strong);
}
.viewer.stage .draw-next-account .button-ghost:hover { background: var(--stage-button-hover); filter: none; }
/* a phone folds the sheet pane while the part card stands, and the finder
   covers the lower half: the line stands over the top of the view, above
   the layers, and its door at the tap size */
body.phone-job .viewer.stage .draw-next-account {
  position: fixed; inset-inline: var(--s2); top: 7rem; z-index: 26;
  visibility: visible; align-items: stretch; padding: var(--s2) var(--s3);
  text-align: left; background: var(--th-bg);
  border: 1px solid var(--th-line-strong); border-radius: var(--radius);
}
body.phone-job .viewer.stage .draw-next-account .button-ghost { width: 100%; min-height: var(--tap); }
