Probe and prioritize module-native runtimes across framework folders - #791
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cee152c461
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 14a6ca0224
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Summary
Why
Multi-target modules can legitimately place runtime assets under more than one
Lib/<framework>/runtimes/<rid>/nativetree. The existing bootstrapper searched only the active managed framework folder. The first revision discovered fallbacks, but a repeated import could leave an already-present fallback ahead of the newly active framework. The generated handlers now remove every module-owned candidate from the existing PATH and rebuild the prefix in the intended order while preserving unrelated entries.Validation
ModuleBootstrapperGeneratorTestspass on the final head