fix: prevent KeyError when setting up lock after previous deletion

[raman325]

Proposed change

When a lock entry is deleted, delete_coordinator() removes hass.data[DOMAIN] after a 20-second delay. If the user creates a new lock entry before or after that cleanup fires, async_setup_services() crashes with KeyError because it assumes hass.data[DOMAIN] exists.

Two fixes applied:

1. services.py — Added hass.data.setdefault(DOMAIN, {}) before accessing hass.data[DOMAIN], so the dict is recreated if it was previously removed.

2. __init__.py — Added a guard in delete_coordinator() to skip domain data removal if new config entries already exist (handles the race condition where the 20-second delayed cleanup fires after a new entry is set up).

Type of change

• Bugfix (non-breaking change which fixes an issue)

Additional information

• This PR fixes or closes issue: fixes ISSUE: Python KeyError during lock setup #593
• This PR is related to issue:

🤖 Generated with Claude Code

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 90.06%. Comparing base (cdb4922) to head (551d48c).
⚠️ Report is 75 commits behind head on main.

Files with missing lines	Patch %	Lines
custom_components/keymaster/__init__.py	50.00%	1 Missing ⚠️
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #595      +/-   ##
==========================================
+ Coverage   84.14%   90.06%   +5.91%     
==========================================
  Files          10       28      +18     
  Lines         801     3471    +2670     
==========================================
+ Hits          674     3126    +2452     
- Misses        127      345     +218     

Flag	Coverage Δ
python	90.06% <66.66%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

Fixes a race condition in the Keymaster Home Assistant integration where hass.data[DOMAIN] could be removed after deleting the last config entry, causing a KeyError during subsequent lock setup (issue #593).

Changes:

• Ensure async_setup_services() recreates hass.data[DOMAIN] when missing to prevent KeyError.
• Guard delayed coordinator cleanup so it won’t remove domain data if new config entries already exist.
• Update/add tests for the hass.data[DOMAIN]-missing scenario, and add new strategy-config-validation plan/design docs.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
custom_components/keymaster/services.py	Recreates hass.data[DOMAIN] defensively before accessing it.
custom_components/keymaster/__init__.py	Prevents delayed cleanup from removing domain data when entries exist (race guard).
tests/test_services.py	Adds coverage to ensure async_setup_services works when the domain key was popped.
tests/test_init.py	Adjusts a test that previously relied on the KeyError behavior (now fixed).
docs/plans/2026-03-10-strategy-config-validation.md	Adds a large implementation plan document (appears unrelated to this bugfix PR).
docs/plans/2026-03-10-strategy-config-validation-design.md	Adds a design doc for the same strategy-validation work (also appears unrelated here).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.