Repository navigation
docs: align public OpenAPI with corrected MCP API contracts - #126
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.
Regenerate the existing public OpenAPI documents from PlatformBackend 00a635440eea357a9e7add2ae7b734e345d0d605. Eight request schemas had drifted from their source, and the MCP contract audit identified additional source fixes now included here.
Uses the repository's
load_services,sync_openapi,merge_openapi_specsand generated-tree validation functions. Output is restricted to the existing public service/path set: 11 files change, covering 22 operations and 13 request-body schemas. No new private operation, navigation entry or translated guide is published.Validation:
Companion: https://github.com/AceDataCloud/PlatformBackend/pull/2250. Merge/publish after the backend contract release. Updated source guides in that companion follow the normal DB source-hash and translation-readiness workflow; this PR does not bypass those publication gates. No production sync or deployment was performed.
Related audit fixes: