Repository navigation
docs: refresh public guide and documentation links - #3
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.
Replace stale waitlist and product copy with a current public guide: web/MCP/CLI entry paths, platform capabilities, PR gate behavior, tool licenses, examples, deployment preview status, and partner documentation. Repair getting-started links and support guidance, and add a pinned weekly/PR link check.
Validation: reviewed the documentation diff, checked whitespace and added-content secret patterns. No runtime behavior changes. Both public entry-point link checks passed locally using Lychee v0.24.2, including fragments; workflow YAML parsed successfully.