v0.6.1 visual integrity and bridge correctness - #40
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.
What this changes
This focused v0.6.1 release replaces four misleading Alignment Lab scatterplots with three data-bound row/forest views, rebuilds the bridge diagram as verified layers plus a prominent untested layer, adds real-browser documentation gates, modernizes and versions the docs site, and makes import/export readiness semantics fail closed.
The README is reduced from 32.9 KB to 8.1 KB and the Chinese README from 20.0 KB to 6.0 KB while keeping the negative calculator, RecoveryBench and Alignment Lab conclusions linked and explicit.
Bridge contract
import-verlclassifies every source field asexact,derived,informational_only,requires_user_confirmationorunsupported.import-report.jsonplus non-executableimported.template.yamlwith statusneeds_user_input.RunConfigvalidation before publication.export-verlwriteslaunch.template.shand reports artifact, upstream smoke, reward, launchability, distributed-execution and semantic-parity states separately.launchable: false.Visual and docs evidence
Distributed execution: NOT TESTED.Validation
[train]wheel installs plus a real toy demo: passedlaunchable: false; distributed execution not testedImmutable evidence
No benchmark JSON/JSONL or committed bridge smoke record changed. All 12 audited frozen hashes were rechecked. The calculator result remains SHA-256
53fc1d4d5b7adee09618d77ad62d4086ba56b78569832d6fc7c3bcd5c2695bbc; Alignment Lab result/task hashes remain584752dccb91654109c357b8ebb12681a12a9c1476a9ba539dd35e4d860a22efand8d7fc723436d7377d196fc44046d960e3cb7f0aa81e03d49ef05b627eb84630f.Checklist
0.6.1release metadata finalized.