Sync published release state and market evidence - #99
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.
Updates aienvmap's internal release contract to represent the already-published 0.2.2 release consistently across the scorecard, schema, summary, and dashboard defaults. Centralizing release metadata prevents stale candidate state from reappearing. It also refreshes the dated market snapshot and regression tests while keeping independent validation separate from engineering readiness. Validation: npm run release:check passed with 407 tests passing, 0 failures, and 1 platform-specific skip; contract, performance, package, installed-package, and simplified-dashboard checks passed.