rudder-ai-events-verify
RudderStack AI Events Verification
Proves the instrumentation sends what ai-events.md promises, before any real traffic. Runs offline: a recorder or mock RudderStack client, a mock model, no provider keys. Verification is not optional: it runs, and passes, before a commit or PR is proposed. If the user commits first, say plainly that verify has not run.
The checker (check, what-changes), the recorders and both schemas ship with the SDKs, @rudderstack/ai / rudderstack-ai 0.7.0 or later and ai-sdk-go v0.3.0 or later (cmd/aicheck v0.1.0); this skill adds the mock data plane and model server (scripts/mock_server.py, Python 3) and the procedures and checklist in references/verification.md. An app instrumented with an older SDK: upgrade first (rudder-ai-events-setup re-resolves versions).
Stacked delivery. When the plan splits the work into several PRs (## Files to change), verify the surfaces instrumented up to the PR at hand, with every check below; report the plan's later surfaces as n/a (later PR). The last PR's run covers the whole plan. With server_dependency, the backend PR lands first; browser verification drives that backend and combines both captures to check joins and the consumed switch.
Migration or new install. When the plan lists legacy events (the app already sends its own AI-related events through a RudderStack SDK), run every check below. With no legacy events, skip the legacy-switch capture, the legacy and breaking-change checks and the before/after diff: every event in ## What changes is new, taken from the switch-on capture.