Repository navigation
Content Telemetry v0.1 conformance and 0.1.3 release - #2
Merged
Merged
Conversation
- TelemetryEvent gains turnId, contentId and licenseRef - the spec event fields the SDK could not emit at all (content events MUST carry content_url or content_id, spec 5.7.5). - ConversationTurn gains responseMode and adRendered (spec 5.4); the wire serialiser now enforces the privacy-level field gating (5.5), so query/response text never leaves at intent or minimal and intent-level fields never leave at minimal. - IntentCategory carries the spec core set (question, explanation, fact_check, analysis, opinion_seeking, creative, ...) with the commerce values kept as documented extensions. - CitationType and CitationPosition gain 'unclassified' (spec 6.5). - New ConformanceLevel type (retrieval | grounding | citation); session documents can declare an informational conformance_level and now emit document_type: 'session' (spec 7.1). Additive only - no existing call sites break. 28/28 tests pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0.1.x implements Content Telemetry 0.1. 0.1.0 and 0.1.1 are consumed on npm by pre-standard releases; 0.2.0-0.4.0 predate the policy and should be deprecated on npm at publish time. Versioning policy documented in README and CHANGELOG. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Spec 5.4 makes privacy_level required on conversation turns. The wire helper previously treated an absent level as unrestricted, letting query_text and other gated fields through. privacyLevel is now required on ConversationTurn, and turnToWire strips gated fields to the minimal set when the level is missing at runtime (untyped JS callers). Adds wire-format gating tests and fixes two pre-existing typecheck errors in mcp.test.ts. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… add CI Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Aligns the SDK with Content Telemetry v0.1 and prepares the 0.1.3 npm release.
🤖 Generated with Claude Code