chore(eval): ASCII-only eval report (replace em-dash with --)#14
Merged
Conversation
The generated .myagent/evals/runs/<id>/REPORT.md Notes paragraph used a U+2014 em-dash, which mojibakes on non-UTF8 console code pages (e.g. PowerShell shows it as a garbled sequence). The file itself was valid UTF-8, but keeping generated artifacts strictly ASCII removes the cross-terminal surprise entirely. Also swapped the matching em-dash in a source comment so eval.ts is uniformly ASCII. No behavior change: eval still passes 5/5 with the same deterministic $0.0528 cost fingerprint; the gate test (eval.test.ts) is green. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
The generated .myagent/evals/runs//REPORT.md Notes paragraph used a U+2014 em-dash, which mojibakes on non-UTF8 console code pages (e.g. PowerShell shows it as a garbled sequence). The file itself was valid UTF-8, but keeping generated artifacts strictly ASCII removes the cross-terminal surprise entirely. Also swapped the matching em-dash in a source comment so eval.ts is uniformly ASCII.
No behavior change: eval still passes 5/5 with the same deterministic $0.0528 cost fingerprint; the gate test (eval.test.ts) is green.