/* ════════════════════════════════════════════════════════════════════
   app.css — the Razor port's own shim layer, and the last sheet in this application that is not
   the design system.

   There is one stylesheet of record now: wwwroot/css/JpscTheme.css, the Office Measures design the port was
   rebuilt onto. It is linked last in the document head (App.razor) — after this file and after Ask.css — so
   on every property it declares for a class it wins the tie. That is what makes the lines left here safe to
   keep: none of them competes with the theme. Each either names a class the theme does not write at all, or
   supplies the one property a theme box deliberately leaves unset.

   What that test leaves is small, and all of it is the port's own need rather than a second taste:

     · the chrome a circuit requires and a postback never did — the focus handoff on navigation, the way a
       refusal's two lines sit against its close control, the stop card's measure and centring;
     · the two register extras with no theme word — a row that opens the slide-over from itself, and a cell
       sub-line that must not wrap a timestamp in half;
     · the slide-over's two header lines, the self-service password panel, the pattern lock's geometry, the
       archive's purge stage, and the printable report's foot;
     · one property the theme's own boxes leave unset: the padding behind a `.panel` that carries content
       instead of `.panel-h` / `.panel-b`.

   Everything else this file carried is gone, and the going was measured rather than judged. A rule was cut
   when either no markup renders its class — a second spelling the page stopped writing when the theme
   conversion renamed it — or the theme already declares every property it sets, in which case it could never
   have painted. The KPI card and its pressed state, the scope band, the module badge and its ten hues, the
   boot splash, the ghost button, the callout pair, the field label and the input box, the slide-over overlay,
   the trail's detail block and the whole table/toolbar/chip/pager imitation are the theme's now, and the
   pristine WebForms sheets that used to sit between them and this file are deleted from wwwroot: the vendored
   stack is in the legacy project as the reference, and nothing here restates it.

   Bootstrap left the shell with them. What it still supplied underneath — the reboot's `box-sizing`, the
   body's 1.5 line, the form controls' inherited type, the heading and paragraph margins, the dialog frame's
   geometry and the button's whole hover/active/disabled state machine — is written into the theme's own
   sections, and the vendored sheet now loads on the login page alone.

   All of it reads the theme's tokens — --ink, --ink-2, --muted, --line, --card, --bg, --gold, --gold-dark,
   --gold-soft, --gold-glow, --red, --input-bg, --radius-sm…xl, --shadow-sm…lg, --transition — every one of
   them declared in JpscTheme.css's `:root`, so a theme change stays a one-file edit.
   ════════════════════════════════════════════════════════════════════ */

/* ── Focus handoff (Routes.razor's FocusOnNavigate) ───────────────────
   After a client-side navigation Blazor moves focus to the page's h1 so a screen reader announces the page
   that arrived instead of leaving the caret on the sidebar link just activated. The move is kept; the ring is
   not. Chrome paints its default focus outline around any tabindex="-1" element it lands on, and the theme
   never drew one because nothing in the legacy application ever moved focus — so on every shell page that
   ring was the port adding a box the design has no class for. Silencing only the outline is safe here: a
   tabindex="-1" heading is never reached by Tab, so the ring was never a keyboard cue to begin with, while
   every real control keeps its own. */
h1[tabindex="-1"]:focus,
h1[tabindex="-1"]:focus-visible {
    outline: none;
}

/* ── The row that opens the panel ───────────────────────────────────────
   The archive's and the log's rows open the slide-over from the row itself, where the .aspx offered only its
   View button. The hover tint already arrives from the theme's `.tbl tbody tr:hover`; the cursor is the part
   a table row never inherits, because a row is not a control until this port made it one. */
tr.clickable { cursor: pointer; }

/* ── The two extras no theme cell supplies ──────────────────────────────
   A sub-line under a cell's main value: the theme sizes and colours it (`.cell-sub`) but lays it inline, and
   the second reading has to sit under the first — and it must not wrap, because the ledger's sub-line is a
   relative date ("3 days ago") that reads as one fact or not at all. */
.cell-sub { display: block; white-space: nowrap; }

/* A value read character by character — a timestamp, an IP, a record key, a raw column's own text. The theme
   gives `.mono` the face; the size and the letter-spacing are what a register's meta line needs and does not
   carry, so both reads (the slide-over's values and the ledger's keys) take this one rule rather than each
   page inventing a second spelling of the same thing. */
.mono { font-size: .78rem; letter-spacing: .2px; }

