perf(tests): reduce schema fixture work and use two file-scheduled workers - #198
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.
Change
Validate immutable authored schema fixtures once per test process, with deep copies and fresh admission contexts per scenario. Preserve real schema loader/currentness tests and all meaningful negative assertions. Run the existing complete release test step with two file-scheduled workers.
Evidence
Same local Python 3.14 environment and exact CI fixture pins, 568 tests plus 694 subtests throughout:
These are shared-host comparisons, not hosted CI or population p95 claims.
Independent fixture review passed. Complete release entrypoint passed all steps; 11 focused release/docs tests, compile checks and diff check passed. Normal KAG family generated with workflow-pinned producer 14ee1e33 and exact base ec1cab9; full stable-candidate gate verified all components. No production protocol/cache changes, no private session data, no deployment.