Keel Defaults compatibility with REEID Translate

Plugin capabilities

• Provides a “Settings → Site Defaults” interface where each security/hardening default is a switch that can be turned on or off individually.
• Implements core vulnerability awareness by querying WordPress.org’s core stable-check API to identify known-insecure installed core versions and the same-line patched release; an authorized admin can install the same-line patch via WordPress’s upgrader with rollback enabled, and the target is re-checked server-side before offering/installing.
• Enforces strong password screening (when the corresponding default is enabled) by checking new/changed passwords against Have I Been Pwned’s Pwned Passwords range API using k-anonymity (only the first five characters of the SHA-1 hash are sent); failures/unreachable/malformed responses cause the check to be skipped (password allowed) and are recorded/reported in Site Health without storing the password or hash prefix.
• Suppresses outgoing email on non-production environments by default (based on `WP_ENVIRONMENT_TYPE` or host-name fallback), while doing nothing on production; includes admin notice behavior and supports overrides via `KEEL_ALLOW_NONPRODUCTION_MAIL` or `keel_suppress_nonproduction_mail` filter.
• Hardens/controls presentation and access defaults including sending `X-Frame-Options: SAMEORIGIN` by default (with an option to leave frame options unchanged) and disabling comments/trackbacks/pingbacks such that they are actually disabled at the data/query level (e.g., `get_comments()` returns nothing).
• Supports Multisite by seeding defaults across existing and newly created sites when activated network-wide, with Super Admin control under “Network Admin → Settings → Network Policy” and per-site saved values preserved underneath locked policy application.