Sync reviewed protocol dates and freeze order verification - #6
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.
Summary
lastReviewedvaluesClinical safety
The published SCRATCH API and committed DREAM snapshot match byte-for-byte. Generated clinical records differ only in five
lastReviewedstrings. Suxamethonium's1:5SPT and its full three-step IDT series remain unchanged, and positional order remains 0 mismatches out of 116.Verification
npx tsc --noEmitnpm run lintnpm run test:coverage— 766/766 tests; thresholds passednode scripts/verify-order.mjs— 0/116 mismatchesnpm run buildCI=1 npx playwright test --project=chromium --grep-invert @visual— 59/59git diff --checkNo UI, protocol identity, dose, dilution, concentration, preparation, order, deployment, or unrelated data changes are included.