Repository navigation
Clarify snapshot observation and schedule review guidance - #95
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.
Upcoming review-date snapshots showed a blank population cutoff before the actual observation date was recorded. The Work Queue and population review now explain which observation date to record, while known cutoff and whole-period dates retain their existing instructions.
A schedule set awaiting independent review of a current successor now names that requirement. It no longer implies that the original approved rule was missing at cutover. Rule selection, approval gates and reconciliation predicates remain unchanged.
Validation: independent combined code and security review; 108 focused tests; complete Node 24 validation; fresh generated consumer (224 records, zero errors or warnings); both package inspections; npm audit (zero vulnerabilities); private-source and secret scans; and a fresh real-browser instance with inspected screenshots and zero console or network errors.