Finalize 2.0 API, package baseline and release validation - #670
Merged
Merged
Conversation
8 tasks
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.
Closes the Phase 18 public API/package preparation work for #86. The eight shipping packages now have reviewed public/protected snapshots extracted from actual nupkgs, a published 1.1.1 comparison with provenance, version calibration guards, and a public API/package ADR with a complete migration table. Removes the unused Default Context, accidental build-symbol API, and legacy descriptor constructor; fixes platform-dependent generated manifest fingerprints and bounds CI test concurrency. Includes both dependency upgrades already merged into main (#566 and #567) for dev.
Validation: Release solution build (0 warnings/errors); unit tests Passed: 1802, Failed: 0, Skipped: 0; generator tests Passed: 264, Failed: 0, Skipped: 0; nine dynamic module tests passed individually, plus 50 bounded diagnostic stream-exit executions passed. One initial stream-exit counter assertion failed; detailed counter diagnostics remain enabled and CI/soak validation is required. Actual-package API comparison and API/version negative controls passed; architecture and maintainability guards passed. DateTime test assertion now checks the established raw ticks/Kind wire contract without depending on the machine timezone.
Release Gate and fresh Actions soak results will be linked as they complete. The five-hour Actions soak is asynchronous under the release instruction; pending never means passed. Final publication follows dev → main, final release validation, then fixed-four-physical-core published-1.1.1 → 2.0 → published-1.1.1 performance evidence. No release tag is created by this PR.