Make native Strands state reviews browsable and portable offline - #24
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
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 native Strands companion required installing its optional SDK or reading raw JSON before users could inspect the complete state review. Add a homepage entry and a browser report with expected/baseline/current state, regression and improvement filters, all eight checks, and links tied to both native report files.
The deterministic download retains the page, original native reports, original EvalArc inputs, and a checksum inventory. The build recomputes each displayed rule against the source recording and rejects contradictory summaries or missing/duplicate identities. Keep the native two-rule mean explicitly separate from the five-dimension EvalArc score; the Python release stays at 0.12.1. Update the existing outreach draft with the install-free entry.
Validation: 366 Python tests, Ruff lint/format, wheel build, HF card validation and documentation links passed. Browser checks passed at 1440/390/320px, including keyboard controls, valid/unknown check links, original downloads, offline mode and disabled JavaScript. The deployment check also exercises the new report and ZIP inside the actual HF Hub iframe.