#Make assumptions executable

IronShim-rs works best when compatibility assumptions are represented as narrow contracts rather than ambient folklore.

#Contract surface

The interface names the host expectations, guest-visible behavior, and recovery paths independently.

#Maintenance pressure

Compatibility layers age poorly when the boundary is implicit. The design goal is to keep every translation point inspectable.

#Result

The crate becomes easier to test, easier to review, and less dependent on accidental agreement between layers.