/* ════════════════════════════════════════════════════
   apps/signals-search.css — the Signals search pane (AB#13977)
   ════════════════════════════════════════════════════
   One rule, and that is the point: the page itself is the shared search control, whose own
   sheet is css/controls/search-page.css under the `app-search-*` prefix. What belongs here is
   only the PANE — the box the control is hung in — because Signals has no content slot and
   every surface is a peer of #signal-home that `applySignalsView` shows or hides.

   Its own file rather than more lines in signals.css, which is far past the 600-line cap, and
   beside signals-all.css whose pane rule this mirrors exactly. If the two ever need to differ,
   that difference is a decision worth seeing in a diff. */

/* ── The pane: a peer of #signal-home, #main-content, #signal-all, #signal-notifications and
   #signal-trash. `applySignalsView` in signals-view.js is the only thing that shows it, which is why there
   is no display rule here — the inline `display:none` in templates.js is the initial state and
   signals-view.js owns every change to it. ── */
.signal-search {
    flex: 1;
    min-width: 0;
    min-height: 0;
    display: flex;
    flex-direction: column;
    overflow: hidden;
}
