/* =============================================================================
   Standalone pages — /news, /projects, /about, /contact and the detail pages.

   Loaded AFTER site.css and depends on it: the palette tokens, .display,
   .lede, .micro, .btn, .card and .news all come from there, so these pages
   inherit a change to the type scale or the palette without restating it.

   THE PAGES ARE THEMED, NOT DARK. Everything below paints with var(--void),
   var(--mist) and friends rather than literal colours, so the light theme
   reaches them through the same :root[data-theme="light"] block that themes
   the homepage. That is the whole reason assets/js/theme.js exists as a
   separate file — see its header.

   Every class here is prefixed pg- or scoped under .pg. site.css is one flat
   unscoped file and already owns bare names like .card, .rail and .news;
   these pages reuse those deliberately and must not add more.
   ========================================================================== */

/* --- shell ---------------------------------------------------------------- */

/*
 * The page base. Formerly .detail-page, which was accurate when the detail
 * page was the only standalone one; four more pages later the name was a lie.
 * .detail-page is still on the detail pages and still styles their content —
 * it just no longer owns the shell.
 *
 * No WebGL backdrop on any of these pages, so the flat base and the drafting
 * grid are the whole background rather than a fallback.
 */
.pg {
    background-color: var(--void);
    background-image:
        linear-gradient(to right, var(--grid) 1px, transparent 1px),
        linear-gradient(to bottom, var(--grid) 1px, transparent 1px);
    background-size: 48px 48px;
    min-height: 100vh;
    display: flex;
    flex-direction: column;
}

.pg-main {
    flex: 1;
    width: 100%;
    max-width: var(--maxw);
    margin: 0 auto;
    padding: clamp(96px, 14vh, 132px) var(--gutter) 88px;
}

/* --- page art ------------------------------------------------------------- */

/*
 * One quiet construction per page — see the partial for what each one draws.
 *
 * SIZED IN MULTIPLES OF 48, WHICH IS NOT ARBITRARY. The viewBox is 0 0 480 480
 * and every coordinate in it is a multiple of 24, so the drawing's cells stay
 * in step with the 48px drafting grid this rule paints across the page as long
 * as the rendered size is a multiple of 48 — 528 (11 cells) here, 288 (6) on
 * mobile. Scale it with vw instead and that correspondence breaks: the drawing
 * stops sharing the page's module and starts looking like a picture laid on
 * top of one.
 *
 * BOTTOM RIGHT, not beside the heading. The first version sat top-right at
 * half opacity in accent blue, level with the h1, and competed with it. Down
 * here it is a watermark: present, never in the way of the measure.
 *
 * TINTED, AND VISIBLE — WHICH TOOK THREE GOES.
 *
 * It shipped neutral grey at 0.11, then tinted at 0.18, and both came back as
 * "too faint, I cannot see it". The mistake each time was calibrating against
 * a screenshot at full brightness rather than against the thing itself: this
 * sits behind a drafting grid, bleeding off two edges, at the far corner of a
 * page whose content is what the eye is doing. 0.42 is where it starts reading
 * as a drawing rather than as a smudge on the glass.
 *
 * The constraint that survives is what it must not become: a coloured picture
 * competing with the text. It is another layer of the same technical drawing,
 * and if a visitor looks at it before they look at the heading, it has gone
 * too far in the other direction.
 *
 * aria-hidden and pointer-events:none — it is decoration, and nothing on the
 * page depends on seeing it.
 */
.pg-art {
    position: fixed;
    inset: 0;
    overflow: hidden;
    pointer-events: none;
    z-index: 0;
    color: var(--mist);
}

/*
 * THE SETTLED OPACITY IS A VARIABLE, NOT A VALUE, and that is load-bearing.
 * Four things want a say in it — motif, theme, and whether the entrance has
 * run — and expressing them as four `opacity` declarations puts them in a
 * specificity fight that the theme wins: `:root[data-theme="light"] .pg-art
 * svg` out-specifies `.art-in .pg-art svg`, so on the light theme the drawing
 * would start already visible and never fade in at all.
 *
 * With a custom property the four inputs compose instead of competing: each
 * sets --art-o, and exactly one rule reads it.
 */
.pg-art svg {
    position: absolute;
    right: -48px;
    bottom: -48px;
    width: 528px;
    height: 528px;
    --art-o: 0.42;
}

/* Gold is the logo, not a theme colour, so the About page's mark survives the
   theme switch and leans gold at both ends of its gradient. */
