v0.3.5

Added

• allow_type_mismatch flag for case() and cases() APIs to enable type mismatch violations (e.g., string instead of int) when generating invalid examples
• Support for TYPE_MISMATCH violation in planner and generator — becomes an available option alongside semantic constraints when the flag is enabled
• Type mismatch semantics factory in resolver module for generating incorrect-type values
• Validation guard: raises ValueError when allow_type_mismatch=True is combined with valid=True

Changed

• bool and object fields can now be violated via type mismatches when allow_type_mismatch=True; NotImplementedError is raised only when attempting to violate these types with allow_type_mismatch=False (no semantic constraints available)