Which conda channel priority rule determines package selection when identical versions exist across channels?

Goal: Identify the deterministic rule conda applies to prioritize channels when multiple channels host the same package version, ensuring that useful alerts remain active while minimizing unnecessary notification noise.

Constraint: Preserve existing conda settings such as notify_outdated_conda false and verbosity ERROR, and avoid disabling critical update notifications, while clarifying how channel order influences solver decisions without manual intervention.

Questions:

1. Which conda configuration can enforce a preferred channel order for identical packages?
2. Does the channel priority logic respect the order defined in .condarc or rely on internal defaults?