Add request-scoped service contexts for embedded memory applications - #204
Draft
Coding-Dev-Tools wants to merge 2 commits into
Draft
Add request-scoped service contexts for embedded memory applications#204Coding-Dev-Tools wants to merge 2 commits into
Coding-Dev-Tools wants to merge 2 commits into
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
1 participant
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.
Embedded HTTP and MCP operations can now resolve an explicitly bound memory service and principal without changing the standalone service singleton. A required context refuses the local fallback, and nested contexts restore the prior service and identity even when an operation fails.
This is the public engine integration point for the private hosted Team runtime. Commercial authorization remains in the cloud service.
Validation: 26 focused service-context, v2 binding and MCP contract tests; Ruff; commercial boundary manifest; candidate wheel build. The private runtime also exercises concurrent organizations with identical workspace names through this binding.