Month picker — page two

Rendered evidence for #6775 (Direction A, decision b88318608). The whole deliverable is “this control should stop reading as a card inside a card”, so the pixels are the claim — a diff cannot show it.

Server-rendered against the branch’s own dev-server stylesheet · 2026-09-02

Page two of the month-range popover: a header row with a back chevron, two endpoint menu rows, and the year column plus month grid laid directly on the popover

What to check against the complaint. There is no folder tab and no enclosing panel — the only structure below the header is hairlines, which is ordinary menu grammar.

From / To are menu rows, in the idiom of the quick ranges one page back: marker slot, label, right-aligned value. The active one carries a filled dot and the accent tone, so which endpoint your next click sets is legible without a silhouette.
The picker sits directly on the popover — no border, no fill, no radius. The year column’s own right edge is the one vertical rule, which is what says that half scrolls.
The grid has the popover’s full width rather than a panel’s inset, so the cells are comfortable instead of cramped.
The range still reads as a shape: Apr and Aug filled, May–Jul tinted between them, Oct–Dec disabled because a month that has not started has no data to range over.
Draft-only is intact — the footer’s Apply is still the only commit path, and Back discards.