Repository navigation
Fix finalized Markdown companion history checks - #97
Merged
Merged
Conversation
This was referenced Oct 28, 2026
Merged
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.
Finalized meeting proof could fail validation after commit because minutes were compared with the historical agenda. Match each Markdown companion by its stable model name so distinct sections validate against their own committed bytes.
Preserve exact content and presence checks. Regression coverage commits meeting proof before validation and rejects each section’s edits, removals, and late additions, with single-section and extended layout coverage. The fix is released in 0.21.5 after the Git compatibility follow-up in #98 and release coordination in #99. No data-model migration is required.
Validation: Node 24 full
CI=true npm run validate; focused committed-history tests; clean install, both package inspections, npm audit, generated consumer (224 resources, zero errors or warnings), private-source and credential scans. An isolated synthetic workspace was checked through the real browser and API: distinct agenda/minutes remain valid, while a real minutes rewrite is rejected. Three independent combined code and security review passes found no actionable issues.Released: FileGRC 0.21.5. Publish and installed consumer smoke passed.