Repository navigation
docs(readme): highlight evaluation and reporting features - #72
Merged
Merged
Conversation
![lexmount-ocr[bot]](https://avatars.githubusercontent.com/u/277637559?s=60&v=4){kind=small}
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.
Change
Make the README opening explain what users can do with Browser Eval: run a comparison and get a report, choose benchmarks, extend participants, inspect evidence, reuse saved outputs, compare quality/performance/cost, trace experiment inputs and share reports with access controls.
Add the same compact feature table and navigation in English and Chinese. Keep workflow and benchmark names in the existing track table, and remove overlapping introductory paragraphs so the opening complements the repository About description.
Validation
All four existing README navigation tests pass, and local links resolve in both languages. The documented single-command offline evaluation completes and generates its HTML report with the expected success and failure fixtures. Markdown diff checks pass.