/* =================================================================== GRAVITY FORMS skin — the dark-surface form. The request form is a Gravity Forms embed (2026-08-21), so its markup is GF's and cannot be changed from here. This file makes that markup render as the house form component: the same `.field` / `.field-label` / `.field-input` treatment global.html has, on the same tokens, so the embedded form is indistinguishable from the hand-built one it replaced. ⚠️ It assumes a DARK surround, because that is the only place a form appears in this design — the `--ink` inset box in `.request`. A form on a light band would need a modifier; there isn't one yet because there is no such form. ⚠️⚠️ THE WRAPPER MUST CARRY `gform-theme__disable`. That is Gravity Forms' own opt-out hook, and without it this skin cannot work — not because of a specificity race it loses narrowly, but because GF's reset sheet does this: .gform-theme--framework :where(:not(html):not(iframe)… ) { all: unset; display: revert } `all: unset` on every descendant, at (0,1,0) — the same specificity as `.btn` — and loaded after vendor.css, so it simply wins. Measured with it live: the submit button lost its height (54px → 38px), its background (`--primary` → GF's #204CE5), its uppercase and its 5px corner notch, all at once. No amount of depth on THIS file would have saved `.btn`, because `.btn` is not this file. Every rule in GF's reset and framework sheets is wrapped in `:where(:not(.gform-theme__disable):not(.gform-theme__disable *) …)`, so one class on the wrapper switches all ~558KB of it off for this form and leaves the cascade to us. It is per-form, needs no WordPress setting, and behaves identically here and on the real site — which is why it is preferred over Forms → Settings → "Output Default CSS: No" or the `gform_disable_css` filter, both of which also work. With GF's CSS disabled, its four tags are fetching ~558KB from another domain to do nothing. They are kept on this page so that what is verified here is what WordPress will actually serve; on a purely static build they can go. Load order still matters for the rest: this file comes after the section sheets and after GF's own, before request-modal.css. The pasted markup also carries an inline