v0.3.1 — Fix Ask AI session-owner resolution error

Ask AI no longer fails with Session owner could not be resolved when opening a new session (regression on connections-registry topologies — two or more backends / profiles).

Root cause: Ask AI pre-created the session with a raw session.create RPC and navigated to it. That bypasses the app's own create path, which is the only place owner hints/tiles/rows get stamped, so the renderer's fail-closed owner resolution refused to route any session-scoped RPC (model pick, prompt send, file attach) to the orphaned session — and the session never reached a state.db.

Fix: Ask AI now opens a fresh draft via host.newChat() — the same door the sidebar '+' uses. No session-scoped RPC is issued; the session is created by the app's own path at send time with full owner bookkeeping.

Behavior change: the new session no longer carries a seeded 'Session analysis: …' title; auto-title takes over from the pasted prompt.