Honor host account availability for explicit child provider preferences - #412
Merged
Brian Krabach (bkrabach) merged 2 commits intoSep 24, 2026
Merged
Conversation
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
1 participant
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.
An explicitly selected unavailable account or an exhausted model preference currently can leave the parent default selected. Add an opt-in synchronous provider.check_available capability to the child preference boundary: check the exact Core instance_id before exact/model-glob resolution, allow only the declared preference chain to fall back, and raise when exhausted instead of silently keeping another account. Hosts without the capability retain current behavior.
Core instance_id now precedes legacy id in lookup and promotion. Cancellation and an invalid async policy callback cannot authorize a provider or trigger account fallback.
Validation: 118 provider-availability, spawn utility, spawn contract and configuration-isolation tests passed. Tests cover same-module accounts, preserved input plans, exact/glob failures, explicit fallback, no-match, legacy behavior, cancellation and callback contract violations. This is a prerequisite for Unified issue182, not host adoption or deployment.