fix: surface list-fetch failures instead of swallowing them

A list load that failed — a transport error, or a result the SDK's era
codec rejects as invalid — reported nothing. The connect-time refresh is
fired with no caller to await it (`void this.refresh()`), so its rejection
became an unhandled rejection: the header said "Connected", the panel
rendered an empty list indistinguishable from a server that has none, and
the failed exchange showed in the Protocol panel as a clean success.

Two surfaces now tell the truth:

- ManagedListState records the failure as observable state (`getError` +
  an `errorChange` event) and still re-throws, so App's auth-recovery
  wrapper keeps working. The four `useManaged*` hooks expose it via a
  shared `useManagedListError`, and the Tools/Prompts/Resources sidebars
  render a `ListLoadError` alert with the reason and a Retry.
- A response the client refused is attributed back to its Protocol entry
  (`markResponseRejected` → `responseRejected` → `MessageEntry.clientError`),
  which now renders an Error status and a "Rejected by the Inspector"
  alert rather than the green resultType badge alone. The SDK gives no
  request id with a decode failure, so the id is recovered by correlation;
  see the comment on `markResponseRejected` for why that is exact.

Also stops `listAllTools` from dropping a failing excluded-tools walk on
the floor — it stays non-fatal but is logged.

Closes #1953

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

core/mcp/inspectorClientEventTarget.ts

@@ -71,6 +71,15 @@ export interface InspectorClientEventMap {
   /** `server/discover` result on a probed/pinned connect; undefined on legacy. */
   discoverResultChange: DiscoverResult | undefined;
   message: MessageEntry;
+  /**
+   * A response the client REJECTED after it was logged — the server answered,
+   * but the SDK's era codec refused the result (e.g. a 2026-07-28 `tools/list`
+   * missing `ttlMs`/`cacheScope`). The wire frame is a valid JSON-RPC result,
+   * so the Protocol entry would otherwise render as a clean success; this
+   * carries the reason so it can be marked instead (#1953). `id` is the
+   * JSON-RPC id of the rejected response.
+   */
+  responseRejected: { id: string | number; reason: string };
   stderrLog: StderrLogEntry;
   fetchRequest: FetchRequestEntry;
   /** Fired when an in-flight fetch's response body is read asynchronously. */