claude_telemetry_events dataset for behavioral events

[philcunliffe]

Parent

Implementation spec: #798 (LLP 0245).

What to build

Behavioral events the wire never showed become queryable: @hypaware/claude registers its first dataset, claude_telemetry_events (manifest contribution plus registration at activation). One row per event; typed columns for the hot fields (event name, session id, tool name, decision, source, cost); an attributes JSON column for the rest. Not routed through @hypaware/otel's generic datasets, not widened into ai_gateway_messages. The registration sets the source signal so central forwarding works.

Acceptance criteria

• Smoke posts tool_decision, permission_mode_changed, and hook events and reads them back via hyp query sql from claude_telemetry_events
• Hot fields are typed columns; remaining attributes preserved in the JSON column
• Source signal present so fleet forwarding does not fall back to the dataset name
• Dataset appears in dataset enumeration alongside the existing ones

Blocked by

• Tracer bullet: claude OTLP listener captures a session into ai_gateway_messages #803

[philcunliffe]

Completed as part of PR #818. claude_telemetry_events is registered, queryable, and covered by unit and smoke tests.