Repository navigation
Defer workflow-step imports until registry assembly - #194
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Importing
infermatrix_copilot.engine.stepscurrently imports all eight workflow domains immediately, including mutation steps, even when a caller only needs the registry facade. This defers those vetted imports untilregister_builtin_stepsassembles a registry. Step decorators and names remain with their definitions, and each new registry still receives the same built-in set. A subprocess test checks that package import is inert and explicit assembly loads the domains.The step SPEC and architecture tour now describe the actual import boundary. Validation: 83 focused assembly/engine/review tests, 1,529 full local tests, and strict SPEC freshness (79 declared-verified pages, no stale or uncovered modules). The local environment lacks the optional
buildmodule, so the repository CI is the installed-wheel gate.