fix(#429): resolve a saved query before navigating, trim blank tile titles (phase 1)

[BorisTyshkevich]

What & why

Part of #429 — phase 1 of 6: the two prerequisites every later phase builds on. Both halves are corrections to primitives rather than features, so they land green and self-consistent on their own.

openSavedQuery resolves before it navigates (#443)

app.openSavedQuery(queryId) called showQuerySurface() before it knew whether the id resolved. An unresolved id therefore threw the user off whatever surface they were on, pushed a history entry, opened no tab and reported nothing — a dead click that also lost their place.

It resolves first now. A miss reports one diagnostic ("That query is no longer part of this workspace.", the wording openDashboard already uses for a missing Dashboard) and changes no surface, no route, no tab. A resolving id behaves exactly as before.

The issue asks for a caller audit before tightening. There are three production callers, and none depended on the unconditional switch:

Caller	Why it is safe
src/ui/dashboard-tree.ts:289 — the row's open-query command	addresses a query the row was just painted from
src/ui/dashboard-tree.ts:350 — the post-assignment reveal	opens the id the assignment mutation just created
src/ui/dashboard.ts:1855 — per-tile Open in Workbench	the button is null unless queryById.has(ts.queryId)

Not reachable through the tree today (#426 cancels pending clicks on workspace switch and disposal), which is precisely why it lands here: it goes live the moment phases 2–5 add more row commands over the same primitive.

A whitespace-only tile title never reaches a heading or an accessible name (#476)

dashboardTileV1.title carries no minLength, so a hand-authored or imported " " is a schema-legal document — and being truthy it beat the query-name fallback unfiltered. The visible .dash-tile-name heading rendered blank, and the names composed from it announced as "Open, — , in Workbench" and "Remove, — , from the dashboard".

The viewer now trims the authored title before the fallback chain, in the one place a tile's display title is resolved — so every consumer of state.title is settled at once: the heading, the KPI card aria-label, the Open in Workbench and Remove tile labels, the tile-search haystack, the parameter-analysis labels, and the variable-conflict diagnostic. A padded authored title is kept, trimmed.

This is a deliberate behaviour change for existing documents carrying such a title: they start showing the query name. No shipped UI writes tile.title, so only hand-authored and imported documents are affected. (dashboard-tree-model.ts already trimmed, so the tree row was correct and the canvas disagreed with it.)

Acceptance criteria claimed

• ✅ openSavedQuery resolves before it navigates and reports a miss (openSavedQuery switches surfaces before resolving the id, and stays silent when it fails #443).
• ✅ A whitespace-only title never reaches a heading or an accessible name (A whitespace-only tile title survives into accessible names #476).

Every other bullet is explicitly deferred: the pencil/trash row actions, the one-create-command reconcile (#481), the chevron/name/trailing gesture split (#472), ownership safety, concurrency, and the repair-planner decision (#449/#431) → phases 2–6. Per the issue's #438 note: this phase adds no focus-tile gesture, so no layout engine needs verifying for one.

Verification

• npm test — 5816 passed, 177 files, per-file gate held (statements/lines 100%).
• Sabotage-checked: with both production changes reverted, exactly the four new tests fail and nothing else — so they are genuinely falsifying, and no existing test depended on the old behaviour.
• npx tsc --noEmit clean; npm run build clean.
• npm run test:e2e — 281 passed on chromium + webkit (Firefox can't launch locally; it comes from CI).

Follow-up filed

tile.description has the identical untrimmed-fallback shape one line below the title (dashboard-viewer-session.ts:563), so a whitespace-only description still renders an empty .dash-tile-desc span instead of falling back to the query description. Out of #476's scope (it corrupts no accessible name), filed as #489 (inbox) rather than folded in here.

Checklist

• npm test passes (the per-file coverage gate is non-negotiable)
• Tests added/updated in the same change as the code
• npm run build succeeds (single-file dist/sql.html)
• Layers kept honest: pure logic in src/core/, network in src/net/ (injected fetch), DOM in src/ui/
• No new runtime dependency (or it's a deliberate, justified addition — see CONTRIBUTING)
• README / CHANGELOG.md ([Unreleased]) updated if behavior or the deployed surface changed
• Reconciled affected tracked work (roadmap Roadmap to 1.0.0 #68, the issue body, ADR/CHANGELOG) if this change reshaped it