/* ============================================================
   The HTML `hidden` attribute, made to actually hide things.
   ------------------------------------------------------------
   `hidden` is only `display:none` in the UA stylesheet, and
   Tailwind's preflight restates it as

       [hidden]:where(:not([hidden="until-found"])){display:none}

   Both land at specificity (0,1,0). A plain class selector such as
   `.dash-concierge{display:flex}` is ALSO (0,1,0), so the tie is
   broken by source order, and author CSS almost always comes
   later. The result: an element carrying `hidden` still renders.

   That is not theoretical. On the tenant portal home the concierge
   card is `<div class="dash-concierge" hidden>` and the JS only
   unhides it once /api/v1/renter/home-brief returns a summary. When
   the brief has no summary (a brand new tenant, or an AI timeout)
   the attribute stays set, `.dash-concierge{display:flex}` wins
   anyway, and the tenant gets an empty branded card. Three
   templates had already grown their own local
   `.thing[hidden]{display:none}` patch for the same reason.

   `!important` is required, not stylistic: without it this rule
   just joins the same (0,1,0) source-order race it is meant to
   settle. The `:not([hidden="until-found"])` guard mirrors
   preflight so browser find-in-page can still reveal collapsed
   content.

   Loaded from every shell head: public base.html, dashboard_base,
   tenant_base, vendor_base, owner_base, admin_base.
   ============================================================ */

[hidden]:not([hidden="until-found"]) {
  display: none !important;
}