nitpick, non-blocking: The reason size was given with style is for the actual size and the size used in calculations not to be out of sync. Now, the sync between size-8 and SEE_MORE_WIDTH_PX has to be managed manually.

issue, non-blocking: Now this section can shrink to nothing.

issue, non-blocking: This is duplicative state (between visitor-graph and this component), which causes us to need syncing code. I think a better split would be to have

GraphIntervalContext - solely responsible for calculating available intervals and the current one, and providing the means to change the current one

ImportsIncludedContext - same as above, just for imports, may itself depend on GraphIntervalContext

and to use the exposed context state in the components where they're needed, when fetching the graph and in the new triple dot menu.

suggestion, non-blocking: Let's also test that it handles timezones in the date string (I've not actually seen 2024-01-13T00:00:00, always something like

        "date_range": [
            "2026-01-19T00:00:00+00:00",
            "2026-04-19T23:59:59+00:00"
        ],

suggestion, non-blocking: If the comment about the function is exactly above the function, IDEs include it when hovering at a call site.

/** Does something complex, explanation */ 
const f = () => {
//  ..
}

issue, blocking: This works for Today vs Previous period, but it is incorrect when comparing Today vs Custom Period (pick yesterday from comparison calendar). The comparison query is made for the whole day, so we'd need to calculate and show comparisonTimeRange here.

question, non-blocking: Why did we get rid of the color asserts? I think they matter because bounce rate down being rendered as green is important. Up/down direction is already tested with toHaveTextContent('↑ 1%'). (The arrow icons are mocked with a particular unicode character)

question, non-blocking: why padding left with !important? I don't see padding left previously declared in popover.toggleButton.classNames.rounded, just on the prev line.

question, non-blocking: Does the switcher not need same left & right padding? E.g. !px-1.5

issue, non-blocking: These tests are running on a constant viewport (1024px). "See N more" depends on that, filter pills style, and other top bar items.

Because the UI changed, the conditions to wrap to to "See N more" changed, so I can see why you added another filter. However, the comment is misleading and there's some missing asserts now.

In these tests, I think we should definitively check which filters of the added filters are visible without clicking "See more", that "See more" has the correct label, and that all the rest are visible after clicking "See more".