docs: fix stale spec anchor "The transparent proxy" -> "Iframe Renderer"

Two doc-pointer comments reference a dor-browser.md section that does not
exist. When dor-iframe.md + dor-agent-browser.md were unified into
dor-browser.md (#156), the proxy moved under the "Iframe Renderer" section;
the cleanup in 595531c missed these two because they wrap the section title
across two comment lines. Match the sibling pointers in iframe-proxy.ts,
iframe-proxy-rewrite.ts, and iframe-proxy-types.ts.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: dormouse-bot

lib/src/lib/platform/types.ts

@@ -176,8 +176,8 @@ export interface PlatformAdapter {
   // URL; absent or null falls back to ws://127.0.0.1:<port>.
   getAgentBrowserStreamUrl?(port: number): Promise<string | null>;
 
-  // iframe surface support (see docs/specs/dor-browser.md → "The transparent
-  // proxy"). Stands up a loopback proxy in front of a `dor iframe` target and
+  // iframe surface support (see docs/specs/dor-browser.md → "Iframe
+  // Renderer"). Stands up a loopback proxy in front of a `dor iframe` target and
   // returns the proxy URL the panel should frame, or a structured reason it
   // could not. Absent on hosts with no process to run a proxy (e.g. the web
   // host), where the panel falls back to a raw, uninstrumented `<iframe>`.

vscode-ext/src/iframe-proxy-host.ts

@@ -2,8 +2,8 @@
  * VS Code extension-host binding for the iframe transparent proxy.
  *
  * The proxy itself is host-agnostic and lives in `lib/src/host/iframe-proxy.ts`
- * (shared with the Tauri sidecar — see docs/specs/dor-browser.md → "The
- * transparent proxy"). This file only injects the VS Code logger; the
+ * (shared with the Tauri sidecar — see docs/specs/dor-browser.md → "Iframe
+ * Renderer"). This file only injects the VS Code logger; the
  * message-router calls `createIframeProxyUrl` exactly as before.
  */
 import { createIframeProxyUrl as createProxy } from '../../lib/src/host/iframe-proxy';