/* ==========================================================================
   Cockpits · audience branching (page-level contract)
   ==========================================================================
   This file owns exactly one thing, and it is the reason it is not filed under
   a section: which sections of the page are shown. Every showcase section
   declares the branch it belongs to,

     data-cockpit-branch="director"   pilotage + skills + market
     data-cockpit-branch="user"       the rep's own cockpit

   and the script writes the reader's choice on the page's <main>. Presentation
   of the control itself belongs to the section that renders it
   (sections/AudienceSection/AudienceSection.css); nothing here styles it, so
   the two files can never fight over the same declaration.

   Without JS the attribute never appears and NOTHING is hidden: the reader gets
   both branches stacked, which is complete rather than broken — the same no-JS
   contract as the rest of the family.
   ========================================================================== */

[data-cockpit-audience='director'] [data-cockpit-branch='user'],
[data-cockpit-audience='user'] [data-cockpit-branch='director'] {
  display: none;
}