/* ============================================================
   prolancer-bridge.css — shell shims only.
   Every page now renders the Prolancer skin (the shells default
   data-skin="prolancer"), so the old clientflow re-assertions for
   un-migrated content are gone. What remains bridges two shell
   details until they move into prolancer.css / the templates.
   Load order on every shell page: app-components.css -> prolancer.css -> this.
   ============================================================ */

/* ── Shell shims (Prolancer chrome) ──────────────────────────────
   Small bridges for the re-skinned shell, not content. Move into the
   migrated templates/prolancer.css over later phases; delete with this
   file in Phase 11.

   Breadcrumbs: prolancer styles the current crumb as `.cur`, but ~30
   child templates still emit `{% block breadcrumbs %}...<span class="current">`.
   Until those templates are swept to `.cur`, give `.current` the same
   treatment so the active page stays highlighted. */
.topbar .crumbs .current {
  color: var(--text-primary);
  font-weight: 500;
}

/* Mobile sidebar: prolancer hides .sidebar at <=1024px (display:none), which
   defeats clientflow's transform-based slide-in. When Alpine adds .mobile-open,
   show it as a fixed full-height overlay. (Transitional; revisit when the shell
   gets a dedicated responsive pass.) */
@media (max-width: 1024px) {
  .sidebar.mobile-open {
    display: flex !important;
    position: fixed;
    left: 0;
    top: 0;
    height: 100vh;
    z-index: var(--z-sidebar, 200);
    transform: translateX(0);
  }
}