/*
 * engagement-gating.css — hide collector-grade maintenance UI from non-collector
 * tiers, default-safe and flash-free.
 *
 * The maintenance trio (cellar-status badge, needs-review banner, organise CTA)
 * is hidden for EVERY engagement state except `established`. Because the rule is
 * `body:not([data-engagement="established"])`, the trio is hidden in the initial
 * HTML before any JS runs (the body carries no data-engagement yet) — there is
 * no show-then-hide race even with deferred module scripts. `maintenanceVisibility.js`
 * only ever sets `data-engagement="established"` to REVEAL them.
 *
 * Whole-element hiding only — this file never rewords business copy. An
 * established user sees the trio exactly as before.
 *
 * Plan: docs/plans/intent-first-ia.md §2.2 / §7.
 */

body:not([data-engagement="established"]) #cellar-status-badge,
body:not([data-engagement="established"]) #needs-review-mount,
body:not([data-engagement="established"]) #organize-cta {
  display: none;
}

/*
 * Cellar-hub segment gating (cellar-hub-tier-adaptive-nav, D3/§4).
 * A hub sub-tab carrying `data-min-tier="established"` (today: Analysis, the
 * collector-coded segment) is hidden for every tier below `established`. The
 * attribute mirrors navConfig SEGMENT_MIN_TIER. Adding another segment gated at
 * the SAME `established` threshold is one markup attribute — no new CSS. A NEW
 * threshold (e.g. a `casual`-gated segment) needs its own paired rule below,
 * because CSS cannot compare tier ranks; the selector is per-threshold by
 * necessity, one rule per distinct min-tier. Attribute-keyed (not id-keyed) so
 * same-threshold segments share the rule. `display:none` removes the tab from
 * the keyboard/tab order too (a11y). Default-safe + flash-free: before JS sets
 * data-engagement, the body carries none, so the gated segment is hidden in the
 * initial HTML.
 */
body:not([data-engagement="established"]) #sub-tabs-cellar .sub-tab[data-min-tier="established"] {
  display: none;
}