/* ========================================================================== np-blend-forms.css — THE NEW POWER BLEND, FORMS EDITION Dedicated forms wave, 2026-08-21 (Zeek: "Forms, yes. Dedicated sweep"). WHY ITS OWN FILE AND NOT np-blend-p100.css ------------------------------------------ Two reasons, one practical and one architectural. Practical: the terms/privacy/ec-next-steps/workshop batch is editing np-blend-p100.css concurrently in another worktree, and a shared file is a merge collision waiting to happen. Architectural: the forms are NOT the nineteen-template marketing family. They are a separate design system with its own bible (docs/P100-FORMS-DESIGN-SYSTEM.md) — a single flat dark app surface, a 780px reading column, Poppins headings over Inter inputs, its own radii ladder. Batch A's layer re-points the marketing system's `--p-*` tokens; nothing in it applies here. THE TWO BIBLES, AND WHO WINS WHERE ---------------------------------- docs/NP-BLEND-THEME.md wins on COLOUR. docs/P100-FORMS-DESIGN-SYSTEM.md wins on LAYOUT, STRUCTURE and TYPE. So this file changes what things are coloured and nothing else, with two named exceptions: the focus ring's `box-shadow` (§1, which paints outside the box and cannot move anything) and the header lockup repair Zeek called for in live review (§6b, four declarations, all listed there). Nothing else sets a size, a spacing, a radius, a font-family or a position. The forms system's Poppins-headings / Inter-body split is left ALONE on purpose: the Inter half is injected at runtime by the form bundles, which are served from the PRODUCTION TPX backend and are not this wave's to edit. THE FORM-BLEND GRAMMAR (derived from NP-BLEND-THEME.md, applied to controls) --------------------------------------------------------------------------- GOLD #C8A951 — static identity. Eyebrows and badges, section labels, NUMERALS (geo numbers, step badges, completed-step plates), static helper/context panels, the dropzone icon disc, the headshot ring, decorative rules. Solid, never gradient on a narrow glyph (hard rule 2). RED #FB0401 — live action only. Focus, required markers, selected/active states, hovers, remove buttons, validation errors. Small red TEXT (< 18.66px bold / < 24px normal) takes the dark-mode lift #FF5A57 (hard rule 3 / flag 124's dark-side mirror). GREEN — the COMMIT. Next / Submit / Continue-to-payment. Per the hybrid CTA rule every one of these measured 13-16px, i.e. the `--deep` band, so they are #007F44 (5.10:1 on white) with hover #006638 (7.10:1). See §0 for the three greens this replaces, all of which fail white text. GRADIENT — progress bars ONLY. A progress fill is the one wide shared object in a form, and it carries no text (hard rule 1). RATIO. NP-BLEND-THEME.md asks for ~90/10 gold-to-red on member surfaces. A form cannot reach that — its whole job is interactive state, and red IS the interactive colour. What the wave does instead is honest to the rule's intent: every DECORATIVE red (an eyebrow, a static label, a context panel, a numeral, an icon disc) moves to gold, and red keeps only what the user's action lights up. Red stopped being wallpaper; it did not stop being red. HOW THIS SHEET REACHES ITS TARGETS ---------------------------------- Every rule is scoped `body.np-forms …`, which buys one class of specificity over each host system's own rules, and — the point of the wave — over the `