Changes in 0.3.0

In development, not yet released. tools/release.sh prepare 0.3.0 removes this note.

Collection

• A landed record keeps the provider model a call ran on, as model, the name the runtime wrote on the record. It is what a token count is reported under, so a metric per model can be produced from the landed data alone. Records landed before this carry none, and the glossary says where the runtime writes it.

Read

• The conversation page is drawn by Horizon’s conversation renderer, @skywalking-horizon-ui/conversation-view, embedded from a pinned Horizon commit with Horizon’s themes and fonts, so asz view and the SkyWalking UI draw a conversation identically and the page needs nothing from the network. The hand-written viewer is gone with the API routes only it read; the page reads the asz.view document, the glossary, and the landed record behind a step. tools/conversation-view.sh rebuilds the copy from the pin, and CI fails when it differs.

Release

• A release publishes the container image under the version the tag names, and under latest when it is the newest release, and nothing looser. The major.minor line tag, 0.2 beside 0.2.0, is no longer published: a reader who pulled it could not tell which release answered. The 0.2 tag that 0.2.0 published stays on the registry and points at the same image as 0.2.0.

Metrics

• claude-code-local with metrics: true derives a reconstructed subset of the runtime’s own metric family from the landed files, claude_code.token.usage in phase one under the name Claude Code’s OpenTelemetry exporter uses: the usage of a call is its last fragment’s in line order and only a finished call counts, per minute, by type, model, query source and session; the exporter’s account, speed, effort and attribution labels and its auxiliary calls are not reconstructed, and the export page states the difference. The points wait in the storage root’s _metrics/ spool and asz push sends them over the metrics service, under asz’s identity, with the same budget and once-only rule as the files. metrics_lookback, 24 hours unless set, bounds the first derivation over a root with history, and so does the newest request the receiver landed, so a switch of source counts nothing twice. A pass is deterministic, names its requests after their landed files and saves its state once, so a pass cut short is run again to the same bytes. Every scenario checks the points on the wire against its plan, and the Collector job verifies the tokens that arrive from both sources.

• A receiver’s partial success is a success the protocol says not to retry: the rejected records or points are counted on the pass line as rejected, and the files are marked sent.

• A capture of what Claude Code 2.1.260 itself sent to the receiver, with every identifying value replaced, is the parity fixture: a test holds the derived token metric to it, the same name, unit, description, kind, value encoding and token types, the same session, model, query source and type labels, and a difference that is exactly the labels and metrics the export page lists as not derived. The derivation now writes doubles and a point for every type, zero included, as the exporter does. tools/otlpdump prints a spooled request as the protocol’s JSON.

• claude-code-otlp is a second adapter for the runtime: an OpenTelemetry receiver its own exporter is pointed at, gRPC and HTTP with protobuf on one listen port. Phase one lands the metrics requests it receives in the same spool, bytes as received, for asz push; logs and traces are accepted and dropped, counted in the status. It runs beside the local adapter under asz collect and asz view. metrics may be on for one adapter, never both, and the configuration refuses to load otherwise, so the same tokens are never counted twice. A receiver takes listen and metrics only; collector settings on it are refused, since it polls nothing.

• export.otlp.logs and export.otlp.metrics switch the two things a push sends, the landed files and rounds as logs and the metrics spool as metrics, each on its own, both on unless set off. asz push says which it is sending, and a configuration with both off is refused.