/*
 * One call to action per tab — and it is the voice.
 *
 * WHY
 * one-orange.css made the voice pill the only *orange* thing. That fixed the
 * colour clash but not the underlying problem: the tabs still offered several
 * competing things to press. Measured live at phone width after that change:
 *
 *   Reels 1 · Book 2 · ScanSquad 3 · Partner 3 · Profile 5
 *
 * Profile alone asked you to log in, verify your ID, continue, and talk. The
 * product's premise is that you say what you want and it happens, so every extra
 * button is a second answer to a question that should only have one.
 *
 * THE RULE
 * Each tab surfaces exactly one call to action: the Talk pill. Everything else
 * that asked to be pressed is removed from the surface.
 *
 * WHAT IS DELIBERATELY KEPT
 *   - Navigation is not a call to action. The bottom tab bar and the Profile
 *     "Back to More" link stay: removing the way out of a screen strands people.
 *   - Information stays. The price summary and the partner's gym name remain
 *     visible; the gym name simply stops being tappable, so it informs without
 *     competing.
 *   - The Talk panel keeps its "Type instead" option. This is the important one:
 *     a tab with no tap buttons would be a dead end for anyone whose microphone
 *     is blocked, unsupported, or who simply cannot speak right now. One CTA on
 *     the surface, never a dead end underneath.
 *
 * REVERSIBILITY
 * Everything here is display:none on a handful of ids, in one file, loaded last.
 * Deleting a rule brings a button back exactly as it was; nothing is unwired.
 * Note that #sg-continue-banner carries the *purchase* action on Book, so this
 * file is where booking-by-tap went. That was an explicit product decision, and
 * it is one line to undo.
 */

/* ─── The bottom bar: "Book this gym", "Continue", "Ask AI …" ───────────────
   One bar, three different second-best answers depending on the tab. */
#sg-continue-banner {
  display: none !important;
}

/* ─── Profile: the secondary prompts ────────────────────────────────────────
   "Get ID verified" and the orange "Log In" button. Both are things the voice
   can start on request, and neither needs to shout on arrival. The button has
   no id or class, so it is matched by the brand orange it paints inline. */
#sg-id-row,
button[style*="background:#FF6D00"],
button[style*="background: #FF6D00"] {
  display: none !important;
}

/* ─── ScanSquad: "Start Earning" and the affiliate-link chip ────────────────
   Both are reachable by saying so; the chip in particular was a second primary
   sitting in the header, above the fold, before you had done anything. */
#join-btn,
#sg-aff-continue-btn,
.affiliate-btn {
  display: none !important;
}

/* ─── Partner: the gym name stays, but stops being a button ─────────────────
   Hiding it would remove the one piece of information telling a partner which
   gym they are looking at. Keeping it inert preserves that while removing the
   invitation to press it — "change my gym address" is a sentence, not a tap. */
#partner-name-display {
  pointer-events: none !important;
  cursor: default !important;
}

/* ─── The one that stays ────────────────────────────────────────────────────
   Nothing here. Stated on purpose.

   This block used to force the pills visible with `display:inline-flex`, to make
   it obvious which element survives. That was a mistake and it shipped: in the
   SPA all five personalities are loaded, each builds its own pill, and
   chat-agent.js hides the four that do not belong to the current tab. Forcing
   display overrode that and put five "Talk" buttons on Book, Partner and
   Profile at once — the exact opposite of one call to action.

   The pill does not need a rule to survive. It survives because this file never
   hides it. Do not "helpfully" add one back. */

/* ─── The four the earlier passes missed, all on Profile ────────────────────
   Reported from the live app and then confirmed in source:

     "Get Your QR Pass →"          #sg-qr-pass-cta    app.ctr576.js
     "I already have an account"   #sg-login-alt      app.ctr576.js
     "Join ScanSquad → 25% …"      #sg-bottom-popup   app.ctr576.js
     "See how it works →"          #sg-how-it-works   sg-scansquad.js

   None of them had an id, so there was nothing to select; the ids above were
   added alongside this rule for exactly that reason.

   Why every earlier audit missed them, including an automated one: they sit
   below the fold, or arrive on a timer after first paint. An audit that only
   inspects the viewport shortly after load reports the page as clean. Anything
   measuring "one CTA per tab" has to scroll the full page and has to wait —
   tools/brand-audit.js now does both.

   Note "Get Your QR Pass" paints itself with a *gradient*
   (linear-gradient(135deg,#FF6D00,#ff8533)), so the existing
   button[style*="background:#FF6D00"] rule above never matched it. A flat
   colour was demoted and the gradient beside it was not.

   All four are removed as buttons, not as features: signing in, joining
   ScanSquad and fetching a QR pass are all things the voice agent already
   does. You get them by saying so. */
#sg-qr-pass-cta,
#sg-login-alt,
#sg-how-it-works,
#sg-bottom-popup {
  display: none !important;
}