Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
hassiebp
commented
Sep 8, 2026
hassiebp
commented
Sep 8, 2026
hassiebp
commented
Sep 8, 2026
hassiebp
commented
Sep 8, 2026
Co-authored-by: Hassieb Pakzad <68423100+hassiebp@users.noreply.github.com>
This branch was successfully deployed
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
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.
Document the v2 observation response-field mappings, literal dotted metadata keys, ignored field groups, and valid empty usage/null costs so migrations update downstream readers as well as request methods. Populate the generation example with OTEL resource attributes and clarify that scans and known trace ranges should use time bounds.
Validation: current-head CI is green, including formatting, H1 checks, production build/link checks, sitemap checks, and Vercel preview. Local validation before review included Node.js 22 formatting, MDX compilation, generated Markdown checks, and response JSON/cursor consistency. No live project reads were performed.
Publish these docs before langfuse/skills#111, which directs agents to the response contract and examples.
Linear: https://linear.app/clickhouse/issue/LFE-16083/close-v4-migration-response-contract-and-verification-gaps