Repository navigation
Separate the MCP service from engine automation - #9
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.
Summary
Separate the standard MCP service from engine domain implementations. The service uses the standalone Automation SDK to discover and invoke the engine Host, while keeping protocol sessions, long-running work and signal reporting under explicit lifetimes.
Changes
0945959a4b527a1cd8db496d86cc70fa13ec0661.Validation
This requires the companion engine Automation Host. It is a breaking service update and does not publish a tag or release package. Client configuration and protocol checks are distinct from end-to-end testing inside every supported client application.
Companion engine pull request: ChenlizheMe/Infernux#106.