Repository navigation
Show execution costs with user and organisation thresholds - #648
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.
Execution summaries now show estimated USD cost immediately after duration, only above the viewer's display threshold. Above the alert threshold the estimate is red and says “High cost”. A reserved responsive slot prevents movement as cost finalises; missing or partially priced totals stay blank.
The represented
#V#hasExecutionCostDisplayPreferencessingleton stores an atomic USD decimal-string pair on a user or organisation. Precedence is user, current server-bound organisation, then server defaults of US$0.01/US$0.10. The predicate uses the existing virtual-concept registry; an actor-bound API persists personal overrides through the canonical governed write service. New telemetry preserves exact Decimal strings, with numeric-only historical compatibility.Validation: 53 targeted Python tests, 301 frontend tests, static JS lint and diff checks pass. Twelve local browser fixture checks exercise the actual template/CSS/chat renderer at 1440px and 390px, including strict boundaries, accessible red alerts, unchanged slot/header geometry, duration and last activity. Fixture receipts/screenshots are retained in the worker worktree at
.run/execution-cost-evidence/; this is not authenticated live acceptance.Merge decision: ready; the observed mobile layout shift is repaired and no material regression remains on the affected path. No live preference records were changed and no deployment is requested. Older numeric-only history cannot recover precision absent from its stored telemetry. Configuration contract and operation are documented in
docs/engineering/execution_cost_display.md.Von task:
#V#task_agent_b7e1e1753af2cee586427d6e9388ac4a.