Repository navigation
Add Token consumption distribution and interval navigation - #236
Merged
Merged
Conversation
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.
Session analysis could show accumulated Tokens but could not locate consumption hotspots or explain which samples support cache ratios. Analytics v5 adds scoped Token distribution, known subtotals with coverage, cache shares from one complete sample cohort, and navigation to contemporaneous original records.
The report uses the existing authorized Canonical snapshot. Thread/model selectors and interval cursors bind the snapshot; Usage-only changes invalidate both evidence and conditional Reader links. Usage intervals span their own stored clocks, including samples outside the Event span. Interval navigation does not infer a response or model attribution. Missing classifications, absent usage, zero denominators and safe-integer overflow remain explicit. Older analytics representations retain their existing wire semantics. Web negotiates v5 through the additive
v=5parameter on the v4 media range, keeping v4/v3/JSON fallback inside the browser's CORS safelist length limit. Pricing remains a separate increment.Validation:
02f9d9e) and 0.5.10 (79a8b3e) passed same-origin and split-origin requests with the exact compact header, returning their genuine analytics v4/v3 representations. Each baseline retained its original source files and dependency lock bytes.ADR-0127 and the current feature/OpenAPI guides document accounting, timestamp and compatibility limits. This PR implements the increment; it does not publish npm packages or deploy the Server.