design: the ecosystem consumer resolves for three targets on the released engine - #547
Merged
Conversation
…ased engine Section 13.3 recorded one target. The release changes what `[xlings]` accepts and when a runner is consulted, and neither is target-scoped, so the criterion that it narrowed nothing has to name more than the target it was written for.
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
2 participants
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.
Documentation only, against the 2026.9.2.1 design record.
Section 13.3 recorded the openkal consumer for one target. The release changes what
[xlings]accepts and when a runner is consulted, and neither is scoped to a target, so the claim that it narrowed nothing has to name more than the one target the runner verification used.Measured in the same sandbox SubOS, on the published 2026.9.2.1: