/* Generated by scripts/build_help_prototypes.py (AR-047). Do not hand-edit.
   Stakeholder and customer view modes for the whole 26-page prototype set.

   Walkthrough finding FR-07: the prototype carries furniture that exists so a
   stakeholder can read the build state, and on 23 of the 26 pages it is the
   loudest content on the page. Correct for Ivo, wrong for anyone being shown
   what a customer meets. The list below is the AR-041 section 6 exclusion list
   plus the internal source notes that section 6 covers under "copy".

   Customer view only hides. It never adds, rewrites, or replaces copy, so what
   remains is exactly what the page gives a customer today, including where that
   is very little. Nothing is invented to fill the gap.

   Stakeholder is the default. `_shared/help-view.js` sets data-help-view on the
   root element before first paint, so neither mode flashes the other.

   The preview server's stubs for routes outside the Help Hub carry
   `body.preview-shell` and are exempt: they are scaffolding for live pages this
   project does not build, so they have no customer view to show. */

:root[data-help-view="customer"] body:not(.preview-shell) :is(
  .proto-only,       /* explicit hooks: state suffixes, chips, outline block, internal notes */
  .review-bar,       /* generated pages and the two written pages */
  .prototype-bar,    /* hub */
  .prototype-status, /* hub, the line under the search box */
  .review-panel,     /* written pages, "Review state:" */
  .rationale-wrap,   /* the 12 eye controls, AR-032 */
  .chips,            /* build ID, wave date, route, STDC, owner */
  .gate,             /* "What is missing before this page can be written" */
  .route-note,       /* names AR-025 on the two shop pages */
  .state,            /* "Structure only" / "Draft written" in the browse lists */
  .state-chip,       /* the same, in search result rows */
  #review-notes      /* written pages, "Reviewer notes" */
) { display: none !important; }

/* The control itself. Prototype furniture in both modes: it is deliberately
   visible in customer view so no screenshot can be mistaken for production. */
.view-toggle {
  position: fixed;
  right: 18px;
  bottom: 18px;
  z-index: 999;
  display: flex;
  align-items: center;
  gap: 6px;
  padding: 6px 8px 6px 13px;
  background: #0d1015;
  border: 1px solid #3b4552;
  border-radius: 999px;
  box-shadow: 0 12px 34px rgba(0, 0, 0, 0.5);
  color: #aeb8c4;
  font: 500 12px/1.4 system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
}
.view-toggle-label { font-size: 10.5px; letter-spacing: 0.08em; text-transform: uppercase; }
.view-toggle button {
  padding: 5px 11px;
  border: 1px solid transparent;
  border-radius: 999px;
  background: transparent;
  color: #aeb8c4;
  font: inherit;
  cursor: pointer;
}
.view-toggle button:hover { color: #ffffff; }
.view-toggle button[aria-pressed="true"] { background: #27313c; border-color: #4d5b6a; color: #ffffff; }
.view-toggle button:focus-visible { outline: 3px solid #8ee6c1; outline-offset: 2px; }

@media (max-width: 560px) {
  .view-toggle { right: 10px; bottom: 10px; padding: 5px 6px 5px 10px; }
  .view-toggle-label { display: none; }
}
@media print { .view-toggle { display: none; } }