Repository navigation
ci: aggregate package validation and align documentation identity - #21
Merged
Merged
Conversation
showxu
added a commit
that referenced
this pull request
Oct 12, 2026
* ci: aggregate package validation and align documentation identity * fix: validate local reusable workflow references
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.
The package CI now reports one stable result covering repository quality, the compiler matrix, Windows products and runtime, and the real AppServer/MCP binary integration. It adopts the shared source policy. Binary integration is called by the main CI once; its separate scheduled and manual entry points remain available.
Apply the family logo and purple identity to all eleven module landings, add the canonical review rules, and make release preparation use a reviewed PR and accepted merge commit. Published release history, notices and API behavior remain unchanged.
Validation: existing local validation passed both build systems (359 tests in 55 suites each), API checks and all eleven DocC builds; that evidence is reused. Changed workflows and whitespace pass. Required hosted checks remain enabled; the integration check now appears beneath its reusable caller and its ruleset name must be aligned after that check succeeds.