Repository navigation
Conversation
biswaroop1547
approved these changes
Oct 9, 2026
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 docs currently say Pro includes confidential inference, describe removed Agent/admin screens, and include Agent API fields the released backend rejects. This pass aligns the guides with the current product and live Clerk catalog. It keeps the future pricing redesign out of the current-plan documentation.
Evidence baseline: backend
01d433396ef225d085abafe9993ebc1855fab213from the October 6 production release manifest; frontend1fc72ba8b8b209a94c087491b6055e7c0757f5e7; admin production2e20d2cd3e7272b6e06ab168eca4125cd500dcc2; production Clerk catalog read October 8. Agents visibility remains beta/deployment dependent. All 54 original MDX pages were reviewed; 42 needed changes, including removal of the retired Telegram guide, plus navigation, diagram wording, redirects and AGENTS guidance. Telegram retirement is confirmed by the product owner; retained backend code is not evidence of availability.Validation: production build / TypeScript / 164 static outputs; all 53 remaining MDX pages, 3,403 internal links, anchors and assets, and 30 JSON examples pass. Removed Telegram routes are absent from generated pages, navigation, search and LLM exports; all three new redirects return 301 and their destinations return 200 under local Cloudflare Pages. The original audit also checked Agent request/response examples against deployed Pydantic schemas, 14 desktop/mobile Chromium views and seven Markdown exports. No product writes or inference calls.
Review boundary: existing team-confirmed SOC 2 Type II, open-source-only and account-deletion policy statements are retained. This documentation audit does not independently certify effective provider overrides, third-party retention, or deletion across every store/backup. Dated release notes retain their workflow-managed history. No product runtime or billing behavior changes.