/* States NOT present in the pristine nearby.css - Step 3.2 of docs/DESIGN_INTEGRATION.md.
   nearby.css defines default/hover/disabled for buttons and active only for .b-pri; the
   spec requires active/hover/focus-visible/disabled/loading/error/empty (as applicable)
   for every interactive component. This file holds ONLY what nearby.css genuinely
   doesn't have - never mixed into nb.css, so the boundary between "your design,
   verbatim" and "gaps filled to satisfy the completeness requirement" stays visible and
   easy to revert or redesign. Every rule reuses EXISTING tokens from
   resources/css/tokens.css - no new hex/px values, per Step 5's rule.

   Three buckets, kept separate on purpose:

     BUCKET A - nearby.css doesn't define this state at all. Temporary in spirit: it
     empties out as states get added to the source design system. If you design a real
     loading spinner, a real active-press for .b-sec, etc., these entries are what to
     replace, not just delete.

     BUCKET B - nearby.css defines a PATTERN, applied here to a context the source
     doesn't cover (e.g. .badge.live exists; .badge.soldout applies the same solid-badge
     mechanism to a status the mockup never shows). Permanent: these aren't gaps waiting
     to close, they're the same design vocabulary doing its job somewhere new.

     BUCKET C (added bulk-page-conversion.md Step 2) - a genuinely new component for a
     page family nearby.css was never scoped to cover (the home page's 632 lines have no
     data table, sidebar, or stat card at all - these pages weren't designed yet when
     nearby.css was written). Not a state gap in an existing pattern like A or B - a new
     pattern, built from the User Pages/ and Organizer Pages/ mockups' own inline
     <style> blocks. Those blocks use the SAME token values as tokens.css (verified:
     --acc:#FF5C35 etc. match byte-for-byte) under shorter ad-hoc names (--accd, --rs,
     --rl, --rx) specific to how each mockup's standalone HTML was authored - every rule
     below is ported using the real tokens.css names, not the mockups' shorthand, so
     there's one token vocabulary in this codebase, not two. Permanent, same as B. */


/* ============================================================================
   BUCKET A — missing states
   ============================================================================ */

/* BUTTON (nb.button) — nearby.css has active only for .b-pri, and no loading state at
   all. .b-dark mirrors .b-pri's own pattern exactly (same translateY(-1px) hover lift,
   same translateY(0) press-cancel). .b-sec/.b-ghost/.b-line have no lift to cancel, so
   each active state deepens whatever its hover already does by one step in the same
   ladder already visible in the file (.b-ghost: line-2 hover -> line active; .b-line:
   .12-alpha wash hover -> .2 active). .b-loading keeps the button's current variant
   colours/dimensions and expects the component to swap its label for a spinner
   (Blade-level, not CSS-only) - simpler than overlaying one via absolute positioning.
   The spinner uses currentColor for both the ring and the arc (two adjacent sides
   transparent), so it needs no per-variant override. */
.nb .b-dark:active{transform:translateY(0)}
.nb .b-sec:active{background:var(--line-2)}
.nb .b-ghost:active{background:var(--line)}
.nb .b-line:active{background:rgba(255,255,255,.2)}

.nb .b-loading{
  pointer-events:none;
  opacity:.72;
}

.nb .spin{
  width:16px;height:16px;flex:none;
  border-radius:50%;
  border:2px solid currentColor;
  border-right-color:transparent;
  border-bottom-color:transparent;
  animation:nb-spin .6s linear infinite;
}

@keyframes nb-spin{
  to{transform:rotate(360deg)}
}

/* No reduced-motion override for .spin, on purpose. nb.css already carries nearby.css's
   own @media(prefers-reduced-motion:reduce){*{animation:none!important}} rule (scoped
   to .nb, but verbatim from the source file) - under that preference .spin freezes into
   a static half-ring. Flagged, not silently decided either way: the frozen ring still
   reads as "busy" alongside the opacity dim and disabled pointer-events, but stops
   communicating progress over time. Overriding nearby.css's own reduced-motion rule for
   just this element is possible (higher specificity would win) - your call. */

/* EVENT CARD (nb.event-card) — nearby.css only defines .poster:hover, no active/press.
   Settles partway back down (-1px, not fully to 0) rather than cancelling the lift
   outright - a card press reads differently from a button press, and "settling, not
   released" is the more common pattern for a tap that's still navigating somewhere. */
.nb .poster:active{transform:translateY(-1px)}

/* nearby.css has no image-load-failure or not-yet-loaded treatment at all - .poster's
   background-image is simply assumed to load. Gives every .poster a --tint ground
   underneath, so a 404'd or still-loading image degrades to a warm neutral panel
   instead of blank/white. This stopped being theoretical during testing: php artisan
   serve's single-request handling dropped both cover-image requests on the event-card
   preview page, and this fallback is what rendered instead - confirmed via curl that
   the URLs were correct (200 in isolation), so the gap was real, not hypothetical. */
.nb .poster{background-color:var(--tint)}

/* x-nb.image — the same --tint ground as .poster, generalised for every OTHER
   image-bearing component (dashboard rows, category tiles, blog cards, gallery
   thumbnails...) instead of each one inventing its own fallback. Unlike .poster's
   404-degrades-invisibly case, this component's $src is null only when
   getImageOrNull()/frontendImageOrNull() already confirmed server-side there's no
   file - so "no src" gets a deliberate icon, not just a bare tint rectangle, since a
   caller-sized box (a 52px row thumbnail, a 240px gallery tile) with nothing in it
   reads as more clearly "no image" than a same-colored blank. overflow:hidden is
   also what keeps a real <img>'s alt text from ever overflowing this box on the rare
   post-getImageOrNull() race (file deleted between the check and the request) -
   there's no oversized-text failure mode left to hit, unlike route('placeholder.image')
   which is never called from here at all. */
.nb .nb-img{position:relative;overflow:hidden;background:var(--tint);display:block}
.nb .nb-img img{width:100%;height:100%;object-fit:cover;display:block;border-radius:inherit;font-size:11px}
.nb .nb-img.is-empty{display:flex;align-items:center;justify-content:center}
.nb .nb-img-fallback{width:28%;max-width:32px;color:var(--mut)}

/* SHARED LOADING/EMPTY PATTERNS — nearby.css has no loading-placeholder or
   zero-results convention anywhere in the file. .nb-skeleton is a shimmer sweep in
   --line/--line-2 (the two tokens the source already uses for "quiet fill" surfaces),
   applied alongside a real component's own sizing class (e.g. class="poster
   nb-skeleton") so a grid doesn't reflow when real content replaces it. .nb-empty is
   just padding - the empty-state component itself (nb.empty-state) is deliberately
   text-only, no invented icon, matching how undecorated the rest of the system is. */
.nb .nb-skeleton{
  background:linear-gradient(90deg,var(--line-2) 25%,var(--line) 37%,var(--line-2) 63%);
  background-size:400% 100%;
  animation:nb-shimmer 1.4s ease infinite;
}

@keyframes nb-shimmer{
  0%{background-position:100% 50%}
  100%{background-position:0% 50%}
}

.nb .nb-empty{padding:var(--sec-y) var(--pad)}

/* TOPBAR (nb.topbar) — the mockup's .city is a static div with no <select>, no form, no
   JS at all - it looks like a dropdown trigger and does nothing. The real component
   wraps a genuine <select> inside .city's existing icon-text-chevron layout; nearby.css
   has no styling anywhere for a <select> living inside that shape, because the source
   never needed one. Made invisible-but-clickable (appearance:none, no border/background
   of its own) so .city's existing flex/gap/padding does all the visual work and the
   select just becomes the middle flex child. */
.nb .city select{
  appearance:none;-webkit-appearance:none;-moz-appearance:none;
  border:0;background:none;outline:0;
  font:inherit;color:inherit;
  cursor:pointer;
}

