docs: add bot platform capability guide - #5115
Open
Pr1p wants to merge 1 commit into
Open
Conversation
Generated-by: Codex
Pr1p
force-pushed
the
codex/docs-bot-platforms
branch
from
September 10, 2026 11:08
6556114 to
394df53
Compare
Pr1p
marked this pull request as ready for review
September 10, 2026 11:10
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.
Summary
Refs #3894.
Adds synchronized English and Chinese documentation for the eight current bot platforms, including a source-derived capability matrix, provider setup guidance, security boundaries, limitations, and a repeatable live-validation checklist. This is a documentation-only change; it does not change runtime behavior.
Verification
git diff --check: passed@Makareply, content preservation, and post-restart group reply passed@Makaround trip and exact reply content passed; a system-level TUN route was required for the Gateway WebSocketcontext_tokenand sends an empty token for outbound replies, so the documentation records this implementation risk instead of claiming live support.No credentials, user IDs, or raw provider payloads are included. Restart recovery, duplicate suppression, group behavior where not tested, and scheduled delivery remain untested in the live smoke entries.
AI use
Tool(s) and scope:
Codex was used for source review, documentation drafting, platform smoke-test recording, and verification.
Checklist
Does this PR entail a change in behavior?