Under the hood
Standard default model resolution no longer short-circuits under a certain guard condition
What
The internal function that determines the standard default model kind used to return early with no model (null) when a particular guard condition held. That early return has been removed, so the function now always falls through to the standard-model branch when there's no recognized organization default.
Why
This means a case that previously resulted in no standard model being selected will now fall through to picking the standard default model instead, when there's no recognized org-level default.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What condition the removed guard checked for, and which users or scenarios it applied to, is not stated.