RevShift × Jessar · render before commit · NOT deployed to the theme

Header, on one row.

Logo · inline nav (mega intact) · search-icon + trade actions — all in a single 66px row. Hover Kitchen & Dining to see the mega menu still drop full-width.
● Design render only — nothing pushed to theme 190048960834. Test-theme deploy after the meeting.
Family-run in Québec — supplying Canadian retailers since 1996
ONE ROW · 66px
What moved The nav row is gone; its links now sit inline in the top row. The mega menu is untouched — same snippet, same triggers.
Search The big center search bar collapses to an icon (click to expand) — that's what frees the center for the nav.
Sticky & mobile Sticky-on-always is preserved. Mobile is unchanged: hamburger → the existing drawer menu (already one-row on phones).
Today (for contrast) — two stacked rows:
Row 1 ·   [hamburger]   JESSAR   [━━━━━ big search bar ━━━━━]   Where to Buy · Become a Dealer
Row 2 ·         Kitchen & Dining ▾   Lighting ▾   Electrical ▾   Home & Bath ▾         (this whole row disappears)

How it's built (staged for the test theme)

  1. In header.liquid, move the header__navigation (the desktop-menu render) out of the header__bottom row and into header__top, as the center grid column — then delete the now-empty header__bottom.
  2. Retune the .header__top grid from [logo · search · icons] to [logo auto · nav 1fr · actions auto]; set the section's header_layout to logo-left.
  3. Switch the predictive search from the always-open center bar to the theme's icon-toggle mode (Hyper already ships the expandable search — it's a class/flag, not new code) so the center is free for the nav.
  4. Point the mega panel's inset-block-start at the single-row header height (one value) so it drops just below the 66px row instead of below the old two-row stack.
  5. Fold the two RS header__top / header__bottom padding blocks into one; keep the sticky + collapse-on-scroll wiring as-is.
Why the mega survives: .mega-menu is position:absolute; width:100%; left:0 anchored to .header (the position:relative ancestor) — not to the nav row. Moving the trigger between rows doesn't change where the panel renders. Verified in theme.css. This is exactly why one-row is low-risk.