/* ============================================================================================
   Gravity Forms — only the parts the design has no name for.
   ============================================================================================

   Added 22 Oct 2026 when the three static placeholder forms became real ones; rewritten the
   same week, because the first version was the wrong idea done carefully.

   ⚑ WHAT IT USED TO BE, AND WHY THAT FAILED. This file held the whole form design re-expressed
   in GF's class names — a second `.form` grid written as `.gform_wrapper form`, a second set of
   input rules written as `.gform_wrapper .ginput_container input`, a second pill written as
   `.gform_button`. Its own header said "if the two ever disagree, the page sheets are right",
   which was an accurate prediction: they disagreed immediately, because THE THREE FORMS ARE NOT
   THE SAME DESIGN. The homepage centres its submit button and gives the message box 104px;
   Contact and Partner left-align theirs and give it 132px. A single copy cannot hold a
   difference it was never told about, so all three rendered as the homepage — and the homepage
   rendered wrong too.

   ⚑ AND THE COPY HID THE REAL BUG FOR LONGER. Every field sat in one narrow column down the
   left of the card with the right half empty. The cause was one element: GF wraps .gform_fields
   in a .gform-body, which was not in the `display:contents` rule, so IT became the only grid
   item and took column one while the fields stacked inside it. Because this file looked like a
   complete, considered form design, the fault read as a design decision rather than a missing
   selector.

   NOW: inc/gravityforms.php relabels GF's markup with the design's own class names — `.form` on
   the form, `.field` (and `.full`) on every .gfield, `.pill.pill--solid` on the submit button.
   The rules the client approved then apply to the real form, unchanged, out of
   assets/css/pages/{home,contact-us,partner-with-us}.css, which are generated from the mockups.
   Each page gets its own variant for nothing.

   So what is left here is only what GF has and the design does not. Anything you are tempted to
   add that the design already names belongs in the mockup, not in this file — see check 900.
   ========================================================================================== */

/* ⚑ THE ONE THAT BROKE IT. GF nests the fields two levels deep:
   form > .gform-body > .gform_fields > .gfield. The design's `.form` is a two-column grid whose
   items are the fields, so both wrappers have to get out of the way. Miss either one and the
   grid still "works" — it just has a single item in it, and a form that lays out down one half
   of the card looks like a styling choice rather than a bug. */
.gform_wrapper .gform-body,
.gform_wrapper .gform_fields {
  display: contents;
}

/* ⚑ THE SAME WRAPPER, ONE LEVEL DOWN, AND IT IS WHY THE DESIGN NEVER SAYS width. In the mockup
   the control is a direct child of `.field`, which is a flex column, so it stretches to the
   column on its own. GF puts a .ginput_container in between: the container stretches and the
   control inside it falls back to its intrinsic size — 215px for a text input, 242px for the
   select, 407px for the message box, each a different width in a form that should have two.
   Nothing looks broken, it just looks careless, which is the version nobody reports.

   Not expressed as `.field input { width: 100% }` in the mockups, because then the mockup and
   the real page would be relying on different mechanisms to reach the same width, and only one
   of them would be the approved one. Everything box-sizing needs is already global (shell.css
   line 34), so the padding and border stay inside the column. */
.gform_wrapper .ginput_container > input,
.gform_wrapper .ginput_container > select,
.gform_wrapper .ginput_container > textarea {
  width: 100%;
}

/* The footer holds the submit button, where the design has one more `.field full`. Giving it
   the same box is what lets `.form .pill { align-self: center }` on the homepage and
   `align-self: flex-start` on the other two work without either page knowing GF exists. */
.gform_wrapper .gform_footer {
  grid-column: 1 / -1;
  display: flex;
  flex-direction: column;
  gap: 8px;
  margin: 0;
  padding: 0;
}

/* ⚑ "(Required)" IS PART OF THE LABEL TEXT in this GF version, not a separate element, so it
   inherits the label's uppercase .2em tracking and reads as shouting. The design marks the
   other way round — `Phone (optional)`, styled by `.field label small` — so this is set to the
   same values that rule uses, and the two forms that have optional fields already match. */
.gform_wrapper .gfield_required {
  font-size: inherit;
  font-weight: 400;
  letter-spacing: .12em;
  text-transform: none;
  opacity: .8;
}

/* Validation and the confirmation message. The design has no error state — the mockups' forms
   could not be submitted — so this is the smallest thing that reads as ours: the body size and
   leading already in use, in a red dark enough to pass AA on --card. */
.gform_wrapper .gform_validation_errors,
.gform_wrapper .validation_message {
  grid-column: 1 / -1;
  font-size: 13px;
  line-height: 1.7;
  color: #8C1D18;
}

.gform_confirmation_message {
  font-size: 15px;
  line-height: 1.8;
  color: var(--ink);
}

/* ============================================================================================
   GRAVITY FORMS COMPENSATION — not styling. Do not remove without reading this.
   ============================================================================================

   GF's own stylesheet is dequeued in inc/gravityforms.php, and some of what it did was never
   visual. Those jobs move here. Each of these renders as visible junk on the page if it goes
   missing, not as an error, so there is nothing to notice until a client or a visitor sees it.

   ⚑ THE HONEYPOT. GF adds a hidden field to catch bots, and it is a REAL labelled input — it
   showed on all three forms the moment the sheet came off, as a box labelled "URL" on Contact
   and Partner and "Name" on the homepage. GF randomises that label from a pool, so it cannot be
   hidden by its wording; `.gform_validation_container` is the handle. Measured, not assumed:
   the field was visible on the rendered page before this rule existed.

   ⚑ DO NOT switch the honeypot off instead. It is the only spam control on these forms — there
   is no CAPTCHA and no Akismet key on this install.

   ⚑ THE !important IS LOAD-BEARING NOW. The honeypot field is a .gfield, so since the relabel
   it also carries `.field`, which is `display:flex`. Without !important the design's own rule
   would put the bot trap back on the page.
   ========================================================================================== */

.gform_wrapper .gform_validation_container,
.gform_wrapper .gform_validation_container * {
  position: absolute !important;
  left: -9999px !important;
  width: 1px !important;
  height: 1px !important;
  overflow: hidden !important;
}

/* Screen-reader-only text GF emits — instructions, "required" announcements, the live region it
   writes validation into. Visible without GF's sheet. */
.gform_wrapper .gform-field-label--type-sub,
.gform_wrapper .screen-reader-text,
.gform_wrapper .gform_hidden,
.gform_wrapper .gf_invisible {
  position: absolute !important;
  left: -9999px !important;
  width: 1px !important;
  height: 1px !important;
  overflow: hidden !important;
}
