Keep search results and nested-level keys in sync on mobile

[gohabereg]

Stacked on #40 — review that one first, this diff only makes sense on top of it.

Two gaps I reported while reviewing #40 and deliberately left out of it, since that branch is already large enough that the reviewer asked for it to be split.

Search results went stale when the item list changed

addItem() / removeItemByName() updated the searchable set but never re-ran the query, so an item added while a query was typed joined the results whether it matched or not, and the announced count went with it. Note this predates #40 — the old addItem appended the element directly and was equally unfiltered.

SearchInput.reapplyQuery() re-runs whatever is already in the field, and PopoverDesktop calls it after either mutation.

PopoverMobile ignored children.isFlippable

Mobile renders nested levels into the same panel rather than into a popover of their own, so the Flipper navigating the root list carried on claiming the arrows and Enter after drilling in. An item built around a text input — the link-tool URL field pattern — could never receive them: preventDefault() on the arrows moved focus off the field, and Enter clicked whatever the cursor was on instead of submitting.

PopoverDesktop has honoured this since before #40, by passing flippable: item.isChildrenFlippable to the nested popover it creates. Mobile had no keyboard navigation at all until #40, so nothing regressed — the flag simply had nowhere to apply. It now travels with the level through PopoverStatesHistory, and a level that opts out leaves the Flipper deactivated, its items becoming individual stops of the panel's Tab trap instead.

Tests

184 passing across chromium and webkit. Two new, plus a mobile-nested-input fixture.

Both were checked against the parent branch's source to confirm they fail without the fix — the isFlippable one initially passed regardless, because the nested level had a single item and the Flipper's arrow simply wrapped back to it; the fixture now has a second stop so the focus has somewhere to be stolen to.

🤖 Generated with Claude Code

[Reversean]

The root state is pushed without isFlippable, and isLevelFlippable is hardcoded to true at declaration instead of reading params.flippable !== false. For instances created with flippable: false, isLevelFlippable remains true on mount and after hide() calls history.reset().

Suggested change

	this.history.push({ items: params.items });
	this.isLevelFlippable = params.flippable !== false;
	this.history.push({ items: params.items, isFlippable: this.isLevelFlippable });

[Reversean]

updateItemsAndHeader is called before history.push. If onChildrenOpen calls close() synchronously (or any re-entrant event triggers during rendering), close() calls history.pop(), which pops and deletes the root state because the child state was not pushed yet.

Suggested change

	this.updateItemsAndHeader(item.children, item.title, item.isChildrenFlippable);
	this.history.push({
	title: item.title,
	items: item.children,
	isFlippable: item.isChildrenFlippable,
	});
	this.updateItemsAndHeader(item.children, item.title, item.isChildrenFlippable);

[Reversean]

Focusing any element inside a non-flippable level (isFlippable: false) triggers syncFlipperCursor, which calls flipper.activate() and accidentally turns keyboard navigation back on. isFlipperCursorSyncEnabled should return false whenever isLevelFlippable is false.

Suggested change

	private isLevelFlippable = true;
	protected override get isFlipperCursorSyncEnabled(): boolean {
	return this.isLevelFlippable && super.isFlipperCursorSyncEnabled;
	}

[Reversean]

If an item is added or removed while an item in the search results is actively focused, reapplyQuery() runs onSearch, which deactivates and reactivates the flipper without restoring the cursor. This blurs the active item and drops focus out of the menu to document.body.