/* public/css/policy.css -- the privacy policy's two pages
   (docs/ARBETSORDER_AUTH.md commit D5, Beslut 0.T).

   WHY A FILE OF ITS OWN, AND UNDER WHICH RULE
   docs/ui-guidelines.md avsnitt 19, as revised 2026-08-21: a new CSS file is
   allowed when a coherent PAGE EXPERIENCE is built, not for a single
   component. public/integritet.html and public/privacy.html are two whole new
   pages, and public/css/konto.css is the precedent this file copies. The
   rule's four conditions:

     1. EXISTING PREFIX, NEW SUB-NAMESPACE. Every class below begins with
        es-love-policy-, inside the es-love- family. No fifth design system.
     2. LOADED LAST, AND ONLY BY THE PAGES IT GOVERNS. integritet.html and
        privacy.html are the only files that link it -- verify with
        `grep -l policy.css public/*.html`.
     3. IT REDEFINES NOTHING ANOTHER PAGE USES. Not one selector below names
        an existing class. The element selectors that do appear are all
        DESCENDANTS of es-love-policy-prose, so they cannot reach a page that
        does not load this file.
     4. NO BARE ELEMENT SELECTORS. Every rule is class-scoped.

   THE ONE THING THIS FILE ADDS THAT THE DESIGN SYSTEM DOES NOT HAVE:
   RUNNING PROSE. .es-love-note-body sets margin: 0, because every card in the
   product until now held exactly one paragraph. A legal document is dozens of
   paragraphs and lists, and they need to be separated from each other. That is
   the whole reason for es-love-policy-prose; everything else here is a heading
   size.

   NO NEW TOKEN AND NO NEW HEX VALUE. Everything reads --love-* from
   design-system-love.css, which both pages load, and every number comes from
   the ranges docs/ui-guidelines.md avsnitt 3 and 5 already record. */

.es-love-policy-title {
    margin: 0 0 6px;
    font-size: 26px;
    line-height: 1.2;
    letter-spacing: -0.015em;
    font-weight: 700;
    color: var(--love-ink);
}

/* The link to the other language version. It is NOT the header's language
   switcher: the switcher changes the chrome's language for this session, and
   these two pages are separate documents whose body text is fixed in the file
   (Beslut 0.T). Only a navigation gets you from one to the other. */
.es-love-policy-langlink {
    display: block;
    margin: 0 0 18px;
    font-size: 14px;
}

/* THERE IS NO CLASS FOR THE SECTIONS THEMSELVES. One section is one plain
   .es-love-card inside .es-love-content, whose 24px grid gap is the design
   system's own step between sections on result.html. konto.css declares its own
   14px because the account page does not use that wrapper; these pages do, so a
   second margin here would have stacked on top of the gap. */

.es-love-policy-block-title {
    margin: 0 0 12px;
    font-size: 17px;
    line-height: 1.3;
    font-weight: 700;
    color: var(--love-ink);
}

.es-love-policy-sub {
    margin: 20px 0 8px;
    font-size: 15px;
    font-weight: 700;
    color: var(--love-ink);
}

.es-love-policy-sub:first-child {
    margin-top: 0;
}

/* The prose block. The three values are .es-love-note-body's own -- muted,
   15px, 1.7 -- so a paragraph here reads exactly like a paragraph anywhere
   else in the es-love family. What is added is the spacing between them. */
.es-love-policy-prose {
    color: var(--love-muted);
    font-size: 15px;
    line-height: 1.7;
}

.es-love-policy-prose p,
.es-love-policy-prose ul {
    margin: 0 0 12px;
}

.es-love-policy-prose p:last-child,
.es-love-policy-prose ul:last-child {
    margin-bottom: 0;
}

.es-love-policy-prose ul {
    padding-left: 20px;
}

.es-love-policy-prose li {
    margin-bottom: 8px;
}

.es-love-policy-prose li:last-child {
    margin-bottom: 0;
}

/* Emphasis inside prose steps up to the ink colour rather than getting a
   heavier weight alone -- muted bold on a muted paragraph is hard to see. */
.es-love-policy-prose strong {
    color: var(--love-ink);
    font-weight: 700;
}