Repository navigation
Remove legacy artifacts and use current released contracts - #9
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.
The test repository now uses released SDK v0.5.0 and protocol v0.3.0, with the cleaned server locked to an immutable verified source revision. Retired profiling tools and historical measurement files are removed, current SDK calls use their direct typed fields, and the README describes the remaining integration and single-record multiprocess benchmark workflows. Generated measurements stay outside source control; preparation warms the full dependency graph in a temporary module while preserving fixed inputs.
Independent review, offline race/vet, integration-tag compilation, dependency checks and Python tests passed. Dependency boundaries also passed offline with a separate cache initialized from empty; regression tests cover checksum isolation, failure propagation and checkout mutation detection. Real MongoDB/Elasticsearch integration passed discovery, direct routing, CRUD/Lua, batch validation, Scan/Native, recovery and independent client-process workloads. The locked server binary was built offline and its source identity and checksum verified.