RudderStack AI Events Instrumentation

Turns the approved plan into the smallest reviewable diff, for AI events spec v0.3. Recipes with exact code: references/node.md, references/python.md, references/go.md, references/client-events.md. Full API: each SDK's README (npm package, PyPI page, Go module).

Preconditions

1. ai-events.md exists at the repo root with front matter status: approved. Missing or draft: stop and run rudder-ai-events-setup; never instrument from an unapproved plan. Copy every value from the fenced yaml block under ## Config (it wins over the prose); the files you may touch are the ones under ## Files to change. Key paths below (spec.config, surfaces[], sdks[], spec.switches) are inside that block, under spec.
2. Every surface you are about to change has status: instrument. Skip the rest (skipped, blocked, unsupported).
3. Apart from ai-events.md, the working tree is clean, or the user agreed to mix changes. Work on the current branch; on the default branch, create the branch the plan's ## Summary names (feat/ai-events by default) without asking.
4. Each sdks[].version (<VERSION> in the recipe files) is @rudderstack/ai / rudderstack-ai 0.7.0 or later, or ai-sdk-go v0.3.0 or later (verify needs their migration check and recorders); never a branch or pseudo-version. Older: run rudder-ai-events-setup, which re-resolves versions on resume. A user-named unreleased exact target stays in the plan, but installation waits for publication. Browser-only plans have sdks: []: skip server install/configure steps and consume the named server dependency's response contract and switch source.

Install preflight

Before writing code, check that the pinned version installs as is: