What is the Ruby "ancestors" chain and how does method resolution order (MRO) work with multiple included modules?

A Ruby checks only the immediate class, ignoring modules entirely B Ruby searches the ancestors array (class, then included/prepended modules, then superclass and its modules, etc.) in order, with later includes taking precedence over earlier ones for method lookup C Modules are always checked before the class itself, regardless of include order D MRO is randomized at runtime