release: v0.15.1.0.1 — classify the LangGraph gateway under the backend architecture policy - #13
Merged
Merged
Conversation
…nd architecture policy
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.
Brings
zeroth.core.langgraph_gateway(14 modules) under the backend dependency policy.LEGACY_DOMAIN_PREFIXES: the package root (and its service-plane modules, including the newenforcement/enforcement_store) →service;models/inventory→contracts;capabilities/events→governance.TEMPORARY_EXCEPTIONSentries, each with a removal task tied to the gateway relocation phase (ZER-24): the governance decision service's reuse of the admission orchestrator, and the LangGraph integration client's reuse of the enforcement surface.Full suite green locally in the pre-commit gate: 5812 passed, 4 skipped.