fix(deeplink): event-path delivery also clears pendingFocusProvider stash

`dispatchFocusConnector` writes the stash before firing the event so the
drain-on-mount path covers a SettingsView that hadn't mounted yet. But
when SettingsView IS mounted, the event handler ran without clearing
the stash — the next mount (tab navigation back to Settings) then
re-drained it and fired a spurious scroll/flash on the previously
focused panel (Greptile P1 follow-up after the timing-race fix).

Clear the stash inside the event handler too, so whichever delivery
path lands first consumes it.

Author: 2-A-M

packages/app-core/src/components/pages/SettingsView.tsx

@@ -767,7 +767,13 @@ export function SettingsView({
 
     function handle(event: Event) {
       const detail = (event as CustomEvent<SettingsFocusConnectorDetail>).detail;
-      if (detail?.provider) focusProvider(detail.provider);
+      if (!detail?.provider) return;
+      // Consume the stash here too — the dispatcher always writes it before
+      // firing the event, but if we're already mounted the event path wins
+      // and the stash would otherwise persist and re-fire on the next mount
+      // (e.g. tab navigation) as a spurious scroll/flash.
+      consumePendingFocusProvider();
+      focusProvider(detail.provider);
     }
 
     // Drain any pending provider stashed before this mount.