Repository navigation
docs: use canonical public sites in active guides - #71
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.
Description
Active bilingual documentation indexes/provider guides still link to the .com registry, which does not resolve from the release-review environment, and the older .com website. Use the verified canonical .cn destinations consistently, including CLI engine/installation references where applicable.
Type of Change
Changes
Testing
Checklist
Definition of Done
.agents/verification/decision records included.Evidence:
.agents/evidence/verify/2026-10-19-canonical-guide-links.md. Normal Registry documentation aggregation must read the accepted source after merge; a green PR alone does not prove the live docs updated.Also correct the catalog module introduction docstring. Its executable REGISTRY_INDEX was already canonical and remains unchanged; no behavior change or cloud rerun is needed.