/* nearby.css's global focus-visible rule (line 107 of nearby.css) covers a/button/
   input - never select, anywhere in the file. Extended to cover it, for every select
   in the nb system that doesn't strip its own outline (nb.toolbar's filter selects,
   for one - they set no outline of their own, so this global rule is the only ring
   they need). */
.nb select:focus-visible{
  outline:2px solid var(--acc);
  outline-offset:2px;
  border-radius:4px;
}

/* .city select DOES strip its own outline (above, needed since a bare <select> box
   would otherwise show a default outline at rest inside .city's borderless layout).
   That reset and the global rule above land at the EXACT SAME specificity - (0,2,1)
   each, .nb .city select vs .nb select:focus-visible - and only the reset being
   written first is what currently keeps the ring alive (the later rule wins a tie).
   tools/focus-outline-check.php flagged this as fragile even though it isn't broken
   today: reorder these two rules, or insert a third same-specificity selector
   between them, and the ring silently disappears with no error anywhere. Given its
   own selector + :focus-visible instead, the same fix already used for
   .bigsearch input and .toolbar .search input - strictly higher specificity than the
   reset by construction, so it wins regardless of file order. */
.nb .city select:focus-visible{
  outline:2px solid var(--acc);
  outline-offset:2px;
  border-radius:4px;
}

/* Real overflow at 375px, not just visually tight - measured, not guessed:
   scrollWidth 459px vs a 375px viewport. nearby.css's own 1040px breakpoint hides
   .nav-links, but the mockup's single static example was never a real component with
   both a working city picker AND an organizer-recruitment CTA AND an auth slot
   together - nothing in the source had to survive this exact combination at 375px.
   Sheds .topbar-cta ("List your event") at nearby.css's own existing 640px breakpoint
   rather than inventing a new one - the same "drop non-essential chrome under width
   pressure" pattern the source already uses for .nav-links, just extended to cover
   what this component added. Removing it alone (119px + gap) clears the overflow with
   room to spare; brand, city picker and the auth slot (avatar or Login) are what
   actually need to survive on a phone. */
@media(max-width:640px){
  .nb .topbar-cta{display:none}
}


/* ============================================================================
   SOURCE CASCADE BUG — the source DOES define this state; its own cascade
   order silently cancels it. Not bucket A (nothing missing) or B (same
   context, not a new one) - a third, hopefully rare category.
   ============================================================================ */

/* SEARCH FIELD (nb.search-field) — nearby.css's global focus ring
   (.nb input:focus-visible{outline:2px solid var(--acc)...}, line 76 of nb.css) and
   .bigsearch input's own reset (outline:0, meant to strip the browser's default blue
   outline at rest) land at the EXACT SAME specificity - (0,2,1) each, .nb + input +
   :focus-visible vs .nb + .bigsearch + input. Whichever comes later in the file wins on
   a tie, and .bigsearch input is defined ~130 lines after the focus rule, so its
   outline:0 cancels the ring unconditionally - not just at rest, but while genuinely
   focused via keyboard too. Confirmed empirically, not just from reading the cascade:
   tabbed a real browser to the search input and read outline-style back as "none".
   "Focus rings must be visible on keyboard nav" is explicit and non-negotiable
   (design-system-integration.md Step 3.2), so this needed a real fix, not a flag.
   Restores the ring with higher specificity ((0,3,1): .nb .bigsearch input:focus-visible)
   rather than relying on load order, so it can't silently break again if nb.css or this
   file ever gets reordered. */
.nb .bigsearch input:focus-visible{
  outline:2px solid var(--acc);
  outline-offset:-2px; /* the ring would otherwise render outside .bigsearch's own rounded edge and look clipped */
  border-radius:4px;
}


/* ============================================================================
   BUCKET B — existing pattern, new context (permanent)
   ============================================================================ */

/* EVENT CARD — sold out is the real equivalent of "disabled" for a card, but it stays a
   genuine, clickable link (the event page is still worth visiting - it explains the
   status, may offer a waitlist later). .badge.soldout applies nearby.css's own solid-
   badge-variant PATTERN (already real via .badge.live) to a status the mockup never
   shows, using --err, which is exactly what that semantic token is for ("meaning only,
   never decoration"). */
.nb .poster.is-soldout{filter:grayscale(.3) brightness(.82)}
.nb .poster.is-soldout .cap{opacity:.85}

