Conversation
Codex wrote this commit. Upgrade Ampere to Phosphor 0.3.0 and map provider completion telemetry into HEAT, INTENSITY, and DENSITY emitter metadata with covering tests.
wow-miley
deleted the
email/ampr-144-ampere-bridge-cost-metadata-to-phosphor-metabolic
branch
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.
Closes #443.
I wrote this PR to upgrade Ampere to Phosphor 0.3.0 and bridge provider completion telemetry into metadata-rich emitter effects.
It threads provider call telemetry through the watch presentation layer, maps cost, latency, and token usage into HEAT, INTENSITY, and DENSITY, and keeps the existing cognitive choreography in place.
It also updates the waveform and demo integrations to use the new Ampere-local bridge and adds tests covering normalization, metadata emission, and telemetry propagation.