The `activeCount` badge only counts advanced filters (severity, service_tier, etc. plus date filters) but excludes the status filter. However, the "Clear all filters" button uses `search: {}` which clears ALL URL params including `status`. This creates a UX inconsistency: if a user is viewing "Closed" incidents with severity=P0, the badge shows "1" but clicking "Clear all filters" also resets the status view from "Closed" to "Active" (the default). Users may not expect their status selection to be reset when the badge doesn't indicate it as an active filter.

The useEffect on line 83-94 that handles the Escape key listener includes `close` in its dependency array. However, `close` is created with `useCallback` which includes `onClose` in its dependency array (line 68). If `onClose` changes (e.g., a new callback is passed), `close` will be recreated, causing this useEffect to re-register the event listener on every render where `onClose` changes. This could lead to memory leaks or multiple handlers if the parent component doesn't memoize `onClose`.