Repository navigation
Align starter monthly and quarterly schedules with calendar periods - #107
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.
Starter monthly and quarterly rules previously inherited the setup date, so a quarterly review completed in October could be followed by another window opening in November. New monthly rules now start on the first of the month, and quarterly rules start at calendar quarter boundaries. Annual and activation-based schedules retain their anchors.
Existing approved rules are unchanged. Document the normal reviewed-successor route for aligning them while preserving completed occurrences and avoiding duplicate work in an already completed period. Prepare coordinated patch release 0.21.13 with no model migration.
Validation: full
CI=true npm run validatepassed on Node 24.22.2; focused generator tests passed; fresh generated workspace validated with 224 records and zero diagnostics; Playwright verified monthly and quarterly rule pages with no console errors or failed requests. Both package dry runs and npm audit passed. One independent combined code and security review found no actionable issues.