[ninglinLiu]

Summary

Fixes #1607.

@x402/svm 2.29.0 peers on @solana/kit >=8 and pulls @solana-program/compute-budget that imports the kit-8 subpath program-client-core. AgentKit still depended on @solana/kit ^2, so Bun hoisted kit 2 to the top level and failed to load AgentKit with Cannot find module '@solana/kit/program-client-core'.

Bump the direct @solana/kit dependency to ^8 so the peer is satisfied under Bun (npm/pnpm already worked via nested installs).

Test plan

• pnpm --filter @coinbase/agentkit build (tsc) succeeds with kit 8.6.0
• svmWalletProvider / solanaKeypairWalletProvider src unit tests pass
• Fresh Bun install of the published range loads import "@coinbase/agentkit" without the missing program-client-core error once this lands in a release

AI assistance was used to prepare this change; I reviewed the dependency bump and test results.

[HarryR]

Confirming this affects pnpm as well as Bun, and that this PR fixes both. A fresh install of @coinbase/agentkit@0.10.4 alone, no overrides (Node 24):

• npm 11: loads (npm nests kit 8 under @x402/svm@2.29.0)
• pnpm 12: fails on import and require: ERR_PACKAGE_PATH_NOT_EXPORTED: Package subpath './program-client-core' is not defined by "exports" in .../@solana-program+compute-budget@0.18.1_@solana+kit@2.3.0.../node_modules/@solana/kit/package.json. pnpm resolves @x402/svm@2.29.0's @solana/kit peer to AgentKit's 2.3.0.
• Bun 1: fails: Cannot find module '@solana/kit/program-client-core'

pnpm 11 and later hid this for a day, because by default they won't install a release less than 24 hours old (minimumReleaseAge). Since about 2026-10-29 18:30 UTC, a fresh pnpm or Bun install of AgentKit doesn't load.

This branch (95952df), built and packed, then installed the same way, loads under npm, pnpm (where @x402/svm@2.29.0 now resolves its peer to kit 8.6.0) and Bun.

Temporary workaround for projects depending on AgentKit 0.10.4, until an AgentKit release includes this fix: hold @x402/svm at 2.28.0, the last version that accepts kit 2.

• npm and Bun, in package.json:

  "overrides": { "@x402/svm": "2.28.0" }

• pnpm 11+, in pnpm-workspace.yaml (pnpm 11+ ignores package.json's pnpm field):

  overrides:
    "@x402/svm": 2.28.0

Remove the override once you're on that release: it would otherwise hold @x402/svm back from later fixes.