Repository navigation
doc: add contract doc for rfc 1299 - #1361
Merged
Merged
Conversation
4 of 29 tasks
7 tasks done
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.
Which issue or RFC does this PR close?
This PR does not close #1298. It documents the contract from RFC PR #1299, which tracks issue #1298.
Rationale for this change
The host-visible integration diagnostics contract needs a single documented reference so plugin implementations and reviews use the same failure classifications, output format, privacy rules, fail-open behavior, and deduplication expectations.
What changes are included in this PR?
docs/en/development/plugin-contract.mddocs/zh/development/plugin-contract.mdzensical.toml.authentication_failed,version_mismatch,server_unavailable, andinvalid_responseAre there any user-facing changes?
Documentation-only change. There are no runtime, API, persistence-format, or migration changes.
How was this change tested?
The strict documentation build completed successfully with no issues.
AI usage statement
This documentation was prepared with OpenAI Codex using the GPT-5 model. The final scope, wording, links, and documentation build were reviewed in the repository.