openSavedQuery switches surfaces before resolving the id, and stays silent when it fails

[BorisTyshkevich]

app.openSavedQuery(queryId) switches to the Query surface before it knows the
query exists, and reports nothing when it does not:

// src/ui/app.ts (openSavedQuery)
const query = app.state.savedQueries.find((saved) => saved.id === queryId);
app.showQuerySurface();                     // <- unconditional
if (query) { loadIntoNewTab(app, { ...query }); toEditorOnMobile(); }

So an unresolved id yanks the user off whatever surface they were on — pushing a
history entry — opens no tab, and shows no diagnostic. It reads as a dead click
that also loses your place.

Why deferred

Pre-existing behaviour, unrelated to #426's scope (a read-only tree). Surfaced by a
review of PR for #426, where it was the tail of a now-fixed problem: a deferred
tree single-click could fire after a workspace switch and reach this path with an id
the new workspace does not contain. That trigger is gone — the tree now cancels
pending clicks on a workspace switch and on disposal — so this is no longer
reachable that way, and fixing the primitive itself belongs in its own change.

Every current caller resolves the id first (the tree only emits open-query for a
query it resolved; saved-history.ts clicks a row it just rendered), which is why
it has not bitten in practice.

Suggested fix

Resolve first: on a miss, report through the shared diagnostic path
(flashToast) and change no surface. Worth checking whether any caller depends on
the current "always switch" behaviour before tightening it.

Acceptance

• openSavedQuery with an id absent from state.savedQueries leaves
  app.mainSurface and the route untouched and surfaces one diagnostic.
• A resolving id behaves exactly as today.

[BorisTyshkevich]

Absorbed into #429 and closed — owner decision (2026-07-27): #429 owns all
Dashboard-tree management and click operations.

This is the primitive behind one of those clicks. #429's panel-row contract is
"Click → Open dedicated query in Query surface", which calls exactly this
app.openSavedQuery path — so the issue that specifies the gesture and the issue
that fixes what the gesture calls are one change.

Your analysis carried over verbatim into #429's "Make the open-query primitive
resolve first (absorbs #443)" section: the unconditional showQuerySurface()
before resolution, the dead click that also pushes a history entry and loses the
user's place, and the reason it is not reachable today — #426 cancels pending tree
clicks on workspace switch and disposal, and every current caller resolves the id
first.

The point that made it worth folding rather than leaving open: it goes live again
precisely when #429 adds more row commands over the same primitive.

Requirements in #429 are yours unchanged — resolve first, report one flashToast
diagnostic on a miss, change no surface and no route, keep resolving ids
behaving exactly as today, and check no caller depends on the current
always-switch behaviour before tightening it. Your acceptance criteria are now
#429's "Open-query primitive (#443)" test subsection and an acceptance bullet.

Nothing dropped; closing as absorbed, not as rejected.