Repository navigation
docs(reference): synchronize the public module catalog - #26
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.
The generated module catalog retains older Memory and UI Kit descriptions. Regenerate it from the current public module manifests, with matching provenance in the companion docs-site change.
Validation: the source synchronization check fails before regeneration and passes afterward; all 60 site tests, strict build, rendered links, content audit, and secret scan pass; the focused documentation workflow scenario passes on SQLite and PostgreSQL.
Compatibility: documentation only; runtime contracts and stored data remain unchanged.