/* ══ The document design system ══════════════════════════════════════════════ One source of truth for the proposal, the invoice and the contract. Every part the three documents have in common — the sheet, the letterhead, the meta band, parties, section bands, label/value fields, text blocks, the schedule card, totals and the footer — is defined once, here. An edit to a shared component changes all three documents; that is the whole point of this file. Loaded by all six document pages (the three *_public.html and the three *_edit.html) BEFORE that document's own stylesheet: fonts_doc.css → doc_core.css → _doc.css → doc_print.css → _doc_brand What still belongs in a per-document stylesheet is only what genuinely exists in one document: the proposal's package cards, add-ons and timeline; the invoice's line items, amount-due callout and payment panel; the contract's numbered clauses, signature blocks and audit trail. If you find yourself writing the same rule in two of them, it belongs here instead. ── Class naming ── Components are named for what they are, not for the document they came from: .text-block, not .term or .clause; .field, not .fact or .sc-cell. Every rule also lists the older per-document class names as extra selectors. Those aliases are load-bearing and must not be dropped: a saved proposal/invoice/contract is a frozen HTML snapshot (Proposal.content, Agent.*_template_html, …) written with whatever class names were current the day the vendor saved it. Nothing ever rewrites that markup, so a rule that only matched the new name would leave every existing document unstyled. New markup should use the modular name; both render identically. ═════════════════════════════════════════════════════════════════════════ */ :root { /* ── Brand pipeline — do not rename. _doc_brand.html overrides these from Agent.doc_theme_vars via an inline