fix(blue-sdk-wagmi): remove blockNumber from query keys to prevent OOM

[prd-carapulse]

Summary

Remove blockNumber and blockTag from all fetch*QueryKey functions so that TanStack Query reuses a single cache entry per entity instead of creating ~2,200 new entries every block (~10 s on Base L2).

The problem

On heavy market pages (e.g. Base cbBTC/USDC with 14 shared-liquidity vaults spanning ~35 markets), connecting a wallet creates ~2,200 TanStack queries. Because blockNumber is part of every query key, each new block creates ~2,200 brand-new cache entries. TanStack Query's built-in GC does not reliably fire at this volume (observed 6,319 idle/inactive queries with gcTime: 30000 that were never collected). Memory grows at ~2.3 MB/s → OOM in ~20 minutes.

Consumer-side workarounds (manual cache cleanup, block-gating, gcTime: 30_000) reduced growth to ~0.9 MB/s but cannot eliminate it — the V8 heap fragments from the sheer allocation/deallocation churn.

The fix

Separate "what to cache by" from "what to fetch at."

Layer	Before	After
fetch*QueryKey	includes blockNumber, blockTag	entity identifiers + chainId only
fetch*QueryOptions.queryFn	reads block from queryKey[1]	captures block from closure
Hook staleTime	defaults to Infinity when blockNumber set	passthrough from consumer (query.staleTime)
Cache entries per cycle	~2,200 created + ~2,200 destroyed	0 new / 0 destroyed (re-fetched in place)
Memory growth (connected wallet)	~0.9 MB/s (with workarounds)	~0 (stable)

Changes

• packages/blue-sdk-wagmi/src/queries/fetch*.ts — Remove blockNumber and blockTag from queryKey return. Capture them from the parameters closure in queryFn.
• packages/blue-sdk-wagmi/src/hooks/use*.ts (20 files) — Remove staleTime: Infinity default when blockNumber != null. Consumers pass staleTime explicitly if needed.
• packages/simulation-sdk-wagmi/src/hooks/useSimulationState.ts — Drop the Infinity staleTime override; use parameters.query?.staleTime directly.
• New: packages/blue-sdk-wagmi/src/query-key-prefix.ts — Exports BLUE_SDK_QUERY_NAMES and invalidateAllBlueSdkQueries(queryClient) for consumer-driven block-change invalidation.

Consumer migration

import { invalidateAllBlueSdkQueries } from "@morpho-org/blue-sdk-wagmi";

// In the component that tracks blocks:
useEffect(() => {
  if (!block?.number) return;
  invalidateAllBlueSdkQueries(queryClient);
}, [block?.number]);

Existing consumer workarounds (manual cache cleanup setInterval, skip-block-while-loading guard) can be removed after this lands.

⚠️ Breaking changes

• Query keys no longer contain blockNumber/blockTag. Code that reads the cache with block-specific keys (queryClient.getQueryData(["fetchMarket", { ..., blockNumber }])) must be updated.
• staleTime no longer defaults to Infinity when blockNumber is provided. Consumers relying on this implicit behavior should pass staleTime explicitly.

Expected impact

Metric	Before (with workarounds)	After
Cache entries at steady state	~2,200 + stale accumulation	~2,200 (fixed)
Entries created per block	~2,200	0
Memory growth (wallet connected)	~0.9 MB/s	~0
Time to OOM on heavy markets	~60 min	Never
Consumer workarounds needed	3	0

Context

Full investigation: see attached a0c1906d-ba4f-49d4-9817-884e500be386.md

Sentry issues: MORPHO-CONSUMER-4HG (894 events), MORPHO-CONSUMER-32X (OOM)