.pg-art .pg-art__gold {
    color: var(--gold);
    --art-o: 0.5;
    --art-c1: var(--gold);
    --art-c2: var(--accent-hi);
}

/*
 * THE GRADIENT STOPS. Two colours the site already owns, running diagonally
 * across the drawing. `stop-color` is a real CSS property, which is the only
 * reason this can be themed at all — a gradient hardcoded in the SVG would be
 * one more palette living outside the stylesheet.
 */
.pg-art__c1 { stop-color: var(--art-c1, var(--accent)); }
.pg-art__c2 { stop-color: var(--art-c2, var(--gold)); }

/*
 * The light theme is a pale ground, so near-white ink vanishes into it and the
 * accents need their darker ends. Ink, not paper, in both directions — and a
 * touch more opacity than the neutral version needed, because colour at 0.09
 * reads as a smudge rather than as a drawing.
 */
:root[data-theme="light"] .pg-art { color: #101a2f; }
:root[data-theme="light"] .pg-art svg {
    --art-o: 0.34;
    --art-c1: var(--accent-deep);
    --art-c2: #a8842c;
}
:root[data-theme="light"] .pg-art .pg-art__gold {
    --art-o: 0.4;
    --art-c1: #a8842c;
    --art-c2: var(--accent-deep);
}

/* Under the content, never over it. Everything the page renders sits in a
   stacking context above the fixed art. */
.pg-main,
.dock,
.pg-foot { position: relative; z-index: 1; }

@media (max-width: 900px) {
    /* 240 keeps the multiple-of-48 rhythm — the cells halve to 24px rather
       than landing on some fraction that lines up with nothing. */
    .pg-art svg {
        width: 288px;
        height: 288px;
        right: -24px;
        bottom: -24px;
    }
}

/* --- page head ------------------------------------------------------------ */

.pg-head {
    max-width: 66ch;
    margin-bottom: clamp(44px, 7vh, 76px);
}

.pg-head .micro { display: block; margin-bottom: 18px; }
.pg-head h1 { margin: 0 0 20px; }
.pg-head .lede { margin: 0; max-width: 60ch; }

/* --- lists ---------------------------------------------------------------- */

/* The news index reuses .news / .news__item from site.css, so a row here and
   a row on the homepage cannot drift apart. Only the count differs. */

.pg-grid {
    display: grid;
    grid-template-columns: repeat(auto-fill, minmax(300px, 1fr));
    gap: clamp(28px, 4vw, 46px);
}

/* .card is sized for the homepage rail — a fixed width inside a flex row.
   In this grid the track decides the width instead. */
.pg-grid .card {
    width: auto;
    display: block;
}

.pg-grid .card__meta { margin-top: 16px; }

/* On the homepage the whole card is made clickable by app.js. These pages do
   not load app.js, so the card IS the anchor and the jump link is redundant. */
.pg-grid .card__jump { display: none; }

/* --- pagination ----------------------------------------------------------- */

/*
 * Hand-rolled rather than {{ $items->links() }}. Laravel's default pagination
 * views are Tailwind markup and this site has no Tailwind — rendering them
 * would drop an unstyled row of blue links onto the page.
 */
.pg-pager {
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: 20px;
    margin-top: clamp(40px, 6vh, 64px);
    padding-top: 26px;
    border-top: 1px solid var(--line);
}

.pg-pager__state {
    font-family: var(--font-mono);
    font-size: 12px;
    letter-spacing: 0.14em;
    color: var(--mist-3);
}

.pg-pager__ends { display: flex; gap: 12px; }

/* The disabled end of the range renders as text, not as a dead link — a link
   that goes nowhere is worse than plain text, and a screen reader announces
   the difference. */
.pg-pager__off {
    display: inline-flex;
    align-items: center;
    padding: 10px 18px;
    font-size: 12px;
    color: var(--mist-4);
    border: 1px solid var(--line);
    border-radius: 999px;
}

/* --- about ---------------------------------------------------------------- */

.pg-about {
    display: grid;
    grid-template-columns: minmax(0, 1fr) minmax(0, 0.85fr);
    gap: clamp(36px, 6vw, 80px);
    align-items: start;
}

.pg-about__copy .lede + .lede { margin-top: 20px; }

.pg-about__time .micro { display: block; margin-bottom: 12px; }
.pg-about__time h2 { margin: 0 0 22px; }

.pg-section {
    margin-top: clamp(56px, 9vh, 104px);
    padding-top: clamp(36px, 5vh, 56px);
    border-top: 1px solid var(--line);
}

.pg-section__head { margin-bottom: clamp(28px, 4vh, 44px); }
.pg-section__head .micro { display: block; margin-bottom: 14px; }
.pg-section__head h2 { margin: 0; }

/* The capability and stat tiles are site.css's .cap and .stat, laid out here
   without the homepage's scroll choreography. */
.pg-tiles {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(240px, 1fr));
    gap: 18px;
}

@media (max-width: 900px) {
    .pg-about { grid-template-columns: minmax(0, 1fr); }
}

/* --- contact -------------------------------------------------------------- */

.pg-contact {
    display: grid;
    grid-template-columns: minmax(0, 0.9fr) minmax(0, 1.1fr);
    gap: clamp(36px, 6vw, 72px);
    align-items: start;
}

@media (max-width: 900px) {
    .pg-contact { grid-template-columns: minmax(0, 1fr); }
}

/* --- footer --------------------------------------------------------------- */

.pg-foot {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: space-between;
    gap: 16px 28px;
    padding: 26px var(--gutter);
    border-top: 1px solid var(--line);
    font-size: 13px;
    color: var(--mist-3);
}

.pg-foot__links { display: flex; flex-wrap: wrap; gap: 22px; }
.pg-foot a { color: var(--mist-3); }
.pg-foot a:hover { color: var(--accent-hi); }

/* --- careers -------------------------------------------------------------- */

/* The facts column — "Engineering · Beijing · Full-time" — sits where the
   newsroom puts the date, and needs to wrap rather than force the row wider.
   .news__date is a fixed 130px track built for "2026-07-12". */
.pg-role .news__date {
    white-space: normal;
    line-height: 1.5;
}

/* --- motion lab ----------------------------------------------------------- */

/* Only /lab/motion uses these. Kept here rather than in a file of their own
   because the lab must load exactly what a real page loads — an extra
   stylesheet is an extra difference between the workbench and the thing on
   the bench. */

.lab-bar {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 14px 20px;
    padding: 18px 22px;
    margin-bottom: 14px;
    border: 1px solid var(--line);
    border-radius: 14px;
    background: var(--glass);
}

/* NOT [data-reveal]. The controls must be usable while the entrance is still
   running — a replay button that fades in after the animation it replays is a
   joke at the operator's expense. */

.lab-bar .btn { padding: 10px 18px; font-size: 12px; }

.lab-speed { display: flex; align-items: center; gap: 10px; }
.lab-speed input { width: 120px; accent-color: var(--accent); }
.lab-speed b { min-width: 3.2em; color: var(--mist-2); }

.lab-engine { color: var(--mist-3); }
.lab-engine b { color: var(--mist-2); }

.lab-note {
    display: block;
    margin: 0 0 clamp(40px, 6vh, 72px);
    color: var(--mist-4);
}

.pg-lab code {
    font-family: var(--font-mono);
    font-size: 0.88em;
    padding: 2px 6px;
    border-radius: 4px;
    background: var(--glass-2);
}

/* --- empty state ---------------------------------------------------------- */

.pg-empty {
    padding: clamp(48px, 8vh, 88px) 0;
    color: var(--mist-3);
    border-top: 1px solid var(--line);
    border-bottom: 1px solid var(--line);
}

.pg-empty h2 { margin: 0; color: var(--mist); }
.pg-empty .lede { max-width: 54ch; }

/* --- reveal --------------------------------------------------------------- */

/*
 * The entrance, in two tiers. assets/js/reveal.js decides which and drives the
 * timing; everything about how it LOOKS is here.
 *
 * VISIBLE UNTIL JAVASCRIPT SAYS OTHERWISE. The hidden state is scoped to the
 * class reveal.js adds to <html>. If that script never runs — 404, error, old
 * browser — the page is static and fully readable rather than a column of
 * invisible text. Same reason site.css declares [data-anim] with opacity 1.
 *
 * TIER ONE, .reveal-on: opacity, a 26px rise, and the background construction
 * drawing itself. 0.8s and var(--ease-out), which are app.js's numbers for the
 * homepage reveals — these pages should not arrive with a different accent
 * from the rest of the site.
 *
 * TIER TWO, .reveal-soft: opacity only. No rise, no stroke animation. But the
 * SEQUENCE survives — reveal.js still offsets each block — because timing is
 * not movement and nothing crosses the screen. That is the same call glyph.js
 * makes: a reduced-motion visitor loses the motion, not the design. An earlier
 * version dropped the whole effect and the result was indistinguishable from
 * the feature never having been built.
 */
/*
 * ARMED, BUT BY NOBODY IN PARTICULAR YET.
 *
 * reveal.js adds this the instant it parses, before it knows which engine
 * will run — GSAP arrives on a deferred script and does not exist yet. It
 * hides the content and nothing more: no transition, because if GSAP wins it
 * owns the animation and a CSS transition underneath would fight its inline
 * styles. Whichever engine starts removes this class and replaces it with
 * its own.
 *
 * The window between the two is one tick, and the cost of not having it is a
 * flash of the settled page before the entrance begins.
 */
.reveal-armed [data-reveal] { opacity: 0; }

/*
 * NOTHING HIDES [data-reveal] IN THE GSAP TIER, AND THAT IS DELIBERATE.
 *
 * The obvious rule here is `.reveal-gsap [data-reveal] { opacity: 0 }`, and it
 * is a trap: GSAP reads the element's CURRENT value as the destination of a
 * from() and as the baseline of a fromTo(), so a stylesheet pinning opacity to
 * 0 makes the timeline animate 0 → 0 and the page never appears. reveal.js
 * hides them with gsap.set() instead — inline, under GSAP's own control, and
 * applied while .reveal-armed is still covering the frame.
 *
 * Do not add an opacity rule here.
 */

/* GSAP writes these properties every frame; a CSS transition on the same
   property fights it and shows up as lag on the background draw. */
.reveal-gsap .pg-art svg,
.reveal-gsap .pg-art [pathLength],
.reveal-gsap .pg-art [fill="currentColor"] { transition: none; }

/*
 * THE TRACE — a short bright segment running the outline, on a loop.
 *
 * The shape is a duplicate of one already in the drawing; the original stays
 * put underneath. Putting the dash on the original instead would hide 92% of
 * that outline, which is a deletion, not a highlight.
 *
 * GSAP drives it when GSAP is there (it can ease and stagger the hand-off from
 * the draw-in). This keyframe version is the fallback, and is also what makes
 * the effect survive a CDN failure.
 */
.pg-art__trace {
    stroke: var(--accent-hi);
    opacity: 0;
    stroke-dasharray: 0.08 0.92;
    stroke-dashoffset: 1;
}

/* Autoplaying, so the reduced tier does not get it at all — that is the one
   distinction this project draws consistently: a scrub survives the setting,
   something moving on its own does not. .reveal-soft is deliberately absent. */
.reveal-on.art-in .pg-art__trace {
    opacity: 0.9;
    animation: pg-art-trace 9s linear 2s infinite;
}

@keyframes pg-art-trace {
    from { stroke-dashoffset: 1; }
    to { stroke-dashoffset: 0; }
}

@media (prefers-reduced-motion: reduce) {
    /* Belt and braces for a setting changed after load. */
    .pg-art__trace { animation: none; opacity: 0; }
}

/* SplitText's masked lines. The wrapper it generates clips the line while the
   text inside rises out of it, which is the difference between type being set
   and a paragraph-shaped box sliding upward. */
.pg-line { will-change: transform; }

.reveal-on [data-reveal] {
    opacity: 0;
    transform: translateY(26px);
    transition: opacity 0.8s var(--ease-out), transform 0.8s var(--ease-out);
    will-change: opacity, transform;
}

.reveal-on [data-reveal].is-in {
    opacity: 1;
    transform: none;
}

/* Dropped once it has arrived. will-change on a few dozen elements that have
   finished moving is a promise the compositor keeps paying for. */
.reveal-on [data-reveal].is-in { will-change: auto; }

.reveal-soft [data-reveal] {
    opacity: 0;
    transition: opacity 0.55s var(--ease-out);
}

.reveal-soft [data-reveal].is-in { opacity: 1; }

/* --- the background, drawing itself --------------------------------------- */

/*
 * The construction behind the page strokes itself in rather than appearing.
 * Same idea as the intro overlay's logo build in app.js, and the same
 * mechanism: pathLength="1" in the markup normalises every shape to a dash
 * length of 1 — a rectangle, a circle and a polyline all become "1 long" —
 * so ONE dashoffset value drives all of them regardless of real geometry. No
 * JS measures anything.
 *
 * Slow on purpose: 1.6s against the text's 0.8s. It is the quietest thing on
 * the page and the only one still moving after the words have settled, which
 * is what makes it read as a backdrop being drawn rather than as a graphic
 * being animated.
 */
/* Starts invisible, settles at whatever --art-o resolved to. The single
   reader of that variable — see the note where it is set. */
.pg-art svg {
    opacity: 0;
    transition: opacity 1.1s var(--ease-out);
}

.art-in .pg-art svg { opacity: var(--art-o); }

/* :not([data-art-trace]) throughout — the trace copy is not part of the build.
   It sits at zero opacity until the outline has closed and then runs its own
   loop, so letting the draw-in own it would fight that. */
.reveal-on .pg-art [pathLength]:not([data-art-trace]) {
    stroke-dasharray: 1;
    stroke-dashoffset: 1;
    transition: stroke-dashoffset 1.6s var(--ease-out);
}

/* Tier by tier, so the drawing builds instead of arriving whole — the same
   reason the intro's three logo tiers are staggered rather than simultaneous.
   Five steps covers the busiest motif; a shorter one simply does not use the
   later ones. */
.reveal-on .pg-art g [pathLength]:nth-child(1) { transition-delay: 0.15s; }
.reveal-on .pg-art g [pathLength]:nth-child(2) { transition-delay: 0.35s; }
.reveal-on .pg-art g [pathLength]:nth-child(3) { transition-delay: 0.55s; }
.reveal-on .pg-art g [pathLength]:nth-child(4) { transition-delay: 0.75s; }

/* One element, both classes — reveal.js puts .reveal-on and .art-in on <html>
   together, so this is `.reveal-on.art-in`, not a descendant combinator. The
   descendant form matches nothing and the drawing never closes. */
.reveal-on.art-in .pg-art [pathLength]:not([data-art-trace]) { stroke-dashoffset: 0; }

/* The solid ticks cannot be dashed — a filled square has no stroke to draw —
   so they fade in last instead, once the lines around them have closed. */
.reveal-on .pg-art [fill="currentColor"] {
    opacity: 0;
    transition: opacity 0.6s var(--ease-out) 1.1s;
}
.reveal-on.art-in .pg-art [fill="currentColor"] { opacity: 0.5; }

/* ============================================================ legal pages ==
 *
 * 隐私政策这类长文。和站内其它页面不同的是，它是拿来"读完"的，不是拿来扫的。
 *
 * 因此这里唯一重要的排版决定是 65ch 的行宽。整站的容器宽度是按图文混排定的，
 * 用同一个宽度铺满一屏纯文字，每行会到九十多个字符 —— 眼睛读到行尾找不回下一
 * 行的行首，长文因此变得难读。这个限制只在这一个页面成立，所以不动全局。
 */
.pg-legal {
    /* font-size 必须写在这里，和 max-width 在同一个元素上。
     *
     * ch 是当前元素字号下 "0" 的宽度。只写 max-width: 65ch 而把字号留在子元素
     * 上，ch 会按继承来的 16px 算，正文却是 14.5px —— 量出来一行能排 78 个拉丁
     * 字符，正好越过这条限制想要挡住的范围。写在一起，65ch 才真的是 65 个字符。
     *
     * 实测：610px / 78 字符 -> 508px / 65 字符；中文相应从 42 字降到 35 字，
     * 都落在长文舒适区内。
     */
    font-size: 14.5px;
    max-width: 65ch;
    margin: 0 auto;
}

.pg-legal__meta {
    margin: 0;
    font-family: var(--font-mono);
    font-size: 11px;
    letter-spacing: 0.06em;
    color: var(--mist-4);
}

.pg-legal__meta span { margin: 0 8px; }

.pg-legal__intro {
    margin-bottom: 46px;
    padding-bottom: 28px;
    border-bottom: 1px solid var(--line);
}

.pg-legal__intro p {
    margin: 0;
    font-size: 16.5px;
    line-height: 1.7;
    color: var(--mist);
}

/*
 * 条款索引。
 *
 * 两列，不是一长条竖排：十条挤成一列会把首屏推得很低，而它本来是"扫一眼
 * 找到那一条"的东西，不是正文。窄屏回落成一列。
 *
 * 编号和标题之间用 baseline 对齐，和下面小节标题的处理保持一致 —— 编号比
 * 标题小一号，居中会让它浮在半空。
 */
.pg-legal__toc {
    margin: 0 0 46px;
    padding: 22px 24px;
    border: 1px solid var(--line);
    border-radius: 10px;
    background: var(--glass);
}

.pg-legal__toc ol {
    display: grid;
    grid-template-columns: 1fr 1fr;
    gap: 2px 24px;
    margin: 0;
    padding: 0;
    list-style: none;
    /* 先竖后横：读的顺序是一列到底再换列，和条款编号的走向一致。
       不加这一行会变成横向蛇形，一二并排、三四并排，扫起来很别扭。 */
    grid-auto-flow: column;
    grid-template-rows: repeat(6, auto);
}

.pg-legal__toc a {
    display: flex;
    align-items: baseline;
    gap: 9px;
    padding: 5px 0;
    font-size: 13.5px;
    color: var(--mist-3);
    text-decoration: none;
    transition: color 0.2s var(--ease-out);
}

.pg-legal__toc a:hover { color: var(--mist); }

.pg-legal__toc-n {
    flex: 0 0 auto;
    min-width: 1.4em;
    font-family: var(--font-mono);
    font-size: 11px;
    color: var(--accent-hi);
}

@media (max-width: 719px) {
    .pg-legal__toc ol {
        grid-template-columns: 1fr;
        grid-auto-flow: row;
        grid-template-rows: none;
    }
}

.pg-legal__sec { margin-bottom: 40px; }

.pg-legal__h {
    display: flex;
    /* baseline 而不是 center：序号比标题小，居中会让它浮在半空。
       对齐基线才是两段文字并排时眼睛期待的位置。 */
    align-items: baseline;
    gap: 10px;
    margin: 0 0 14px;
    font-family: var(--font-display);
    font-size: 17px;
    font-weight: 500;
    letter-spacing: 0.01em;
    color: var(--mist);
}

.pg-legal__n {
    flex: 0 0 auto;
    font-family: var(--font-mono);
    font-size: 12px;
    color: var(--accent-hi);
}

/* 正文由 RichText 输出，标签不固定（p / ul / ol / strong / a / code），
   所以按子元素选，不按类名选。 */
.pg-legal__sec p,
.pg-legal__sec ul,
.pg-legal__sec ol {
    margin: 0 0 12px;
    /* 字号继承自 .pg-legal。在这里重新声明一次，就是把行宽和字号又拆成两处，
       下次改字号时 65ch 会再次悄悄失准。 */
    line-height: 1.75;
    color: var(--mist-3);
}

.pg-legal__sec p:last-child,
.pg-legal__sec ul:last-child,
.pg-legal__sec ol:last-child { margin-bottom: 0; }

.pg-legal__sec ul,
.pg-legal__sec ol { padding-left: 1.35em; }

.pg-legal__sec li { margin-bottom: 5px; }

.pg-legal__sec strong {
    font-weight: 500;
    color: var(--mist);
}

/* 政策里出现的是 localStorage 这类标识符，不是代码块。给一点区分度就够，
   不要整块底色 —— 那会把一句话读成一段引用。 */
.pg-legal__sec code {
    font-family: var(--font-mono);
    font-size: 0.88em;
    padding: 1px 5px;
    border-radius: 3px;
    background: var(--glass-2);
    color: var(--mist-2);
}

.pg-legal__sec a {
    color: var(--accent-hi);
    text-underline-offset: 3px;
}

.pg-legal__sec--contact {
    margin-top: 52px;
    padding-top: 30px;
    border-top: 1px solid var(--line);
}

/* dt/dd 两列。用 grid 而不是 float：dd 的内容长度不定（地址可能折行），
   grid 会让两列各自按最长的一项对齐，float 则要靠猜一个固定宽度。 */
.pg-legal__dl {
    display: grid;
    grid-template-columns: max-content 1fr;
    gap: 8px 20px;
    margin: 16px 0 0;
    font-size: 14px;
}

.pg-legal__dl dt {
    font-family: var(--font-mono);
    font-size: 11px;
    letter-spacing: 0.06em;
    color: var(--mist-4);
    /* dt 比 dd 小一号，两列的基线因此对不上。这一点点偏移把它压回同一行。 */
    padding-top: 2px;
}

.pg-legal__dl dd {
    margin: 0;
    color: var(--mist-2);
}

.pg-legal__dl a { color: var(--accent-hi); }

@media (max-width: 719px) {
    /* 窄屏放弃两列：max-content 那一列在小屏上会把 dd 挤成一列竖排的字。 */
    .pg-legal__dl {
        grid-template-columns: 1fr;
        gap: 3px 0;
    }
    .pg-legal__dl dd { margin-bottom: 12px; }
}