Repository navigation
Add typed AI resource workflows with human plan review - #230
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.
Adds resource-family discovery and safe metadata reads, plus typed Stack,
Service and Container plans for basic creation, metadata and lifecycle
operations. The existing seven tools and ordinary UI/API permissions remain
intact. Advanced forms and other families remain explicitly pending.
Human review shows exact changes and mounted-data warnings, supports cancelling
unsubmitted plans, and cannot be performed by a bridge Key. New messages and
review controls are translated in all 13 locales. Versions are Web Console
1.6.198 and bridge 0.2.0; dependency graphs are unchanged.
Focused source validation passed: resource core 24 cases, UI 5, locale rendering
2, negative contract 5, the cross-repository wire contract, syntax and diff
checks. Required CI/artifact checks and candidate browser, role/cross-ID and
live lifecycle acceptance remain separate gates. This does not claim complete
frontend WebMCP coverage.