Repository navigation
Add authenticated capability discovery and complete API contracts - #51
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.
Dashboard backends can discover the authenticated credential's effective permissions and allowed endpoint templates through GET /capabilities and /v1/capabilities. Discovery performs no database reads or runtime probes, never lists other integrations, and distinguishes operations that can change domain/lifecycle state or migrate the database.
Stacked on #50; the diff contains only capability discovery and contract completion.
Verification: 63 capability, repository-contract, operator-interface and module-size tests passed. A separate 42-test capability/integration/diagnostic run passed. Targeted Ruff, mypy, Bandit and git diff --check passed. No live Olymp deployment or tunnel test was performed.