Repository navigation
docs: resolve duplicate minutes and document public CI evidence - #242
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
1 participant
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.
Resolve the duplicated June/July 2025 minutes using the original publication history: PR #230 called them July minutes, and PR #231 explicitly corrected June to July. Preserve the June URL as a pointer and retain the July record as canonical.
Add dated public CI workflow examples for all six libraries, distinguishing tests, documentation and static analysis without asserting provisioned capacity. Add an on-demand advisory external-link review with separate missing/restricted/transient classifications.
Validation: structure and file-link checks pass; all eight unit tests pass. Live report checked 60 guidance/index URLs with no 404/410 responses; remaining responses were access restrictions. Original PRs and cited successful workflow records were verified through GitHub. PDFs are unchanged.
The user explicitly authorized continued pushing and merging. An administrator merge may satisfy the separate-review requirement after automated checks pass; it is not an independent CODEOWNER approval.