/* ═══════════════════════════════════════════════════════════════════════════ vanta-pdp.css — THE PRODUCT DETAIL PAGE. Owner brief, 2026-08-24 (client demo): "make product pages for vanta match this styling — only difference with ours is we dont do subscriptions." The reference is the client's own number-one reference site, refinedbiolabs.com (voice.references[0] in client.json), and the surface being matched is its PDP: a tall tinted media plate on the left, and on the right ONE bordered card that carries the whole purchase decision in a fixed order — category · title + price · attribute chips · one-line description · size · quantity · bundle · COA + add-to-cart · dispatch · details WHAT IS MATCHED AND WHAT IS NOT. The reference is taken for STRUCTURE — the order of the blocks, the card, the chip and pill idiom, the label register, the bundle row, the dispatch panel. It is NOT taken for colour or type: Vanta is a monochrome brand (frontend/vanta-mono.css) on Sora/Barlow (frontend/vanta-type.css), and the reference's lavender/serif identity has no business here. BUILD-DEFAULTS.md's hierarchy of authority reads a reference site for structure, never for colour, and this file is that rule applied to one page. THE SUBSCRIPTION BLOCK IS NOT HERE, and its absence is the owner's own line: this engine has no subscription rail, so a "Subscribe & save" panel would be a control that does nothing and a price that cannot be charged. It is not styled away — it is never emitted (see apply-pdp.mjs). ── TWO HOUSE RULES THIS FILE KEEPS ─────────────────────────────────────── NO HEX IN THIS FILE, AND NO LITERAL FONT FAMILY. Three sessions are on this client at once: the palette lives in vanta-mono.css (declared on html:root, so it out-specifies every :root on the site) and the type lives in vanta-type.css. Every colour and every face below is a var() read from those, so the palette can move under this file without it going stale. SPECIFICITY, NOT SOURCE ORDER. product.html carries ~170 lines of its own inline