
/* CHOSEN: B (wizard) with A's split entry promoted to step 1 (DECISIONS.md).
   B alone dropped you straight into exhibitor fields and made a visitor read
   past an application. A alone put the choice up front but then dumped one
   long form under it. Combined: the choice IS step 1, and the three steps
   after it are the ones that path actually needs.

   Everything visible comes from the shared kit — .stepper .step .field-row
   .label .input .select .textarea .hint .err-msg .opts .opt .box .req
   .is-filled .is-focus .actions .success .kv .fs-note .sum .bar .navbtns
   .form-grid, plus the graphic layer (data-lines, .ndiv, .rrule,
   .icowell.solid). Only the four things below are page CSS. */

/* 1. PATH-CONDITIONAL STEP VISIBILITY — the whole point of the merge, and the
   one thing no utility or component can express. The choice made in step 1
   sets data-path on the wizard; the stepper labels, the step-2 panel and the
   summary rail all carry both variants in the markup and CSS reveals the one
   that belongs to the chosen path. Done in CSS rather than JS so the branch is
   visible in the source and works with scripting off. */
[data-path="exhibitor"] .p-vis,
[data-path="visitor"]  .p-exh { display:none }

/* 2. The wizard's two-column shell and its sticky rail. Layout unique to this
   page; no utility exists for `sticky` + a token top offset. */
.wizard{display:grid;grid-template-columns:minmax(0,1.9fr) minmax(0,1fr);
  gap:var(--gap-xl);max-width:var(--maxw);margin:0 auto;align-items:start}
.rail{position:sticky;top:var(--gap-xl);display:grid;gap:var(--gap-md)}
@media(max-width:980px){ .wizard{grid-template-columns:1fr} .rail{position:static} }

/* 3. .bar's fill. .bar is in base.css; its inner span is not. */
.bar i{display:block;height:100%;width:42%;border-radius:var(--r-pill);background:var(--cream)}

/* 4. The step-1 path card. A real <label> wrapping a real radio, so it is
   keyboard operable and announced as a choice — not a div with a click
   handler. PROMOTION CANDIDATE: this is a component, not page layout, and it
   belongs in base.css the moment a second page needs a large choice card
   (Contact and Exhibitor Feedback both will). Left here only because this
   task may write one file. */
.paths{display:grid;grid-template-columns:1fr 1fr;gap:var(--gap-md);
  max-width:var(--maxw);margin:0 auto}
.path{position:relative;display:grid;gap:var(--gap-sm);padding:var(--gap-lg);cursor:pointer;
  border-radius:var(--r-panel);border:1.5px solid var(--ink-hairline);
  background:color-mix(in oklab,var(--navy-950) 34%,transparent);
  transition:border-color var(--d-base) var(--e-enter),transform var(--d-base) var(--e-enter)}
.path:hover{transform:translateY(-2px);border-color:var(--ink-rim)}
.path>input{position:absolute;opacity:0;width:1px;height:1px}
.path:has(>input:checked){border-color:var(--cream);box-shadow:var(--sh-sm)}
.path>input:focus-visible~.path-top .box{outline:2px solid var(--cream);outline-offset:3px}
.path>input:checked~.path-top .box{background:var(--cream);border-color:var(--cream)}
.path>input:checked~.path-top .box.round::after{opacity:1}
.path-top{display:flex;align-items:center;gap:var(--gap-sm)}
.path-top .name{font-family:var(--f-display);font-weight:800;
  letter-spacing:var(--ls-display-tight);font-size:var(--t-display-sm);color:var(--cream)}
.path .price{font-family:var(--f-mono);font-weight:800;font-size:var(--t-body-lg);color:var(--cream);margin:0}
.path ul{margin:0;padding-left:1.1em;display:grid;gap:6px;font-size:14px;color:var(--ink-84)}
.path ul li::marker{color:var(--accent)}
@media(max-width:820px){ .paths{grid-template-columns:1fr} }

/* 5. GAP IN THE SHARED FORM KIT — base.css styles every control state except
   disabled, so a locked field is indistinguishable from an open one. Flagged
   for promotion; kept minimal here. */
.input[disabled],.select[disabled],.textarea[disabled]{
  opacity:.5;cursor:not-allowed;border-style:dashed;
  background:color-mix(in oklab,var(--navy-950) 55%,transparent)}
