Repository navigation
fix(agent): align the blue_cell export with the decepticon.agents discovery contract - #9
Merged
Merged
Conversation
…discovery contract
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.
The Decepticon graph registry discovers plugin agents under the
decepticon.agentsentry-point group, and its loader contract requires a module-levelgraphattribute (module:graph). Two alignments:decepticon.graphs(introduced in the gateway PR) to the existingdecepticon.agentsgroup thatdecepticon_core.plugin_loader.load_plugin_agents()already discovers — no Decepticon-side registry changes needed.__getattr__(lazy compiled graph) instead of a factory function — the discovery contract wants the attribute, and laziness keeps the model env read at resolution time. Verified:mod.graphresolves toCompiledStateGraph.