Repository navigation
Fix operating proof and activation windows; release 0.19.1 - #81
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.
Completed occurrences could freeze current Controls and ongoing reviews through Evidence source links, and activation-based review windows offered by the planner could fail validation. Preserve explicit operating proof against its first finalized Git snapshot while allowing current source context to evolve, and share recurrence/window calculations across planning and validation. Historical windows are rechecked in their original committed governing context.
Includes coordinated 0.19.1 package versions and regressions for superseded proof, rewritten completions and attachments, later cutovers, month-end cycles and leap-day recurrence.
Validation: four independent combined code/security review passes; Node 24 full
CI=true npm run validate; both package dry runs; npm audit; fresh local-tar consumer validation (224 resources, zero errors/warnings). Playwright exercised Control JSON and Markdown saves plus an October 23–November 22 completion in dedicated local instances; no browser errors, and the instances were stopped.