migrate-waniwani-sdk-0.22-to-0.23

Migrate @waniwani/sdk 0.22 → 0.23

A self-contained migration for the single hop from 0.22.x to 0.23.x. It covers only that jump; for other version boundaries use the matching migrate-waniwani-sdk-<from>-to-<to> skill, or the general procedure in the SDK's changelog.

Precondition: the project is on @waniwani/[email protected]. If it is on an older version, migrate up to 0.22 first; if it is already on 0.23+, there is nothing to do here.

What 0.23 changes

withWaniwani adds one argument to every tool it wraps so the calling model can say why the user came. In 0.22 that argument was a nested telemetry object ({ intent, context }) the model was asked to fill after every user message. In 0.23 it is one optional string, sent only on the model's first call to the app:

"intent": {
  "type": "string",
  "description": "Brief summary of what the user wants and what prompted it, in their words. Send only on your first call to this app."
}

The shape follows OpenAI's plugin guidelines, which allow "a brief, task-specific user intent field" and rule out broad contextual fields and accumulated conversation context.

Breaking, and visible to tsc:

0.22	0.23
withWaniwani(server, { captureTelemetry })	withWaniwani(server, { captureIntent })
import type { CaptureTelemetryOptions } from "@waniwani/sdk/mcp"	import type { CaptureIntentOptions } from "@waniwani/sdk/mcp"

There is no deprecated alias. In plain JavaScript a leftover captureTelemetry is ignored and capture stays on, so search for it even when nothing fails to compile.

Behavior changes, not visible to tsc:

• tools/list. Each wrapped tool lists an intent string instead of a telemetry object. Snapshot tests of tool schemas change.
• Tool call arguments. A test that calls a wrapped tool with telemetry: { intent } should pass intent: "..." instead. A leftover telemetry key is stripped by schema validation, except on a tool whose schema is .strict(), which rejects the call.
• Tools with their own intent argument are left alone in 0.23 and record nothing. In 0.22 they got a telemetry argument beside it.
• Tools with their own telemetry argument gain the intent string in 0.23. Their own telemetry still reaches the handler unchanged.