Repository navigation
docs: clarify CI inventory and repair specification and meeting records - #241
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.
Clarify previously reported CI requirements and capacity, identify unverified availability and missing support information, and remove retired specification destinations from editable pages. Flag the duplicated June/July 2025 meeting records for source verification without inventing a corrected date. Repair historical RST formatting and point current specification proposals to the dynamic specification and project documentation.
Add RST rendering, dated-record index coverage and retired-specification reference checks to documentation CI. Local checks and all five tests pass. No PDFs or other presentation binaries are changed.
The user reviewed the internal-page comparisons, requested the specification-reference sweep, and explicitly authorized pushing and merging. Administrator merge may satisfy the separate-review requirement after automated checks pass; this is not an independent CODEOWNER approval. No protection settings will be changed.