/* xp-chrome.css — grid-side chrome for the experimental search console.
   Every rule is scoped under html.xp, so this sheet is completely inert with the flag off.

   ⚰ THIS FILE IS DOWN TO ONE RULE, AND THAT IS THE POINT (forage-l1e, 2026-08-21).
   Its other half — `.xpc-pill`, a sticky `<query> · N results ×` bar under the masthead, plus
   the rule that suppressed `.resultbar`'s count because "the count moved into the pill" — is
   DELETED along with `web/xp-chrome.js`, which drew it. The pill was a SECOND SEARCH BAR
   sitting directly above the phase-3 pill box, so the grid asked the same question twice and
   printed the answer three times (the pill, `.sqline`, and the box's own pills). The owner
   photographed it on his phone on the day phase 3 went live.
   ⛔ DO NOT BRING A QUERY PILL BACK. There is one box (`.sqbox`), one printed query
   (`.sqline`, the teaching line), one count (`.resultbar`, directly above the grid it counts)
   and one clear (`#sqclear`, in the control row). The FAB console is untouched and is not a
   second bar — it is an overlay you open, not chrome stacked on the grid.
   ⚑ The count is the capability that came back rather than being dropped: while the pill
   existed, `html.xp.xp-pill-on .resultbar > span:first-child { display:none }` meant the
   result count existed ONLY inside the pill, so deleting the pill without deleting that rule
   would have taken "22 results" off the screen entirely.

   ⚠ AND THE FILE STAYS. It is the eleventh stylesheet in `app.css`'s cascade order only in the
   sense that it is linked on `/`; the rule below is live, `xpEnabled()` defaults ON, and
   deleting the sheet would silently restore two wrapped rows of query-syntax tabs above the
   first meme. See web/app-search.css for the surface this defers to. */

/* ═══ THE IN-PAGE SEARCH BAR IS BACK — AND HIDING IT WAS THE BUG THAT MADE PHASE 3 INVISIBLE ═══
   🐛 forage-n0k, 2026-08-21, found by DRIVING THE REAL APP: `xpEnabled()` has defaulted ON since
   the experimental UX shipped, so a block here was hiding `.searchwrap` for every member on every
   visit. Phase 3 built the pill box, the canonical teaching line, the narrow button and the
   quick sort chip INTO that wrapper, exactly as owner ruling H directs — and every one of them
   would have shipped inside a 1px clipped box that nobody can see.

   ⚖ THE RULING THAT HID IT IS SERVED BY UNHIDING IT, NOT REVERSED. The reason was never "the bar
   is unwanted": it was ~600px of pre-content chrome on a 2285px phone screen — masthead + bar +
   TWO WRAPPED ROWS of query-syntax tabs + the count + the sort bar. Phase 3 deleted most of that
   budget outright, and forage-l1e has since deleted the pill too. What stands now is the bar
   (~44px), a 12px token line that COLLAPSES TO NOTHING when the query is empty, and one 34px
   control row — about 90px, and it is the search experience rather than an approach to it.
   ⛔ DO NOT RE-HIDE THIS TO RECLAIM HEIGHT. If the chrome grows again, cut the chrome — a
   control the member cannot see is not chrome, it is a missing feature, and this file has now
   shipped that mistake once.

   ⚠ THE FORM WAS NEVER `display:none` AND STILL MUST NOT BE. The console commits a search by
   setting `#q.value` and calling `requestSubmit()`, which reuses index.html's own search path;
   a hidden input also cannot be focused. Both callers still work — page-index.js tells a button
   press from a programmatic submit by `event.submitter` — and the FAB, the console, its saved
   and recent searches are all untouched. */

/* ═══ THE QUERY-SYNTAX TABS STAY OFF THE GRID ═══
   Two wrapped rows of group names above the first meme, teaching a grammar the box now writes
   into itself on every tap. `.sqline` is the replacement and it costs 12px when it costs
   anything. The console keeps its own help panel for anyone who wants the full table. */
html.xp .searchwrap .qhelp { display: none; }