Feature picker: "N more" row looks expandable but only selects, and the confirm count reads as "31 things to do"

What happened

On the "Select the PostHog areas your agent can reach" step (GroupedPickerMenu, used by the MCP feature picker), the list is taller than the viewport so it renders a bare ↓ N more row underneath the options.

Two problems reported from a real run:

1. The ↓ N more row reads like an actionable "show more" control, but it isn't one. There is no hint about how to reveal the hidden entries, so the natural move is to press space on it — and space is bound to "toggle selection", so it silently toggles the focused option instead of expanding anything. PickerMenu already appends [N] for next page / [P] for previous page to the same indicators; GroupedPickerMenu has no equivalent hint and no paging keys at all.

2. The confirm button count reads like a count of actions the wizard is about to take. With everything selected the button says Confirm (31), which invited the reading "this is going to go off and do 31 things" and caused real hesitation before confirming. The full picture only appeared after confirming, following a noticeable wait — so the reveal happened at the point where it was no longer useful for deciding.

Why it matters

This is the step where the user grants the agent its scope. Hesitating here, or accidentally toggling an option while trying to see the rest of the list, both lead to installing the wrong set of areas.

Suggested fix

• Make the ↑/↓ N more rows in GroupedPickerMenu self-describing scroll affordances rather than something that looks tappable, and advertise the keys that move through them in the hints bar (mirroring what PickerMenu already does).
• Give the confirm count a noun so it reads as scope, not as a task queue — e.g. Confirm (31 areas).

Context: Slack thread

Start with the GroupedPickerMenu used by the MCP feature picker, then compare its overflow indicators and hints with PickerMenu's paging behavior. Make the ↑/↓ rows explain how to move through hidden entries and ensure the hints advertise those keys; update the confirm label so the selected count is described as areas. Done means the overflow affordance is unambiguous, navigation does not toggle options, and the count reads as scope.