test(dogfood): the MCP context-thread pin admits the bridge's per-request seams (#30892)

`handleMcp` now builds the bridge as `buildMcpBridge(deps, context,
{ recordFiles })`. The pin still requires the request context as the
second argument and only admits a trailing seams object literal, so a
bridge built from anything else still drops the key and goes STALE.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016WV4cyqd3A7fbCWrqM3KCz

Author: claude

packages/qa/dogfood/test/authz-conformance.test.ts

@@ -519,10 +519,13 @@ const PROBES: readonly Probe[] = [
     re: /async\s+handleMcp\s*\(/g,
     key: () => 'mcp:http-dispatcher.ts:handleMcp',
   },
+  // [#30892] The request context stays the bridge's SECOND argument; a trailing
+  // seams object literal (the per-request file seam) is admitted beside it, so
+  // a bridge built from anything but the request context still vanishes here.
   {
     kind: 'GATE_PIN',
     file: 'packages/runtime/src/domains/mcp.ts',
-    re: /buildMcpBridge\(deps, context\)/g,
+    re: /buildMcpBridge\(deps, context(?:, \{[^}]*\})?\)/g,
     key: () => 'mcp:domains/mcp.ts:buildMcpBridge(context-threaded)',
   },
   // (3) The stdio transport's PRINCIPAL binding (ADR-0101): the long-lived