Skip to content

docs: use canonical public sites in active guides - #71

Merged
anycodes merged 2 commits into
mainfrom
docs/canonical-guide-links-20261019
Oct 19, 2026
Merged

anycodes merged 2 commits into
mainfrom
docs/canonical-guide-links-20261019

Conversation

@anycodes

@anycodes anycodes commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

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

  • Documentation

Changes

  • Correct active English/Chinese links; preserve historical archive/design records and runtime endpoints.
  • Add current owner evidence/CHANGELOG and reconcile the accepted CLI release-boundary record lifecycle where applicable.

Testing

  • Canonical website/registry HTTP200, existing bilingual public content and provider archive hashes independently verified.
  • Repository health/hygiene/diff checks PASS (exact counts in evidence).
  • Latest-head hosted CI and merge review

Checklist

  • Scope is documentation/records only; no runtime, dependency, DNS, release, credential or visibility change.

Definition of Done

  • Bilingual guides/CHANGELOG and own .agents/ verification/decision records included.
  • No new cloud/model test for link-only edits; existing product acceptance is preserved as immutable history.

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.

@anycodes
anycodes merged commit d4d93e8 into main Oct 19, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant