web: address rollup review #1 — deep-link reconnect on restored activeServerId

Gate the deep-link connect phase on 'not already connected' rather than on
activeServerId identity: if a prior session restored activeServerId to the
'deep-link' id while disconnected, the old guard marked the ref consumed and
never connected, so reloading the same deep-link URL silently didn't auto-
connect. onToggleConnection only disconnects when the id is active AND status
is connected, so the new condition also avoids toggling a live connection off.

Also documents (rollup review #3) that pre-selecting a deep-linked app
deliberately bypasses AppsScreen.handleSelect's no-input auto-launch — a URL
must not fire a tool call without the token-gated autoOpen.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BrihGWcrM9JGRyu41nzZYw

clients/web/src/components/views/InspectorView/InspectorView.tsx

@@ -892,6 +892,13 @@ export function InspectorView({
       ...collectSchemaDefaults(target.inputSchema),
       ...deepLink.appArgs,
     };
+    // Seed the selection directly rather than routing through
+    // AppsScreen.handleSelect. This deliberately bypasses handleSelect's
+    // no-input-app auto-launch: a deep link must never invoke a tool against
+    // the target server unless the token-gated `autoOpen` is set — even a
+    // no-input app waits for that explicit signal (or a manual "Open App"
+    // click), matching the security stance that a crafted URL alone can't fire
+    // a tool call.
     onActiveTabChange("Apps");
     onAppsUiChange({
       ...appsUi,