Function strict_mode_enabled 

pub fn strict_mode_enabled() -> bool

Whether strict mode is on, read from STRICT_ENV_VAR.

Deliberately an environment variable rather than a separate validate_with_tools_strict entry point. The call sites that matter are the generated-code assertions in tests/tool_validation.rs, and the property we want is “CI checks every language, a laptop checks what it can” – with a second entry point every one of those call sites would have to branch on the environment itself, which is precisely the per-call-site policy decision that let the original None-is-a-pass bug spread to nine places. One switch, read in one function, cannot drift.