fix(tools): clear every type error under packages/tools/test

[rajarshidattapy]

Fixes #1545 — with a correction to its error inventory, see the last section.

What was broken

claude-memory.ts lives in packages/tools/src/, but five files under test/ still imported ./claude-memory, and the Mastra and AI-SDK fixtures had drifted behind their installed types.

Changes

• Dangling imports (5 files, not 1). anthropic-example.ts, claude-memory-examples.ts, claude-memory-real-example.ts, claude-memory.test.ts and test-memory-tool.ts all imported ./claude-memory; all five now point at ../src/claude-memory.
• Mastra fixtures (35). ProcessInputArgs / ProcessOutputResultArgs gained a required state; added it to every fixture in test/mastra/{unit,integration}.test.ts.
• AI-SDK usage fixtures (2). Added totalTokens to the LanguageModelV2Usage literals — and removed rawCall, which surfaced as the next error once the usage type resolved: it is no longer part of the doGenerate result.
• Index-access errors. test-memory-tool.ts and claude-memory-examples.ts looped with for (let i…) + arr[i], which noUncheckedIndexedAccess rejects. Now for (const [i, x] of arr.entries()). These were masked behind the unresolved import.
• test-supermemory.ts. Called withSupermemory(client, containerTag, options); the signature is (client, options) with containerTag/customId inside options.
• anthropic-example.ts. Typed the conversation with the beta message types it actually uses, narrowed block.input once through MemoryCommand (which also removes an as any), and made view_range a tuple rather than number[].
• tsconfig.json. Excluded test/chatapp — a standalone Next.js demo with its own package.json, lockfile and tsconfig.json. It was contributing 56 JSX errors to this package's program, which is not something this package should be compiling.

Repointing the import also made test/claude-memory.test.ts loadable for the first time in a while, and it turned out to be a live-API suite: vitest run went from silently failing to collect it to reporting a dozen 401s. It is now gated behind SUPERMEMORY_API_KEY via describe.skipIf, matching test/mastra/integration.test.ts and test/with-supermemory/integration.test.ts. Its two offline path-validation tests still run.

Verification

cd packages/tools && bunx tsc --noEmit:

	before	after
test/**	110	0
src/**	36	36
total	146	36

bunx vitest run: 2 failed files / 90 passed → 1 failed file / 92 passed / 43 skipped. The remaining failure is src/tools.test.ts, which throws at module load when SUPERMEMORY_API_KEY is unset — pre-existing on main and a separate problem from type-checking. biome ci --changed exits 0.

Correction to the issue

The issue reports 31 errors, all in test/, with src/ clean. On main the actual count is 146, and src/ is not clean — it has 36:

29  src/ai-sdk.ts
 3  src/openai/tools.ts
 2  src/shared/cache.ts
 1  src/voltagent/middleware.ts
 1  src/openai/middleware.ts

Those are left alone here deliberately. The src/ai-sdk.ts and src/openai/tools.ts ones are a dual-zod install, not a code defect: packages/tools resolves its own zod@4.3.6, while the hoisted ai@5.0.148 resolves zod@3.25.76 from the root, so FlexibleSchema expects zod 3's ZodType and gets zod 4 objects. Fixing that means a root-level dependency or overrides change with monorepo-wide blast radius — worth its own PR rather than being smuggled into a test-fixture cleanup. src/shared/cache.ts (lru-cache v11 generic constraint) and the two middleware ones are ordinary typing fixes, also separate.

So check-types for @supermemory/tools is not green after this PR — but everything the issue names, and everything else under test/, is fixed.

[graphite-app]

This line also uses a type assertion (block.input as MemoryCommand) instead of a type annotation. The style guide rule 'Use type annotations instead of assertions for object literals' discourages unnecessary type assertions. Consider narrowing the type via a type guard or using a typed helper function instead of a bare as cast.

Spotted by Graphite (based on custom rule: TypeScript style guide (Google))



Is this helpful? React 👍 or 👎 to let us know.