/* ── The plain card that holds content rather than a header and a body ──
   The theme's `.panel` is a frame for `.panel-h` and `.panel-b`, and it is those two that carry the padding —
   which is right for the dashboard's seven panels and wrong for the one page that has no header to give a
   rule to and no body to pad: the self-service password change. So the room is claimed here, on that page's
   own class, and not on `.panel`, where it would have inset every panel header's divider by 18px.
   `.panel-note` is the small grey line beside a control; the theme has `.ps` inside a header and nothing for
   a note under one. */
.pw-panel { max-width: 640px; padding: 16px 18px 18px; }
.panel-note { font-size: .72rem; color: var(--muted); }

/* ── The slide-over's two header lines ────────────────────────────────
   The panel itself is section 14 of the theme (`sp-overlay`, `sp`, `sp-head`, `sp-body`, `sp-foot`) and the
   SlideOver component writes those names, so nothing about the drawer's geometry lives here any more. What is
   left is the pair of lines under the title: the theme sets `.sp-title` as a block with `min-width: 0`, and
   the heading needs the meta run beside it rather than under it; and `.sp-meta` is given colour and size but
   no arrangement, because the old drawer stacked its three items while this one lets them run. Each meta
   item is a number, a role or an employer, and a wrap between "Property #" and its digits reads as two
   separate facts, so the pairs are kept whole. */
.sp-title { display: flex; align-items: center; gap: 12px; }
/* The theme's heading is a title and not a paragraph: with no margin of its own reset, an h2's browser
   default would push the meta line away from the pills beside it. */
.sp-title h2 { margin: 0; }
.sp-meta { display: flex; flex-wrap: wrap; gap: 4px 12px; }
.sp-meta span { white-space: nowrap; }

/* ── The self-service password change ─────────────────────────────────
   Three boxes and a checklist, so the page takes a reading width rather than the grid width a register page
   earns. The rule list is the password policy's own Rules array rather than a sentence typed under the box,
   because a person who has to satisfy six conditions reads them one at a time. */
.pw-actions { display: flex; align-items: center; gap: 14px; margin-top: 16px; flex-wrap: wrap; }
.pw-rules {
    margin: 2px 0 8px; padding: 11px 13px;
    border: 1px solid var(--line); border-radius: var(--radius-sm);
    background: var(--input-bg);
}
.pw-rules-title {
    display: block; margin-bottom: 7px;
    font-size: .7rem; font-weight: 700; letter-spacing: .04em; text-transform: uppercase;
    color: var(--muted);
}
.pw-rules ul { list-style: none; margin: 0; padding: 0; display: grid; gap: 5px 16px;
    grid-template-columns: repeat(auto-fit, minmax(215px, 1fr)); }
.pw-rules li { position: relative; padding-left: 15px; font-size: .78rem; color: var(--ink-2); }
.pw-rules li::before { content: '\2022'; position: absolute; left: 4px; color: var(--gold); }

/* ── The corner notice, and the card that stops a page ────────────────
   The notice is the theme's (`.notice`, with its `-ok` / `-bad` tones) and so is its close control: section
   15 draws `.btn-close` as a 30px white box with an `Ico` inside it and gives it `margin-left:auto`, and the
   port's markup writes nothing else. The stop card's plate, border, radius, padding and shadow are the
   theme's too. What neither can supply is the two things that come from this application rather than from
   its design: how a refusal's two lines sit against a control built for one, and the fact that a card which
   stops a page has to stop it in the middle of the screen rather than at the top of a column.

   align-items stays at the top so a two-line refusal does not float its ✕ in the middle of the sentence —
   the theme's `.notice` centres its children, which is right for the one-line save and wrong for the wrapped
   refusal — and the message takes the room the button does not, so a long record key wraps inside the line
   instead of outrunning it. */
.notice-closable { align-items: flex-start; }
.notice-closable span { flex: 1 1 auto; }

.stop-card { max-width: 480px; margin: 14vh auto; text-align: center; }
.stop-card h1 { margin: 0 0 10px; }
.stop-card .btn { margin: 0 4px; }

/* ── The heading that opens a stored-credentials group ────────────────
   `/account-credentials` renders the theme's `.cred-group` for each provider block, and the theme's heading
   is the type: 11px, 800, uppercase, the muted blue-grey, flexed against its icon. The one thing it is not is
   a rule under itself, which is what the ledger needs between a heading and a list of boxes that all read the
   same. So the port adds the hairline and the 6px above it, and nothing else. */
