Krikri::CollectionIndex::Resolution

Would the real controller resolve name (exactly as a task wrote it) to an existing module file? Follows real's own rules: ansible.builtin./ansible.legacy. spellings, builtin files, ansible_builtin_runtime.yml redirects, collection meta/runtime.yml redirects (chained, cycle-limited), the collections: keyword's listed collections, and role/playbook-private library/ modules. Returns false ONLY when a needed directory/file is definitely absent from every path real would search - nil means unsure (missing ansible-core installation, unreadable runtime data, redirect cycle), and the caller keeps the permissive path.

A name that dies on a collection that cannot be imported refuses SILENTLY: ansible-core 2.21's loader catches the ImportError while it reads that collection's routing metadata (2.19 let it escape, which is where the "Error loading plugin '<name>': No module named ..." [WARNING] line came from), so real prints no warning ahead of the refusal and resolution carries no text for the caller.