.nb .badge.soldout{background:var(--err);color:#fff}


/* ============================================================================
   DELIBERATELY NOT BUILT — states that don't apply, not gaps
   ============================================================================ */

/* BUTTON — no "error" skin. A failed action is surfaced by the calling code (this app
   already has iziToast wired for that); a button re-skinning itself red on failure
   isn't a real pattern nearby.css or most design systems use, and inventing one would
   be manufacturing a state rather than filling a real gap.
   No "empty" state either - doesn't apply to a single atomic control. Empty states
   belong to listings and are built where they're real (nb.empty-state). */


/* ============================================================================
   BUCKET C — new component, new page family (permanent)
   ============================================================================ */

/* PAGE SHELL (nb.user-sidebar / nb.organizer-sidebar) — the account-page two-column
   layout (sidebar + content) every Manage Tickets/Events/Transactions/Withdraw/Support
   page in both mockup batches shares. Ported from both mockups' .page-grid, using the
   customer version's flex-column sidebar (min-height + margin-top:auto on the logout
   row) over the organizer version's position:sticky — sticky breaks the moment a
   sidebar's content is taller than the viewport, which a long nav with an open submenu
   can be; a plain non-sticky column doesn't have that failure mode. */
.nb .page-grid{display:grid;grid-template-columns:260px minmax(0,1fr);gap:28px;align-items:start;padding:34px 0 10px}
.nb .sidebar{background:var(--surface);border:1px solid var(--line);border-radius:var(--r-lg);min-height:calc(100vh - 150px);display:flex;flex-direction:column;overflow:hidden;box-shadow:var(--s1)}

/* Organizer identity — dark card, matches that mockup's own treatment. */
.nb .org-card{background:var(--ink);color:#fff;border-radius:var(--r);padding:18px 15px;margin:10px 10px 0}
.nb .org-card .org-avatar{width:52px;height:52px;border-radius:50%;background:var(--surface);display:grid;place-items:center;color:var(--acc-d);font-weight:700;font-size:18px;margin-bottom:12px;border:3px solid var(--acc)}
.nb .org-card strong{display:block;font-size:16px}
.nb .org-card small{color:#CFCAC2;font-family:var(--fm);font-size:var(--fm-label);font-weight:400}
.nb .org-pill{display:inline-flex;margin-top:10px;padding:5px 10px;border:1px solid rgba(255,92,53,.6);border-radius:var(--r-pill);color:#FF8D70;font-size:10px}

/* Customer identity — light card, matches that mockup's own (different) treatment. No
   profile photo — same call already made for the topbar avatar (an initial, not an
   invented headshot); see docs/DESIGN_PIPELINE.md if a real photo field ever exists. */
.nb .profile-card{padding:24px 22px 20px;border-bottom:1px solid var(--line-2)}
.nb .profile-card .profile-avatar{width:58px;height:58px;border-radius:var(--r-lg);background:var(--acc-w);color:var(--acc-d);display:grid;place-items:center;font-size:22px;font-weight:600;margin-bottom:13px}
.nb .profile-card h2{margin:0;font-size:22px;letter-spacing:-.03em}
.nb .profile-card .handle{margin-top:4px;color:var(--mut);font-size:13px}

/* Nav — one shared vocabulary for both sidebars, consolidated from the two mockups'
   divergent naming (.org-card/.side-link vs .profile-hero/.menu/.menu-group/.submenu)
   rather than porting both verbatim into two different systems. */
.nb .side-nav{padding:12px 10px;flex:1}
.nb .side-link{width:100%;border:0;background:transparent;text-align:left;padding:11px 12px;border-radius:var(--r-sm);color:var(--ink-2);display:flex;align-items:center;gap:11px;font-size:13.5px;min-height:44px;cursor:pointer}
.nb .side-link:hover{background:var(--line-2);color:var(--ink)}
.nb .side-link:active{background:var(--line)}
.nb .side-link.active{background:var(--acc-w);color:var(--acc-d);font-weight:600}
.nb .side-link .ico-slot{width:20px;text-align:center;flex:none}
.nb .side-chev{margin-left:auto;color:var(--mut);transition:transform .15s}
.nb .side-group.open .side-chev{transform:rotate(180deg)}
.nb .side-submenu{display:none;padding:3px 0 7px 43px}
.nb .side-group.open .side-submenu{display:block}
.nb .side-submenu a{display:block;padding:9px 10px;color:var(--mut);font-size:12.5px;border-radius:var(--r-sm)}
.nb .side-submenu a:hover{background:var(--line-2);color:var(--ink)}
.nb .side-submenu a:active{background:var(--line)}
.nb .side-submenu a.active{color:var(--acc-d);background:var(--acc-w);font-weight:600}
.nb .side-divider{border-top:1px solid var(--line-2);margin:6px 12px}
.nb .side-logout{margin-top:auto;padding:14px 12px 16px}
.nb .side-logout .side-link{color:var(--acc-d)}

/* Sidebar nav has no :focus-visible ring of its own — nearby.css's global a/button/
   input:focus-visible rule already covers both the <button> (.side-link on a group
   toggle) and <a> (.side-link/.side-submenu a on a real link) forms these render as, so
   there's nothing missing here. Verify this empirically once a real page uses it,
   same discipline as every other component in this file — not asserted blind. */

/* STAT CARD (nb.stat-card) — a bordered summary card for list-page KPI rows (12 sold,
   ₹48,650 available, etc.). Deliberately its own component, not nb.stat-block wrapped
   in a card: stat-block's typography is tuned for the hero's showcase scale (32px+),
   and every one of these mockups' summary cards is compact (24px value, a small mono
   label, an optional meta line) — forcing the hero's scale into a 4-up card row would
   look oversized, not reused. Same design language (bordered surface, mono uppercase
   label, semantic tone on the meta line), different component for a different job. */
.nb .stats-row{display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:10px;margin-bottom:18px}
.nb .stats-row.cols-3{grid-template-columns:repeat(3,minmax(0,1fr))}
.nb .stat-card{background:var(--surface);border:1px solid var(--line);border-radius:var(--r);padding:16px 17px;min-width:0}
.nb .stat-card .stat-label{font-size:var(--fm-label);font-weight:400;color:var(--mut);margin-bottom:5px;font-family:var(--fm);letter-spacing:.1em;text-transform:uppercase}
.nb .stat-card strong{font-size:24px;letter-spacing:-.03em;display:block;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}
.nb .stat-card .stat-meta{font-size:10.5px;margin-top:4px;color:var(--mut)}
.nb .stat-card .stat-meta.tone-ok{color:var(--ok)}
.nb .stat-card .stat-meta.tone-warn{color:var(--acc-d)}
/* .stats-row.cols-3 at (0,3,0) is more specific than a bare .stats-row override at
   (0,2,0) inside the media query below, so without a matching .cols-3 override here
   too, the 3-column desktop definition would keep winning under 640px regardless of
   source order - specificity, not order, decides a tie here. Caught on the organizer
   dashboard: "$0.00 USD" clipped to "$0...." at 375px because its card was still one
   of three squeezed into a row with no room, not one of two. */
@media(max-width:640px){
  .nb .stats-row{grid-template-columns:repeat(2,minmax(0,1fr))}
  .nb .stats-row.cols-3{grid-template-columns:repeat(2,minmax(0,1fr))}
}

/* DASH SPLIT (organizer dashboard's Upcoming events / Recent bookings pair, and
   anywhere else a page needs an uneven two-column layout side by side). minmax(0,1fr)
   from the start this time, not just at a breakpoint - the same class of bug as
   .page-grid's own 1000px collapse, caught here before it shipped rather than after:
   a bare 1.4fr/1fr pair squeezed both columns narrower and narrower at small widths
   instead of ever actually stacking, each column's content (an image+text row, an
   empty-state message) never got the chance to just go full-width. */
.nb .dash-split{display:grid;grid-template-columns:1.4fr 1fr;gap:20px;align-items:start;margin-top:20px}
@media(max-width:760px){.nb .dash-split{grid-template-columns:minmax(0,1fr)}}

/* Same card, used as a clickable quick-access tile (dashboard) rather than a passive
   KPI display - the only nb.stat-card usage that's genuinely interactive. Hover/focus
   scoped to the <a> form specifically (.nb a.stat-card), not the bare div nb.stat-card
   itself renders everywhere else - a passive KPI card lifting under a mouse it isn't
   listening to would be a tell without a purpose. nearby.css's global
   a:focus-visible rule already covers the keyboard ring; no reset here to fight it. */
.nb a.stat-card:hover{border-color:var(--acc-b);transform:translateY(-1px)}

/* QUICK ACCESS GRID (dashboard) — same bare-1fr blowout as .page-grid's 1000px
   collapse above, just narrower: 4 fixed 1fr tracks holding short-but-unshrinkable
   uppercase labels ("SAVED EVENTS") don't wrap enough to fit 4-across under ~360px,
   and a bare 1fr track grows to fit rather than clipping. minmax(0,1fr) at the base
   size (not just the narrow breakpoint this time - four tiles are tight even before
   375px) plus an explicit 2-column collapse under 480px, same value nearby.css itself
   uses for other 4-up-to-2-up collapses (.footer-cols, .cats' second stop). */
.nb .quick-access-grid{display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:10px}
@media(max-width:480px){.nb .quick-access-grid{grid-template-columns:repeat(2,minmax(0,1fr))}}

/* DATA TABLE (nb.table) — chrome: card wrapper, column-header row, and (once a page
   passes a real paginator) pagination. Rows are page-specific and get built when each
   page converts (Step 3) — the column shapes differ too much across pages (event
   listing vs. transaction ledger vs. payout history) to generalize further without
   forcing an awkward abstraction.

   No overflow:hidden on .data-table, on purpose, even though that's what a rounded
   card normally reaches for. A row's nb.row-menu dropdown is position:absolute inside
   a row inside this card - overflow:hidden clipped it to almost nothing, caught
   visually during verification (the menu opened but rendered as a sliver). Rounding
   .table-head's own top corners instead gets the same visual result (no square corner
   poking past the card's rounded edge) without clipping anything that needs to escape
   the card's bounds. */
.nb .data-table{background:var(--surface);border:1px solid var(--line);border-radius:var(--r-lg)}
.nb .data-table .table-head{display:grid;gap:14px;align-items:center;padding:13px 16px;background:var(--line-2);font-family:var(--fm);font-size:var(--fm-label);font-weight:400;letter-spacing:.1em;text-transform:uppercase;color:var(--mut);border-bottom:1px solid var(--line);border-radius:var(--r-lg) var(--r-lg) 0 0}
.nb .data-table .table-body>*{border-bottom:1px solid var(--line-2);padding:13px 16px}
.nb .data-table .table-body>*:last-child{border-bottom:0;border-radius:0 0 var(--r-lg) var(--r-lg)}
.nb .data-table .table-body>a:hover{background:var(--tint)}

/* LIST ROW (a page's own row markup inside nb.table's :slot) — grid-template-columns
   set via the --cols custom property rather than a plain inline style, specifically
   so the collapse below can override it. A real 375px test on the first page built
   with this pattern (user/event/ticket/index.blade.php) showed why the difference
   matters: an inline style="grid-template-columns:..." has higher precedence than
   ANY stylesheet rule short of !important, so a @media override can set display:flex
   all it wants and the row stays a 5-column grid wider than the viewport regardless.
   --cols is just a variable read BY the stylesheet's own grid-template-columns
   declaration below - switching that declaration's producing property (display) at
   the breakpoint makes --cols irrelevant there, no !important needed. Mirrors the
   original mockups' own collapse (table-head hidden, each row stacked) rather than
   inventing a different narrow-width treatment. */
.nb .list-row{display:grid;grid-template-columns:var(--cols);gap:14px;align-items:center}
@media(max-width:760px){
  .nb .data-table .table-head{display:none}
  /* align-items:stretch (the default - kept explicit since .list-row sets center
     above), not flex-start. A row's children - .row-info in particular - have their
     own min-width:0/ellipsis rules for exactly this breakpoint, but those only
     engage once something gives the child a WIDTH to shrink against. flex-start
     lets every child size to its own max-content width instead, i.e. exactly as
     wide as its longest unwrapped string, silently defeating the ellipsis rules
     below and dragging the whole row - and the page - wider than the viewport.
     docs/UI_DEFECTS.md bucket 7, caught on real transaction remark text. */
  .nb .list-row{display:flex;flex-direction:column;align-items:stretch;gap:6px}
  .nb .list-row .row-amount{text-align:left}
}

/* STATUS BADGE (nb.status-badge) — four semantic tones, reusing the exact tokens
   nearby.css already ships for "meaning only, never decoration" (--ok/--warn/--err
   plus their -w washes) and a fifth neutral tone for draft/queued states nearby.css's
   own semantic set doesn't cover — there's no --neutral token; --line-2/--mut is the
   existing "quiet fill" pair used everywhere else in this codebase for that purpose,
   not a new value. */
.nb .status-badge{display:inline-flex;align-items:center;gap:5px;width:max-content;padding:5px 9px;border-radius:var(--r-pill);font-size:10px;font-weight:600}
.nb .status-badge:before{content:"";width:5px;height:5px;border-radius:50%;background:currentColor}
.nb .status-badge.tone-ok{background:var(--ok-w);color:var(--ok)}
.nb .status-badge.tone-warn{background:var(--warn-w);color:var(--warn)}
.nb .status-badge.tone-err{background:var(--err-w);color:var(--err)}
.nb .status-badge.tone-neutral{background:var(--line-2);color:var(--mut)}
/* outline: a neutral state that must not look like a 'good' one (e.g. booking Active next to payment Paid) */
.nb .status-badge.tone-outline{background:transparent;color:var(--ink);box-shadow:inset 0 0 0 1.5px var(--ink)}

/* FILE UPLOAD WITH PREVIEW (nb.file-upload) — the mockups already dropped the legacy
   image-uploader.min.js plugin (docs/PAGE_CONVERSION_MAP.md 1.6) in favour of plain
   FileReader + a styled drop target; this ports that same approach rather than
   reaching for a plugin the design itself already moved away from. */
.nb .upload-box{height:205px;border:1px dashed var(--acc-b);border-radius:var(--r-lg);background:linear-gradient(135deg,var(--tint),var(--surface));display:flex;align-items:center;justify-content:center;text-align:center;cursor:pointer;overflow:hidden;position:relative}
.nb .upload-box:hover{background:var(--acc-w);border-color:var(--acc)}
.nb .upload-box:active{background:var(--acc-b)}
.nb .upload-box.has-error{border-color:var(--err);border-style:solid}
.nb .upload-box input{position:absolute;inset:0;opacity:0;cursor:pointer;z-index:4}
.nb .upload-box .upload-copy{position:relative;z-index:2;pointer-events:none}
.nb .upload-box .upload-icon{width:44px;height:44px;border-radius:50%;background:var(--surface);border:1px solid var(--line);display:grid;place-items:center;margin:0 auto 9px}
.nb .upload-box b{display:block;font-size:13px}
.nb .upload-box .upload-copy span{display:block;color:var(--mut);font-size:10.5px;margin-top:3px}
.nb .upload-box img{position:absolute;inset:0;width:100%;height:100%;object-fit:cover;display:none;z-index:1}
.nb .upload-box.has-image img{display:block}
.nb .upload-box.has-image:after{content:"";position:absolute;inset:0;background:linear-gradient(transparent 40%,rgba(0,0,0,.55));z-index:1}
.nb .upload-box.has-image .upload-copy{color:#fff;position:relative;z-index:2}
.nb .upload-box.has-image .upload-copy span{color:rgba(255,255,255,.8)}
.nb .upload-box.round{border-radius:50%;width:120px;height:120px;flex:none}

/* .compact - a multi-file/document field (support-ticket attachments) sitting inside
   an otherwise-compact form, not a standalone cover/logo upload. Same box, input, and
   focus-visible relay as the default 205px variant; just a short horizontal row with
   no image preview (createObjectURL() can't render a .pdf/.doc anyway) - selected
   filenames go in .upload-box b as text, kept inside the box by the same
   overflow:hidden the parent already has. */
.nb .upload-box.compact{height:auto;min-height:64px;flex-direction:row;justify-content:flex-start;text-align:left;padding:14px 16px}
.nb .upload-box.compact .upload-copy{display:flex;align-items:center;gap:12px;width:100%}
.nb .upload-box.compact .upload-icon{margin:0;flex:none}
.nb .upload-box.compact .upload-text{min-width:0}
.nb .upload-box.compact b{overflow-wrap:anywhere;display:block}
.nb .upload-box.compact.has-files b{color:var(--acc-d)}

/* .upload-box input is a real file input (type=file, spread full-bleed and made
   transparent) rather than a hidden input triggered by a wrapping <label> the way the
   source mockups did it (display:none input, label captures the click). A hidden
   input is invisible to focus-visible entirely — Tab skips straight past it, so
   keyboard users can never reach it. Kept it a real, visible-to-focus element instead.

   Caught by an actual Tab press once this component finally shipped on a real page
   (organizer profile setup) rather than assumed: nearby.css's global
   input:focus-visible rule DOES apply to the input, but the input itself has
   opacity:0 - opacity makes the whole rendered box invisible, outline included, so
   the ring fired with zero visible feedback. Same bug family as .bigsearch input /
   .toolbar .search input (docs/DESIGN_PIPELINE.md's outline:0 trap), one level
   removed: nothing here resets outline, opacity just as silently eats it. Fixed on
   the box itself, which isn't transparent. */
.nb .upload-box:has(input:focus-visible){outline:2px solid var(--acc);outline-offset:2px}

/* TABS (nb.tabs) — real <a> navigation, not the source mockups' <button class="tab">
   with a client-side JS filter. Every tab across all 15 organizer pages turned out to
   map to a real, distinguishable server-side query (docs/INTERACTIVE_CONTROLS.md
   decision) - an anchor is the correct element for "this click changes the URL and
   loads different data", not a button pretending to. */
.nb .tabs{display:flex;gap:7px;flex-wrap:wrap;margin-bottom:14px}
.nb .tab{padding:7px 13px;border:1px solid var(--line);border-radius:var(--r-pill);background:var(--surface);color:var(--mut);font-size:12px;display:inline-flex;align-items:center;gap:4px}
.nb .tab:hover{border-color:var(--acc-b);color:var(--ink)}
.nb .tab:active{background:var(--line-2)}
.nb .tab.active{background:var(--ink);border-color:var(--ink);color:#fff}
.nb .tab .count{font-family:var(--fm);font-size:11.5px;font-weight:400;color:var(--mut)}

/* TOOLBAR (nb.toolbar) — one real GET <form>: submit-to-search (not live/debounced -
   every search here is a query against an unindexed column, docs/INTERACTIVE_CONTROLS.md),
   onchange-submits selects (the same pattern nb.topbar's city picker already uses),
   Laravel's own pagination further down this file. No AJAX anywhere in this family -
   one interaction model for the whole panel, not a different one per page. */
.nb .toolbar{background:var(--surface);border:1px solid var(--line);border-radius:var(--r-lg);padding:11px;display:flex;align-items:center;gap:9px;flex-wrap:wrap;margin-bottom:12px;box-shadow:var(--s1)}
.nb .toolbar .search{height:40px;border:1px solid var(--line);border-radius:var(--r-sm);background:var(--surface);display:flex;align-items:center;gap:8px;padding:0 4px 0 12px;flex:1;min-width:220px}
.nb .toolbar .search input{border:0;outline:0;background:transparent;width:100%;font-size:13px;height:100%}

/* Same cascade mechanics as nb-extensions.css's earlier SOURCE CASCADE BUG entry for
   .bigsearch input, except this one is self-inflicted, not nearby.css's: the outline:0
   above (needed to strip the browser's default outline at rest) is
   .nb .toolbar .search input at specificity (0,3,1), which beats nearby.css's global
   .nb input:focus-visible at (0,2,1) in every state, including genuinely focused -
   caught via a real Tab press during verification, not read off the cascade. Same
   fix: restore the ring at higher specificity. */
.nb .toolbar .search input:focus-visible{
  outline:2px solid var(--acc);
  outline-offset:-2px;
  border-radius:4px;
}

.nb .toolbar .search button{border:0;background:transparent;width:32px;height:32px;border-radius:var(--r-sm);display:grid;place-items:center;color:var(--mut);cursor:pointer;flex:none}
.nb .toolbar .search button:hover{background:var(--line-2);color:var(--ink)}
.nb .toolbar .search button:active{background:var(--line)}
.nb .toolbar select.select{height:40px;border:1px solid var(--line);border-radius:var(--r-sm);padding:0 11px;background:var(--surface);color:var(--ink-2);min-width:125px}
.nb .view-toggle{display:flex;border:1px solid var(--line);border-radius:var(--r-sm);overflow:hidden;flex:none}
.nb .view-toggle button{width:40px;height:38px;border:0;background:var(--surface);display:grid;place-items:center;cursor:pointer;color:var(--mut)}
.nb .view-toggle button:not(.active):hover{background:var(--line-2);color:var(--ink)}
.nb .view-toggle button:not(.active):active{background:var(--line)}
.nb .view-toggle button.active{background:var(--ink);color:#fff}
@media(max-width:640px){.nb .toolbar .search{min-width:100%}}

/* PAGINATION (nb.table's :paginator prop) — Laravel's real LengthAwarePaginator,
   already the app-wide pattern (User/UserController.php:99, OrganizerController.php:127
   both already call ->paginate(getPaginate())) - this only builds the presentational
   wrapper, not new pagination logic. The calling controller must call
   ->withQueryString() on the paginator or search/filter state is lost on page 2 - easy
   to miss, called out again in the component's own doc comment. */
.nb .pagination{display:flex;justify-content:space-between;align-items:center;padding:14px 3px;color:var(--mut);font-size:11px;flex-wrap:wrap;gap:10px}
.nb .pages{display:flex;gap:5px}
.nb .pages a,.nb .pages button{width:32px;height:32px;border:1px solid var(--line);border-radius:var(--r-sm);background:var(--surface);display:grid;place-items:center;color:var(--ink-2);font-size:12px}
.nb .pages a:hover{border-color:var(--acc-b);color:var(--ink)}
.nb .pages a:active,.nb .pages button:active{background:var(--line-2)}
.nb .pages a.active{background:var(--ink);color:#fff;border-color:var(--ink)}
.nb .pages button:disabled{color:var(--faint);cursor:not-allowed}

/* ROW MENU: now <x-action-menu> (assets/global/css/action-menu.css). The old absolute dropdown
   here was clipped by .mrow-desktop{overflow:hidden} and opened off-screen on phones - removed. */

/* ROW INFO CELL — the image/icon + title + sub-line pattern repeated inside table
   rows and card lists across every Step 3 customer-account page (a ticket row's
   event thumbnail+name+venue, a transaction row's icon+description, the dashboard's
   Upcoming Tickets card). Small enough that duplicating the class names per page
   (like nb.table's own rows) would just be copy-paste, but common enough across this
   one batch of pages to be worth a shared class - same reasoning BUCKET C's other
   entries already used. */
.nb .row-info{display:flex;align-items:center;gap:12px;min-width:0}
.nb .row-info img,.nb .row-info .nb-img{width:52px;height:52px;border-radius:var(--r-sm);object-fit:cover;background:var(--tint);flex:none}
.nb .row-info .row-icon{width:40px;height:40px;border-radius:var(--r-sm);display:grid;place-items:center;flex:none;background:var(--line-2);color:var(--ink-2)}
.nb .row-info .row-icon.tone-ok{background:var(--ok-w);color:var(--ok)}
.nb .row-info .row-icon.tone-warn{background:var(--warn-w);color:var(--warn)}
/* The title+sub text wrapper - .row-info's one non-flex:none child (an unclassed
   div in every consumer's markup: icon/img, then this). .row-info's own
   min-width:0 above only lets ROW-INFO shrink inside ITS parent; this div is
   itself a flex child of .row-info's own row and needs the same min-width:0 or
   it inherits the flex default (min-width:auto = its content's width) and never
   shrinks enough for row-title/row-sub's ellipsis rules to have anything to do. */
.nb .row-info>div{min-width:0;flex:1}
.nb .row-info .row-title{font-weight:600;font-size:14px;margin-bottom:3px;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}
.nb .row-info .row-sub{font-size:12px;color:var(--mut);overflow:hidden;text-overflow:ellipsis;white-space:nowrap}

.nb .row-amount{text-align:right}
.nb .row-amount strong{display:block;font-size:14px}
.nb .row-amount span{display:block;font-size:11px;color:var(--mut);margin-top:2px}

/* minmax(0,1fr), not a bare 1fr - a bare 1fr track still carries CSS grid's default
   min-width:auto floor, so a descendant with non-shrinkable content (nb.event-card's
   .rail, overflow:auto but only actually scrollable once its own box has a hard width
   ceiling) can force the WHOLE TRACK wider than the viewport instead of scrolling
   internally. Caught at 375px on the dashboard's "Discover what's next" rail:
   scrollWidth 510 vs a 375 viewport, section/.page-grid both measured exactly as wide
   as the rail's un-scrolled content (484px) rather than the available 323px - the
   grid literally grew to fit content instead of clipping/scrolling it, the same
   failure mode minmax(0,1fr) already prevents at desktop width one line above. */
@media(max-width:1000px){.nb .page-grid{grid-template-columns:minmax(0,1fr)}.nb .sidebar{position:static;min-height:auto}}

/* FORM CARD (nb.user support create, and every future real form in this system - the
   organizer event/onboarding forms will need the exact same primitives). Ported from
   the mockups' own .form/.fields/.field pattern, one deliberate deviation: the
   mockups' own input:focus rule matches BOTH mouse and keyboard clicks, unlike every
   other focus treatment in this codebase, which is consistently :focus-visible
   (keyboard only). Kept the rest of this file's own convention rather than importing
   the mockup's inconsistency - :focus-visible, same outline-ring recipe as
   .bigsearch/.city select/.toolbar .search input. */
.nb .form-card{background:var(--surface);border:1px solid var(--line);border-radius:var(--r-lg);box-shadow:var(--s1);overflow:hidden}
.nb .form-section{padding:25px}
.nb .form-section+.form-section{border-top:1px solid var(--line)}
.nb .fields{display:grid;grid-template-columns:1fr 1fr;gap:15px}
.nb .fields .full{grid-column:1/-1}
.nb .field label{display:block;font-size:11.5px;font-weight:600;margin-bottom:6px}
.nb .field .req{color:var(--acc-d)}
/* :not([type=radio]):not([type=checkbox]) - a bare "input" selector here would also
   catch the radio-pill's real <input type=radio> below and force it to
   width:100%;height:43px, which is wrong independent of focus (a checkbox-sized
   control stretched to a text-input's box). Excluded at the selector instead of
   overriding it back afterward - the earlier .city select fragility
   (tools/focus-outline-check.php) was exactly this shape of "two rules narrowly
   avoid fighting today" problem, not repeating it here on purpose. */
.nb .field input:not([type=radio]):not([type=checkbox]),.nb .field textarea,.nb .field select{width:100%;height:43px;border:1px solid var(--line);border-radius:var(--r-sm);background:var(--surface);color:var(--ink);outline:0;padding:0 12px;font-size:13px;font-family:inherit}
.nb .field textarea{height:104px;padding:11px 12px;resize:vertical}
.nb .field .hint{font-size:11px;color:var(--mut);margin-top:5px}
/* .field .hint (0,3,0) beats the generic .t-err utility (0,2,0) regardless of source
   order - same specificity-over-order trap as .stats-row.cols-3. A validation error
   rendered as class="hint t-err" (organizer profile setup form) silently came out
   var(--mut) grey instead of var(--err) red until this same-or-higher-specificity
   override was added; caught by reading the error text's actual computed color, not
   just glancing at the screenshot. */
.nb .field .hint.t-err{color:var(--err)}
/* x-nb.field-error (block-b-fix-drift.md B.4) always renders this slot, even with no
   error yet, so AJAX pages have real markup to fill in from JS - :empty keeps that
   slot from adding its own 5px margin-top to every field on every page that never
   errors, which is most fields most of the time. */
.nb .field .hint.t-err:empty{display:none}
.nb .field input:not([type=radio]):not([type=checkbox]):focus-visible,.nb .field textarea:focus-visible,.nb .field select:focus-visible{
  outline:2px solid var(--acc);
  outline-offset:1px;
  border-radius:4px;
}
@media(max-width:640px){.nb .fields{grid-template-columns:1fr}}

/* Priority as a real radio group (three states, one always selected) rather than a
   <select> - matches the mockup's own choice for this exact field and reads faster
   for a 3-option field than opening a dropdown. The pill itself carries the visible
   "selected" state (:has(input:checked)); the native input stays real and focusable
   rather than visually hidden, so nearby.css's own global input:focus-visible rule
   (a/button/input, nb.css line 107) covers its ring for free - no reset to fight it. */
.nb .radio-row{display:flex;gap:10px;flex-wrap:wrap}
.nb .radio-pill{display:flex;align-items:center;gap:7px;height:43px;padding:0 16px;border:1px solid var(--line);border-radius:var(--r-pill);font-size:13px;cursor:pointer}
.nb .radio-pill:has(input:checked){border-color:var(--acc);background:var(--acc-w);color:var(--acc-d);font-weight:600}
/* accent-color, not appearance:none+a hand-drawn dot - the comment above already
   settled on keeping the native control real rather than resetting it; accent-color
   recolors what the browser already draws (the dot, the focus outline it contributes
   to) without touching hit-testing/keyboard behaviour at all. This is the fix for
   "blue native radio inside an orange-accent pill" - before this, .radio-pill/.chk
   only ever sized+positioned the native control and left its own rendering (a plain
   OS-blue circle/box) completely untouched. Sized up from the browser's ~13px
   default too - a tap target that small next to a 43px-tall pill read as an
   afterthought, not a checkbox verifying its own state. */
.nb .radio-pill input{width:17px;height:17px;border:0;margin:0;accent-color:var(--acc)}

/* WIZARD STEPS (event-creation flow, 6 real steps) - a real gate, not decoration; see
   templates/basic/organizer/event/partials/wizard_steps.blade.php. Locked future steps
   are plain <span>, never a fake-disabled <a href=#> - nothing here for Tab to land on
   that does nothing, so no focus-visible pairing is needed for the locked state at all. */
.nb .wizard-steps{display:flex;flex-wrap:wrap;gap:8px;margin-bottom:20px}
.nb .wizard-step{display:flex;align-items:center;gap:8px;height:40px;padding:0 14px 0 6px;border:1px solid var(--line);border-radius:var(--r-pill);background:var(--surface);font-size:12.5px;color:var(--mut)}
.nb .wizard-step-no{display:inline-flex;align-items:center;justify-content:center;width:22px;height:22px;border-radius:50%;background:var(--tint);color:var(--mut);font-family:var(--fm);font-size:11px}
.nb .wizard-step.done{color:var(--ink)}
.nb .wizard-step.done .wizard-step-no{background:var(--acc-w);color:var(--acc-d)}
.nb .wizard-step.current{border-color:var(--acc);color:var(--ink);font-weight:600}
.nb .wizard-step.current .wizard-step-no{background:var(--acc);color:var(--ink)}
.nb .wizard-step.locked{color:var(--faint-2);border-style:dashed}
.nb .wizard-step.locked .wizard-step-no{background:transparent;border:1px solid var(--line)}
.nb .wizard-step.locked.current{color:var(--ink);font-weight:600;border-color:var(--acc);border-style:solid}
.nb .wizard-step.locked.current .wizard-step-no{background:var(--acc);color:var(--ink);border:0}
@media(max-width:640px){.nb .wizard-step{font-size:11.5px;padding:0 11px 0 5px}}

/* TIME SLOTS repeater (event creation step 3, no mockup source - see the view's own
   comment). Minimal bordered box per slot, reusing the same --line/--r tokens every
   other card already uses rather than a new visual language. */
.nb .ts-slot{position:relative;border:1px solid var(--line);border-radius:var(--r);padding:16px;margin-bottom:12px}
.nb .ts-slot:last-child{margin-bottom:0}
.nb .ts-slot .ib{position:absolute;top:10px;right:10px;width:28px;height:28px;font-size:15px;line-height:1}
.nb .ts-add{margin-top:4px}

/* GALLERY GRID (event creation step 4) - x-nb.file-upload is single-image only, so
   multiple gallery images with individual removal needed a new minimal tile grid
   rather than a second file-upload instance. Each existing tile is backed by a real
   oldGalleryImages[] hidden input - removing a tile here is a real delete
   (storeGallery diffs whatever's left), not a cosmetic hide. */
.nb .gallery-grid{display:flex;flex-wrap:wrap;gap:10px}
.nb .gallery-tile{position:relative;width:96px;height:96px;border-radius:var(--r-sm);overflow:hidden;border:1px solid var(--line);flex:none}
.nb .gallery-tile img{width:100%;height:100%;object-fit:cover;display:block}
.nb .gallery-tile .ib{position:absolute;top:4px;right:4px;width:24px;height:24px;font-size:13px;line-height:1;background:var(--surface)}
.nb .gallery-add{display:flex;align-items:center;justify-content:center;text-align:center;padding:8px;border:1px dashed var(--acc-b);background:linear-gradient(135deg,var(--tint),var(--surface));cursor:pointer;font-size:10.5px;color:var(--mut);position:relative}
.nb .gallery-add:hover{background:var(--acc-w);border-color:var(--acc)}
.nb .gallery-add input{position:absolute;inset:0;opacity:0;cursor:pointer}
/* Same opacity-swallows-the-outline trap as .upload-box, fixed the same way this
   time from the start rather than rediscovered - the ring goes on the tile itself. */
.nb .gallery-add:has(input:focus-visible){outline:2px solid var(--acc);outline-offset:2px}

/* SPEAKER CARDS (event creation step 5, no mockup source - see the view's own
   comment). Same bordered-box-per-item shape as Time Slots' .ts-slot, for the same
   "no repeater pattern exists elsewhere" reason - kept consistent with that choice
   rather than inventing a second shape for the second no-mockup step. */
.nb .sp-card{position:relative;border:1px solid var(--line);border-radius:var(--r);padding:16px;margin-bottom:12px}
.nb .sp-card:last-child{margin-bottom:0}
.nb .sp-card .sp-remove{position:absolute;top:10px;right:10px;width:28px;height:28px;font-size:15px;line-height:1}
.nb .sp-card-inner{display:flex;gap:16px;align-items:flex-start}
.nb .sp-card-inner .fields{flex:1}
@media(max-width:640px){.nb .sp-card-inner{flex-direction:column}}

/* PAGE HEADER (x-nb.page-header, block-b-fix-drift.md B.2) - .head-row/.head-actions/
   the page-title h1 had genuinely zero CSS anywhere before this; every page's title
   was rendering at the browser's unstated UA default size. First real styling for a
   pattern already live, verbatim, on 21 pages. */
.nb .head-row{display:flex;align-items:flex-end;justify-content:space-between;gap:20px;flex-wrap:wrap;margin-bottom:24px}
.nb .head-row h1{font-size:28px;margin:8px 0 6px}
.nb .head-row p{color:var(--mut);font-size:13.5px;margin:0;max-width:56ch}
.nb .head-actions{display:flex;gap:10px;flex-wrap:wrap}
@media(max-width:640px){
  .nb .head-row{align-items:flex-start}
  .nb .head-row h1{font-size:24px}
  .nb .head-actions{width:100%}
  .nb .head-actions .btn{flex:1}
}

/* AUTH SHELL (Block C - login/register/forgot/reset password, both guards). No
   mockup source anywhere (site-wide-conformance.md: "a card, a form, a button -
   all built. Let the agent assemble those.") - a narrow centered .form-card, sized
   to the form itself rather than the full .wrap shell every sidebar page uses,
   since these pages have no sidebar to sit next to. */
.nb .auth-shell{max-width:420px;margin:56px auto;padding:0 var(--pad)}
.nb .auth-shell .brand{justify-content:center;margin-bottom:28px}
.nb .auth-shell h1{font-size:22px;text-align:center;margin:0 0 6px}
.nb .auth-shell .auth-sub{color:var(--mut);font-size:13px;text-align:center;margin:0 0 4px}
.nb .auth-switch{text-align:center;font-size:13px;color:var(--mut);margin-top:18px}
.nb .auth-switch a{color:var(--acc-d);font-weight:500;border-bottom:1px solid var(--acc-b)}
.nb .auth-switch a:hover{border-color:var(--acc)}
@media(max-width:480px){.nb .auth-shell{margin:32px auto}}

/* "OR" divider between the social-login buttons and the email/password form - CLASS
   3, the old markup was bare Bootstrap-utility text (text-center/mb-4) with no line
   either side, visually disconnected from the nb .form-card it sits inside. A flex
   row with two flex:1 rules either side of the label reads as an actual divider
   rather than a stray line of text between two unrelated blocks. */
.nb .divider{display:flex;align-items:center;gap:12px;margin-bottom:20px;color:var(--mut);font-size:11px;letter-spacing:.04em}
.nb .divider:before,.nb .divider:after{content:"";flex:1;height:1px;background:var(--line)}

/* Plain checkbox row (remember-me, terms agreement). Same minimal-native approach as
   .radio-pill (nearby.css never fully re-skins native checkbox/radio controls, just
   sizes/positions them) - accent-color finishes that pattern rather than replacing
   it, recoloring the browser's own drawn checkbox instead of hand-drawing one. */
.nb .chk{display:flex;align-items:center;gap:8px;font-size:13px;color:var(--ink-2)}
.nb .chk input{width:17px;height:17px;margin:0;accent-color:var(--acc)}

/* Safety net for any native radio/checkbox reached from outside .radio-pill/.chk
   (a form built off this pattern later, or one this sweep missed) - accent-color
   costs nothing to apply broadly and a stray unstyled OS-blue control is exactly
   the CLASS 1 defect this whole file exists to close. */
.nb input[type=radio],.nb input[type=checkbox]{accent-color:var(--acc)}

/* ORGANIZER TILE (x-nb.organizer-card, Block C) - a centered profile card for
   listing grids (following/organizers, the public organizer directory). Reuses
   .avatar's own circle-with-initial treatment at a larger size rather than
   inventing a second avatar style. */
.nb .org-tile{background:var(--surface);border:1px solid var(--line);border-radius:var(--r-lg);padding:22px 18px;text-align:center;display:flex;flex-direction:column;align-items:center;gap:4px}
.nb .org-tile-avatar{display:block;margin-bottom:8px}
.nb .org-tile-avatar img{width:64px;height:64px;border-radius:50%;object-fit:cover;display:block}
.nb .org-tile-avatar .avatar{width:64px;height:64px;font-size:22px}
.nb .org-tile-name{font-size:15px;font-weight:600;color:var(--ink)}
.nb .org-tile-name:hover{color:var(--acc-d)}
.nb .org-tile-meta{color:var(--mut);font-size:12.5px;margin-bottom:10px}
.nb .org-tile .btn{margin-top:2px}
.nb .org-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(200px,1fr));gap:16px}

/* Wrapping grid for .poster (x-nb.event-card) - nearby.css only ever defines
   .rail's horizontal-scroll layout for posters, no wrapping variant. A "liked
   events"/listing page wants to browse many at once, not scroll a shelf. */
.nb .poster-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(230px,1fr));gap:16px}
/* x-nb.toolbar's view-toggle (events.blade.php, Block C - first real use of it
   anywhere in nb). .poster is a single background-image box (nearby.css:417) with
   no separate image element - there's no way to split it into an image column vs
   a text column, so .view-list is a density change only: the same square tile,
   one per row and left-aligned, not a second row-shaped template. */
.nb .poster-grid.view-list{grid-template-columns:1fr}
.nb .poster-grid.view-list .poster{margin-right:auto}

/* BLOG CARD (x-nb.blog-card, Block C) - landscape thumbnail + title/date, the
   real .form-card surface/border/radius vocabulary rather than .poster's
   background-image shape (wrong aspect ratio for a 415x210 blog thumbnail). */
.nb .blog-card{display:block;background:var(--surface);border:1px solid var(--line);border-radius:var(--r-lg);overflow:hidden;color:inherit;transition:.18s}
.nb .blog-card:hover{transform:translateY(-2px);box-shadow:var(--s2)}
.nb .blog-card .nb-img{width:100%;aspect-ratio:415/210}
.nb .blog-card-body{padding:14px 16px}

/* EVENT DETAILS (event_details.blade.php) - the hero cover, the plain photo grid for
   the gallery section, x-nb.ticket-panel's own price-row/stepper, and the mobile
   bottom-bar/sheet that panel renders inside. Nothing here resets a default outline,
   so nearby.css's global a/button/input:focus-visible rule (nb.css:76) already covers
   every new interactive element - no new focus-visible pairing needed anywhere below. */
.nb .ev-cover{width:100%;height:340px;object-fit:cover;border-radius:var(--r-lg);display:block}
@media(max-width:640px){.nb .ev-cover{height:200px}}

/* Plain wrapping photo grid - .poster-grid is shaped for x-nb.event-card's .poster
   (a background-image tile with its own badge/hover chrome); a gallery is just real
   <img> elements, so this is its own small rule rather than forcing that shape on. */
.nb .ev-gallery{display:grid;grid-template-columns:repeat(auto-fill,minmax(140px,1fr));gap:10px}
.nb .ev-gallery img,.nb .ev-gallery .nb-img{width:100%;aspect-ratio:1/1;object-fit:cover;border-radius:var(--r-sm);display:block}

/* Sticky buy panel (desktop only, .dash-split's right column). Sticky was deliberately
   REJECTED elsewhere in this codebase for a sidebar column ("breaks the moment a
   column is taller than the viewport") - safe here specifically because
   x-nb.ticket-panel's content is short and bounded (price, one stepper, one CTA),
   never taller than the viewport the way a full nav sidebar could be. 90px clears
   .topbar's own sticky height plus breathing room. */
.nb .ev-buy-sticky{position:sticky;top:calc(var(--hdr-h, 64px) + 16px)}

/* Mobile bottom bar - the collapsed form of the sticky panel below 760px, matching
   .dash-split's own collapse point so the two-column content+sidebar layout and the
   sidebar-becomes-bottom-bar swap happen at the same width, not two different ones. */
.nb .ev-bottombar{display:none}
.nb .ev-bottombar-spacer{display:none}
@media(max-width:760px){
  .nb .ev-buy-sticky{display:none}
  .nb .ev-bottombar{
    display:flex;align-items:center;justify-content:space-between;gap:16px;
    position:fixed;left:0;right:0;bottom:0;z-index:var(--z-bar);
    padding:12px var(--pad);
    background:var(--surface);border-top:1px solid var(--line);box-shadow:var(--s3);
  }
  /* Keeps the fixed bar from covering the last real content when scrolled to the
     bottom of the page - a plain spacer the bar's own height, mobile only. */
  .nb .ev-bottombar-spacer{display:block;height:84px}
}

/* x-nb.ticket-panel's own markup - the price/badge row, the quantity stepper. Renders
   identically inside .ev-buy-sticky and inside .sheet (the bottom sheet below) -
   these rules apply to both, by design, since it's one component in two containers. */
.nb .tp-price-row{display:flex;align-items:flex-start;justify-content:space-between;gap:12px}
.nb .qty-stepper{display:inline-flex;align-items:center;border:1px solid var(--line);border-radius:var(--r-pill);overflow:hidden}
.nb .qty-btn{width:40px;height:40px;display:grid;place-items:center;background:var(--surface);color:var(--ink-2);font-size:18px;line-height:1;border:0}
.nb .qty-btn:hover{background:var(--line-2)}
.nb .qty-input{width:44px;height:40px;text-align:center;border:0;border-left:1px solid var(--line);border-right:1px solid var(--line);font-size:14px;font-weight:600;-moz-appearance:textfield;background:var(--surface);color:var(--ink)}
.nb .qty-input::-webkit-outer-spin-button,.nb .qty-input::-webkit-inner-spin-button{-webkit-appearance:none;margin:0}

/* Bottom sheet - the mobile container x-nb.ticket-panel's second render sits inside.
   The only modal/drawer primitive anywhere in nb; nothing existing to reuse (checked
   both CSS files - confirmed absent before adding this). Overlay + panel are two
   elements so the panel's own slide transform and the overlay's own fade can run
   independently; .open is toggled by event_details.blade.php's own script. */
.nb .sheet-overlay{position:fixed;inset:0;z-index:var(--z-overlay);background:rgba(18,18,17,.45);opacity:0;visibility:hidden;transition:.2s}
.nb .sheet-overlay.open{opacity:1;visibility:visible}
.nb .sheet{
  position:fixed;left:0;right:0;bottom:0;z-index:var(--z-sheet);
  background:var(--surface);border-radius:var(--r-xl) var(--r-xl) 0 0;box-shadow:var(--s3);
  padding:10px 20px 28px;max-height:80vh;overflow:auto;
  transform:translateY(100%);transition:.24s;
}
.nb .sheet.open{transform:translateY(0)}
.nb .sheet-handle{width:36px;height:4px;border-radius:var(--r-pill);background:var(--line);margin:0 auto 14px}
.nb .sheet-close{position:absolute;top:12px;right:14px}
@media(min-width:761px){.nb .sheet,.nb .sheet-overlay{display:none}}
.nb .blog-card-title{font-size:14.5px;font-weight:600;margin-top:4px;line-height:1.35}

/* INDIAN MOBILE (x-nb.phone-in) - fixed, non-editable +91 prefix joined to the
   10-digit input. India-only: there is no country picker anywhere. */
.nb .phone-in{display:flex;align-items:stretch}
.nb .phone-in__prefix{display:inline-flex;align-items:center;padding:0 12px;border:1px solid var(--line);border-right:0;border-radius:var(--r-sm) 0 0 var(--r-sm);background:var(--line-2);color:var(--ink-2);font-size:13px;font-weight:600;font-variant-numeric:tabular-nums}
.nb .field .phone-in input{border-radius:0 var(--r-sm) var(--r-sm) 0;flex:1;min-width:0}

/* Ticket type picker in the event page booking panel (x-nb.ticket-panel) */
.nb .tp-types { border: 0; padding: 0; margin: 0; display: grid; gap: 8px; }
.nb .tp-types legend { margin-bottom: 8px; }
.nb .tp-type { display: grid; grid-template-columns: auto 1fr auto; gap: 10px; align-items: center; min-height: 48px; padding: 10px 12px; border: 1px solid var(--line); border-radius: var(--r-md, 10px); cursor: pointer; }
.nb .tp-type:has(input:checked) { border-color: var(--ink); background: var(--bg-2, #F3F1EE); }
.nb .tp-type.is-off { opacity: .55; cursor: not-allowed; }
.nb .tp-type__name { font-weight: 600; }
.nb .tp-type__name small { display: block; font-weight: 400; color: var(--mut); }
.nb .tp-type__price { font-weight: 600; white-space: nowrap; }

/* Typographic fallback poster: an event with no cover image shows its name, large,
   on ink - readable, and clearly intentional rather than a broken image. */
.nb .poster--text{background-color:var(--ink)}
.nb .poster--text::after{background:none}
.nb .poster--text .cap .t{font-size:22px;line-height:1.15;letter-spacing:-.03em}

/* active (dark) tab: the count follows the tab text colour */
.nb .tab.active .count, .nb .tab[aria-selected="true"] .count, .nb .tab[aria-current="page"] .count { color: inherit; opacity: .8; }
/* <x-refund-status>: the chip, and "Ref: …" under it when the refund has one */
.nb .refund-status{display:inline-flex;flex-direction:column;align-items:flex-start;gap:3px;vertical-align:middle}
.nb .refund-status__ref{font-size:12px;color:var(--mut);overflow-wrap:anywhere}
/* a long refund label ("Refunded ₹300.00 · UTR 412345678901 · 10 Oct 2026") wraps inside the chip instead of
   widening the page on a phone (flow audit 07-06 / 07-08) - beats the fixed-height chip rules (tk-head, head-actions) */
.nb .refund-status{max-width:100%}
.nb .refund-status > .status-badge, .nb .page-grid > section .refund-status > .status-badge, .nb .page-grid > section .tk-head .refund-status > .status-badge, .nb .page-grid > section .head-actions .refund-status > .status-badge{width:auto;max-width:100%;height:auto;min-height:26px;padding-top:4px;padding-bottom:4px;white-space:normal;overflow-wrap:anywhere;line-height:1.35}

/* Organiser Transactions: titles wrap to two lines (booking ID + event stay visible), full text in the title attribute */
.nb .tx-line .tx-text{min-width:0}
.nb .tx-line .tx-title{font-weight:600;font-size:14px;line-height:1.35;margin-bottom:3px;display:-webkit-box;-webkit-line-clamp:2;-webkit-box-orient:vertical;overflow:hidden;overflow-wrap:anywhere}
.nb .tx-row .mrow__name{white-space:normal;display:-webkit-box;-webkit-line-clamp:2;-webkit-box-orient:vertical;overflow-wrap:anywhere}
.nb .tx-line .tx-sub{white-space:normal;overflow-wrap:anywhere}
.nb .tx-row .mrow__sub{white-space:normal;overflow-wrap:anywhere}
