Repository navigation
fix(qualification): synchronize sustained timing fixtures - #50
Merged
Merged
Conversation
rschlaefli
changed the title
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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 qualification fixtures could advance virtual time while admission or HTTP responses were still pending, and resource checks could read partially written guard JSON. Wait for each admitted fixture wave to register and settle before advancing virtual time, release intentionally held requests through a controlled cohort barrier, and publish guards atomically. Existing late-slot, blocked-slot, boundary, overrun and cleanup assertions remain. A regression covers slower synthetic signing and transport.
The package also persists the finite production-load and staging recovery procedure. Production client and deployed service behavior are unchanged. The Node 24 suite passes all 21 tests; focused formatter and diff checks pass. Integrated review and all 14 exact-head CI jobs pass. Operational acceptance, measurements and observer receipts remain private under the plan. Staging interruption retains its concrete target approval. No UI changes are included.