Bottle compatibility precedence across overlapping macOS version ranges

When a formula provides multiple pre-compiled bottle candidates with overlapping but non-identical macOS version compatibility, Homebrew's mechanism for selecting a single optimal bottle is not explicitly documented. The stated resolution logic references the current macOS version and architecture, but does not address how minor version differentials, build‑version suffixes, or arm64/x86_64 hybrid targets influence candidate prioritization.

This ambiguity arises when a user's system version falls between declared bottle compatibility ranges, creating uncertainty about whether Homebrew will select the newest compatible archive, the most restrictive version match, or fall back to compilation from source.

• Does Homebrew prioritize the newest compatible bottle when multiple candidates satisfy the architecture requirement?
• Are bottle candidates sorted by macOS SDK version, chip architecture specificity, or a secondary checksum tiebreaker?
• If multiple candidates satisfy the architecture requirement, what specific condition triggers the fallback to source compilation?