Fit cascade lab

The order. Things the reader did not choose go first, things they opened go last: the tab bar's spacing, then where its icons sit, then the minimap (drawn automatically, no switch of its own), then Contents, then Tags. The panel the reader has just opened stays exempt, as now (fitPanels's exempt). Today's order is Contents, Tags, minimap (SidebarStore.ts, decided 20 Sep 2026); this lab proposes moving the minimap to the front.

What the panels protect, by surface.

• Browser: the centre keeps the tab bar on one row. Its floor is the tab bar's narrowest one-row width (condensed, icons in the header) plus the centre's 40px of padding, or the quote card's 368px if that is wider: 555px in English, 600 in French, 583 in German. That number moves with the language and with the lenses a project has (Screens appears only when a project has screens), so the product has to measure it, as this page does, not hold a constant.
• Mac: no tab bar (the lens rail is native), so the floor stays the quote card, 368px. The projects column is the native side's move, and it already collapses on window resize when the report would fall below the width the web side asks for. If the minimap is to go first, that request must stop counting the minimap (wantedWidth counts it today), or the projects column folds away to save an 80px overview. With that change the Mac order is: minimap, projects column, Contents, Tags.

The two surfaces diverge only in their floor and in the native column. The cascade itself (which panel goes when) is one function, fitPanels, on both; the browser passes a wider floor. That keeps the logic the Mac relies on (the exemption, the auto-collapse handshake, the 700pt window minimum) intact.

One way only. The steps are one ordered list, and the page takes the shortest run of them that fits. A step therefore stays taken while any later one is in effect: closing Contents does not bring the icons back down into the tab bar, and folding the projects column does not bring the minimap back. A first version computed each step on its own, and the icons went up, down and up again as the window narrowed. fitPanels already works this way for the panels; the tab bar's two steps would join its list.

What breaks, and where

• Browser: with everything closed, the tabs stay on one row down to the window width in the table's "tabs wrap" row (675px in English, 720 French, 703 German). Below that they wrap (the shipped behaviour), and the quotes squeeze below 488px, where the centre falls under one quote card. The window cannot get narrower than that in practice without it being a phone, which is a different layout.
• Mac: the window's minimum is 700pt. At that width the projects column has folded and Contents has closed, and Tags still fits (it needs 648px). The quotes never squeeze on the Mac, and the cascade starts at the same window width as today (1188px): the minimap goes there instead of the projects column, which now holds on to 1108px.

Not settled here

• Whether the tab bar should ever close a sidebar. The lab gives the tab bar priority over Contents and Tags (they close before the tabs wrap). The alternative is to let the tabs wrap first and close panels only for the quote floor; the "tabs wrap" and "Contents closes" rows would then swap places.
• The exemption: opening Contents on a narrow window keeps it open and closes Tags instead, as now. Not drawn.

Strings

All shipped: nav.*, header.researchReport, quotes.sections, quotes.themes, quotes.groupBy.*, tags.tags. Project names, counts and tags are fixtures.