v0.1.5 — Fix disable_automations default, add config flow toggles

Fixes

Root cause

The Voluptuous service schema in __init__.py still had default=True for disable_automations. When the card sent an empty payload {}, the HA backend schema validation filled in True before the handler ran — undoing the earlier fix.

Changes

• Service schema default: disable_automations changed from True → False (the proper fix)
• Config flow toggles: Visual on/off switches in Settings → Gatekeeper HA → Options:
  • Disable automations when guest mode activates (default OFF)
  • Disable scripts when guest mode activates (default ON)
  • Disable scenes when guest mode activates (default ON)
  • Apply safe states in guest mode (default ON)
• Internal defaults: guest_mode.py method defaults changed to match service defaults
• Blueprint: disable_automations is now a configurable blueprint input (defaults true for lock-code users)
• Translations: Added for the new config field

Upgrade path

1. Update via HACS (or copy custom_components/gatekeeper manually)
2. Restart Home Assistant
3. Browse to Settings → Gatekeeper HA → Options to configure your defaults
4. Clear browser cache to pick up the new card JS

Fixes #17 (gatekeeper-card), Fixes #54 (gatekeeper-ha)