.cred-group h3 { padding-bottom: 6px; border-bottom: 1px solid var(--line); }
.cred-group h3 i { color: var(--gold); font-size: .92rem; }

/* ── Pattern lock ────────────────────────────────────────────────────
   Ported from the legacy account register with one change of shape: a dot is clicked, not dragged, so the
   control works on a trackpad and a touch screen. The theme draws the lock's colours (its section 19 owns
   `.pl-dot-ring`, `.pl-dot-core`, the active pair, the stroke and the readout plate); what is here is the
   geometry it has no word for, because the legacy control positions its dots from a viewBox rather than from
   a grid track.

   A dot is 168px box, three cells of 56, each dot at its centre, and the sizes are custom properties so the
   same markup renders the dialog's lock and the register's thumbnail from one set of rules. The rules that
   name a state are anchored on `.pl-grid` where the theme's own state rules are: the theme writes
   `.pl-grid .pl-dot-active .pl-dot-core` at three classes and it loads after this file, so a two-class
   selector here is a tie it loses — which is why `.pl-mini` and the active core are stated against the grid
   rather than left to inheritance.

   The scale is turned off on the active dot rather than inherited. The legacy lock grew its plain 7px idle
   dot into the active one with a `transform: scale()`, because that was the only way it could animate a dot
   it had no separate size for; here the dot has the two sizes it needs (--pl-idle at rest, --pl-on once
   chosen), so a scale on top of them measures a 28px disc over a 25px ring. */
.pl-grid {
    --pl-box: 168px; --pl-dot: 24px; --pl-idle: 8px; --pl-on: 20px; --pl-num: .62rem;
    position: relative;
    width: var(--pl-box); height: var(--pl-box);
    margin: 0 auto; flex-shrink: 0;
    user-select: none;
    background: linear-gradient(135deg, #FFFFFF 0%, #F8FAFC 100%);
    border: 1px solid var(--line); border-radius: 16px;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .6), 0 2px 8px rgba(15, 23, 42, .05);
    transition: box-shadow var(--transition), border-color var(--transition);
}
.pl-grid.pl-drawing {
    border-color: rgba(234, 166, 15, .35);
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .6), 0 0 0 3px var(--gold-glow), 0 6px 16px rgba(234, 166, 15, .10);
}
.pl-lines { position: absolute; inset: 0; width: 100%; height: 100%; pointer-events: none; }
/* Strokes are in the viewBox's 168 units, so one width serves both sizes. */
.pl-dot-wrap {
    position: absolute;
    width: var(--pl-dot); height: var(--pl-dot);
    margin: calc(var(--pl-dot) / -2) 0 0 calc(var(--pl-dot) / -2);
    display: grid; place-items: center; padding: 0;
    background: transparent; border: 0; cursor: pointer;
}
.pl-dot-wrap:disabled { cursor: default; }
.pl-dot-ring {
    position: absolute; inset: 0;
    border-radius: 50%;
    transition: border-color var(--transition), box-shadow var(--transition), transform var(--transition);
}
/* The centre is the dot's state: a small point at rest, a disc carrying its place in the sequence once
   drawn — which is what the legacy lock could only show as a line. The two colours are the theme's. */
