feat(pricing): flag pinned rows in diff/show (provenance vs costing)#152
Merged
Merged
Conversation
Both commands render the RAW snapshot for provenance, so a pinned (verified) row displays the source's value and diff lists it as drift — even though the cost engine ignores the source there and prices at the baseline (#151). Left unmarked, `diff` invites a reader to "correct" the baseline toward the stale source value, re-introducing exactly the regression pinning fixed. Add PinnedSnapshotKeys() (catalog pin keys translated into the normalized "<provider>/<model>" snapshot key space) and use it to annotate both views: - `diff`: a pinned modified/removed row gets "[pinned: runtime keeps baseline]" plus a footer explaining the cost engine ignores the source here and warning against editing the baseline toward the drift without re-checking the vendor. - `show`: pinned rows get a "[pinned]" marker and a footer noting the printed value is provenance only and may differ from what costing uses. Purely presentational — no change to costing or the snapshot store. Claude-Session: https://claude.ai/code/session_01QKTcmXFTKoTQr7mB3HCuHZ
felixgeelhaar
added a commit
that referenced
this pull request
Jul 8, 2026
felixgeelhaar
added a commit
that referenced
this pull request
Jul 8, 2026
…emini rows Claude-Session: https://claude.ai/code/session_01QKTcmXFTKoTQr7mB3HCuHZ
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.
Fast-follow to #151.
pricing diffandpricing showrender the raw snapshot for provenance, so a pinned (verified: true) row displays the source's value anddifflists it as drift — even though the cost engine ignores the source there and prices at the baseline. Unmarked,diffinvites a reader to "correct" the baseline toward the stale source value, re-introducing exactly the regression pinning fixed.Change (presentational only)
pricing.PinnedSnapshotKeys()— catalog pin keys (Key{provider,"model*"}) translated into the normalized"<provider>/<model>"snapshot key space.diff: pinned rows get[pinned: runtime keeps baseline]+ a footer explaining the cost engine ignores the source here and warning against editing the baseline toward the drift without re-checking the vendor.show: pinned rows get a[pinned]marker + a footer noting the printed value is provenance only.No change to costing or the snapshot store.
Live output
New test
TestPinnedSnapshotKeys(key translation + no-star + unpinned excluded). Full suite + lint green.https://claude.ai/code/session_01QKTcmXFTKoTQr7mB3HCuHZ