migrate-waniwani-sdk-0.15-to-0.16

Migrate @waniwani/sdk 0.15 → 0.16

A self-contained migration for the single hop from 0.15.x to 0.16.0. Apply it when a project on 0.15 is moving to 0.16. 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.15 first (that jump ships its own migration); if it is already on 0.16+, there is nothing to do here.

What 0.16 changes

Tracking becomes one typed track client on four surfaces (server waniwani(), the scoped client in tool handlers and flow nodes, useWaniwani() in MCP-app widgets, and chat.track on chat host pages), each attaching session identity automatically. Five breaking changes result, all mechanical.

Procedure

1. Bump the dependency.

   bun add @waniwani/sdk@^0.16.0
   

2. Apply changes 1–5 below. Skip any with no matching call sites and note it in the report.
3. Verify — this is the completion check.

   bun run typecheck
   bun test
   

   Every remaining type error points at a call site the new API rejects; each is one of the changes below.
4. Report which changes applied, which were skipped for lack of call sites, and anything that needed a judgment call (a string track() name with no typed equivalent).

1. useWaniwani() returns the typed server track surface

useWaniwani() now returns { sessionId, track, identify, flush }, where track is the same TrackFn as the server client. Removed: string-based track(name, properties), step(name, meta), conversion(name, data), the capture option, and all DOM auto-capture (a single widget_render event still fires automatically on mount).

Auto-fix, in order:

1. Delete any capture option passed to useWaniwani({ ... }).
2. Replace wani.step(<name>, <meta>) and wani.conversion(<name>, <data>) with the typed revenue helper for that funnel stage:
   • price shown → wani.track.priceShown({ amount, currency })
   • options compared → wani.track.pricesCompared({ options })
   • a choice made → wani.track.optionSelected({ id, amount, currency })
   • qualification bar met → wani.track.leadQualified({ externalId?, email?, name? })
   • a conversion → wani.track.converted({ amount, currency })
3. Rewrite string calls wani.track("<name>", <props>):
   • <name> is a typed event (quote.requested, quote.succeeded, quote.failed, link.clicked, purchase.completed, or a revenue event) → object form: wani.track({ event: "<name>", properties: <props> }).
   • otherwise → pick the closest typed event; custom event names are not part of the typed surface (flag these in the report).
4. Remove any imports of AutoCaptureToggles or WidgetTrackFn; the widget track is the same TrackFn type as the server client (from @waniwani/sdk).