Repository navigation
docs: close out v0.52.0 release and companion verification - #339
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.
Record the authenticated v0.52.0 release and completed playground/guardbench synchronization. Update current scope, backlog and maintainer checkpoints while keeping historical candidate and failed-attempt evidence distinct; broader #141 remains open and #331 stays excluded.
The actual published native probe exposed VS Code migrating a legacy boolean
extensions.autoUpdatefixture setting to the current stringoff. Correct that single synthetic literal; preserve all byte/mode checks. The fresh published run passed all 12 CLI cases and native path/JSONC observations, with independent image/raw readback and 124 harness checks. No npm runtime changed and no republish is required.Validation includes independent provenance/SBOM/tamper checks, all 66 runtime files matching a source build, published clean-install smoke, 139 protocol comparisons and 104 raw capture replays. Both companion updates are independently reviewed, CI-green and merged. Actual browser parity covers 57 corpus cases plus one raw prototype case; all seven deployed Pages assets match the tested source. Repository links and Obsidian frontmatter/wikilinks/content readback are checked; Obsidian visual rendering remains unverified.