Validate telemetry beyond connectivity with a canary trace

Telemetry validation should separate configuration, transport, persistence, and presentation. A successful protocol initialization proves connectivity, not lifecycle collection.

After hook trust is established, send a harmless uniquely tagged canary and require proof at three layers: a tool call reaches the collector, the server appends an ordered requested, activity, completed sequence, and the reviewer view renders the activity without double-counting transport events.

In subscription-observed mode, provider frames, token usage, and activity that bypasses hooks remain unknown. This validates observed hook coverage, not complete provider or local activity.