Update Claude Agent SDK to 0.3.245

[SawyerHood]

Human comments

What was wrong

@anthropic-ai/claude-agent-sdk was pinned at ^0.3.197; the current release is 0.3.245. The old pin also forced a compatibility cast in SdkSession.applyMutableSettings, because that SDK's Settings type omitted effortLevel: "max".

Separately, the recorded-conformance fork cell failed on macOS before this change. tmpdir() is a symlink there, and the Agent SDK names a project directory after the real path, so the harness seeded the fork transcript under a name the SDK never looked up. Linux CI never hit this.

What changed

• plugins/provider-claude-code/package.json: SDK ^0.3.197 → ^0.3.245. Lockfile changes are limited to the SDK and its platform packages.
• plugins/provider-claude-code/src/bridge/sdk-session.ts: the new SDK types max on applyFlagSettings, so the ClaudeMutableSettingsQueryBoundary cast is gone. ClaudeMutableFlagSettings is a type alias now, because the new Settings carries a string index signature that only an object type alias satisfies implicitly.
• bridge.test.ts / bridge.calibration.test.ts: the new CanUseTool requires requestId and may resolve to null; the tests pass a request id and narrow the result.
• packages/provider-bridge-protocol/src/testing/parity.ts: the replay workspace is realpathSync'd so the seeded fork transcript sits where the SDK looks.
• @get-bb/plugin-sdk 0.4.19 → 0.4.20 (packages/domain/src/plugin-sdk-version.ts + packages/plugin-sdk/package.json): the parity.ts change ships in dist/provider-bridge-testing.js, and 0.4.19 is already taken on main. The npm version guard passes.

No wire change between server and host daemon; HOST_DAEMON_PROTOCOL_VERSION is unchanged.

How you verified

• pnpm exec turbo run typecheck test --filter=bb-plugin-provider-claude-code --force: typecheck clean, 335/335 tests pass (rebased on current main).
• pnpm exec turbo run test --filter=@bb/provider-bridge-protocol --force: 237/237 pass. @bb/domain: 172/172.
• node packages/plugin-sdk/scripts/check-npm-version-guard.mjs: PASS (0.4.20 not on npm yet). Before the bump it failed on dist/provider-bridge-testing.js drift, which confirms the bump is required.
• Baseline check: with the old SDK on HEAD, the fork cell fails identically on macOS, so the harness fix is not masking an SDK regression. After the fix, bridge.recorded-conformance.test.ts passes on macOS.
• Note: running the replay suites of several packages concurrently produces spurious 5 s timeouts in bridge-worker-entry.test.ts and the recorded cells; run alone, each suite is green every time.
• EAP codename scan (working tree, tracked files at HEAD, added lines and commit messages of origin/main..HEAD): 0 hits in every group.

AGENT GENERATED