Repository navigation
Separate obligation snapshots, period coverage, and waiting work - #93
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.
Recurring point reviews could stay Due until a future population cutoff even after their work was recorded. Add an explicit review-date snapshot criterion, separate whole-period proof coverage, and a neutral Waiting state shared by planner, CLI, API, workflow, audit checks, and browser. Whole-period work remains open through its inclusive final day; new or unresolved members restore actionable work.
Add a previewed, revision-bound rule correction that creates a reviewed successor and retains supported historical member rows, original windows, deadlines, approvals, and proof. Existing rules keep their semantics. New fields require explicit adoption of the 0.21 compatibility line, with model v13 unchanged.
Validation: clean independent combined code and security review; Node 24 full release validation; fresh generated consumer validation; both package-content checks; npm audit (zero vulnerabilities); private-source/secret scans; native committed-history correction rehearsals; and real-browser observation-date, correction preview/apply, reconciliation, and whole-period waiting checks with no browser errors.