Repository navigation
Require preactivation channel and schedule-set review; release 0.17.0 - #53
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.
Require independent Reporting Channel Set approval in Step 1 and verify exact approved channels, authority, evidence, and effective coverage at Step 3 cutover. Review the complete Program Obligation schedule set, including active rules and proposals, with explicit adoption, replacement, retirement, and inapplicability decisions before content activation. Browser, HTTP, CLI, and direct-file validation use shared readiness checks.
Model v12 adds authoritative schedule dispositions and a preview/apply migration that preserves existing operating records. This breaking release coordinates both packages at 0.17.0. Existing Policy, Document, Training, retention, and scope approval checks remain in place.
Validation: Node 24 full
CI=true npm run validate; focused temporal, exact-revision, replacement, exclusion, and cross-Program regressions; fresh consumer generation with the local package; package dry runs; npm audit; changed-file secret scan. Independent combined code and security review completed with no unresolved findings.Playwright verified proposal approval after an unrelated commit, complete schedule review with a legitimate replacement, independent Control oversight, rejection of activation before channels become effective, and successful cutover on the covered date. The local validation server was stopped after inspection.