.pl-dot-core {
    position: relative;
    display: grid; place-items: center;
    width: var(--pl-idle); height: var(--pl-idle);
    font-size: var(--pl-num); font-weight: 700; line-height: 1; color: transparent;
    border-radius: 50%;
    transition: width var(--transition), height var(--transition), background var(--transition), color var(--transition);
}
.pl-dot-active .pl-dot-ring { box-shadow: 0 0 0 4px var(--gold-glow); transform: scale(1.05); }
.pl-grid .pl-dot-active .pl-dot-core { width: var(--pl-on); height: var(--pl-on); color: #fff; transform: none; }
/* The read-only form is a picture, not a control the eye can press: the dots are `disabled` for the
   accessibility tree, and this takes the pointer off them as well so a thumbnail never shows a hover or a
   tooltip for a pattern nobody is about to draw. */
.pl-readonly { pointer-events: none; }
/* The register's thumbnail: the same nine dots and the same lines in a little over a third of the room,
   read-only, so a recorder's cell shows its pattern without deciding how tall the row is. The theme owns
   `.pl-mini` as a grid of 32px dots — a layout this control does not use, because its dots are placed from
   the box rather than from a track — but a two-class `.pl-mini .pl-dot-wrap` still reaches the size, so every
   dimension the thumbnail changes is restated at three classes and lands back on the custom properties, which
   is the only weight that wins it. Without those restatements the thumbnail measured a full 168px box. */
.pl-mini { --pl-box: 64px; --pl-dot: 15px; --pl-idle: 5px; --pl-on: 13px; --pl-num: 0px; }
.pl-grid.pl-mini { width: var(--pl-box); height: var(--pl-box); border-radius: 10px; }
.pl-grid.pl-mini .pl-dot-wrap { width: var(--pl-dot); height: var(--pl-dot);
    margin: calc(var(--pl-dot) / -2) 0 0 calc(var(--pl-dot) / -2); }
.pl-grid.pl-mini .pl-dot-ring { width: var(--pl-dot); height: var(--pl-dot); border-width: 1px; }
.pl-grid.pl-mini .pl-dot-core { width: var(--pl-idle); height: var(--pl-idle); }
.pl-grid.pl-mini .pl-dot-active .pl-dot-core { width: var(--pl-on); height: var(--pl-on); }
.pl-foot {
    display: flex; align-items: center; justify-content: space-between; gap: 10px;
    margin-top: 8px; font-size: .72rem; color: var(--muted);
}
/* The foot's sentence is the longest thing in it ("6 dots — release to save" at the widest, a hint at the
   narrowest) and the Clear button must never be pushed out of the 168px box, so the readout takes the room
   that is left and wraps into it. */
.pl-readout { flex: 1 1 auto; min-width: 0; }

/* ── The archive's purge stage ────────────────────────────────────────
   The bar itself is the theme's: `.bulk-bar` and its `.bulk-btn`s, gaining `show` when a row is ticked, and
   the row's tick box is the register's own checkbox class. Only the deletion stage needs a layer of this
   file's own, because the legacy screen asked for the word PURGE inside a dialog: a box no sheet in the
   register ever styled, and one that vanished the moment the word was typed correctly. The theme states its
   two warning lines and its label; what it leaves is the column they stand in, the icons' optical alignment,
   and the rule that separates the sentence from the box. A permanent delete has no undo, so its warnings are
   given more weight and more room than the bar they sit in. */
.arch-purge {
    display: flex; flex-direction: column; gap: 7px;
    flex: 1 1 460px; min-width: 0;
}
.arch-purge-warn i, .arch-purge-note i { margin-top: 1px; }

.arch-purge-type {
    display: flex; align-items: flex-end; gap: 10px; flex-wrap: wrap;
    padding-top: 8px; border-top: 1px solid var(--line);
}
/* The theme's label pairs its text with the N/A checkbox on one line; this one stacks the word over the box,
   because a typed confirmation reads as a field and not as a sentence with a control at the end of it. */
.arch-purge-type label { flex-direction: column; }
.arch-purge-type span { font-size: .74rem; font-weight: 600; color: var(--ink-2); }
.arch-purge-type .inp { width: 170px; text-transform: uppercase; }

/* The reasons a selection did not move, per record, kept on the screen after the notice goes. The theme
   styles the list's type; the pair of stacked lines needs the flex row that keeps its icon off the wrap. */
.arch-blocked { display: flex; align-items: flex-start; gap: 8px; }
.arch-blocked strong { display: block; margin-bottom: 2px; }
.arch-blocked ul { margin: 0; padding-left: 18px; font-size: .78rem; }
.arch-blocked li { margin-top: 2px; }

/* ── The printable report's foot ──────────────────────────────────────
   /audit-report has no .aspx twin — the legacy application wrote every row of HistoryLogs and then offered
   no page that printed any of them — so the sheet is the theme's own document vocabulary (`report-sheet`,
   `rs-*`) and the filter bar is its own (`audit-filter-bar`, `af-*`). One line is left to this file: the
   note under the signature block, which the page composes in prose and the theme has no class for.

   It is the last place the page stops looking like the application around it, and that is the point rather
   than an oversight: it is a thing that gets printed, signed and filed. The printed copy in `shell.js`'s
   `reportStyles` hard-codes the two colours the document is drawn in, because a print frame inherits none of
   the shell's variables; the two have to be changed together, and the day one of them drifts the report will
   look right on screen and wrong on paper. */
.ar-foot {
    margin-top: 22px; padding-top: 8px;
    border-top: 1px solid var(--line);
    font-size: .7rem; text-align: center; color: var(--muted);
}
