Krikri::RemovedModuleError

A tombstoned-removed module name whose tombstone carries its OWN custom removal message ("The 'community.docker.docker_compose' module has been removed. ..."). Ansible refuses the WHOLE playbook at LOAD time for one of these - probed against ansible-core 2.19.11: rc=1 (NOT the generic couldn't-resolve rc=4), zero tasks run including Gathering Facts, "[ERROR]: <message>" plus the offending task's Origin block on STDERR - the same load-time refusal even when the offending task sits behind when: false. (This used to read "raises that at RUN time", when the engine only hit the tombstone for names that resolved to nothing; the table's collection-wide extension and the resolved-name-first check moved the refusal to match real's load-time shape.) Carries the rendered stderr block ([ERROR] line + Origin + 3 context lines + caret) built at the raise site for krikri-playbook.cr to print verbatim; nil renders message-only. The render getter and constructor are inherited from UnresolvedModuleError - a local initialize here that called super(message) would wipe the render UnresolvedModuleError's own initialize assigns.