A repository's oracle route that cannot apply takes the configuration or the person's setting down: a route in .abcd/config.json naming a model a configured keyless provider does not list refuses the whole provider configuration load (every command that reads it fails), and a route there naming a provider this machine has not configured wins over the machine's own route of the same name, so the role runs on the host and displaces the person's setting. Both disagree with ruling CD2's shape for a repository's route (skip with a diagnostic, the machine's route applying in its place).

A repository's oracle route that cannot apply takes the configuration or the person's setting down: a route in .abcd/config.json naming a model a configured keyless provider does not list refuses the whole provider configuration load (every command that reads it fails), and a route there naming a provider this machine has not configured wins over the machine's own route of the same name, so the role runs on the host and displaces the person's setting. Both disagree with ruling CD2's shape for a repository's route (skip with a diagnostic, the machine's route applying in its place).

Grounds

• pursued: LoadAPI loads with one diagnostic and the machine's route in force for both cases (TestARepositoryRouteToAnUnlistedModelIsSkipped, TestARepositoryRouteToAnUnconfiguredProviderYieldsToTheMachineRoute); a machine route to an unlisted model or a denylisted model from the repository still refusing shows the skip is not a softening, and a refusal or a host fallback in either new test would show it wrong