v1.0.2 - 2026-07-21

[1.0.2] - 2026-07-21

Changed

• Bumped the devcontainer's base image from mcr.microsoft.com/devcontainers/python:3.13 to :3.14, and
  requires-python from >=3.13.2,<3.14 to >=3.14.2,<3.15 (.python-version from 3.13 to 3.14),
  to track current homeassistant (2026.7.2, up from 2026.2.3) and
  pytest-homeassistant-custom-component (0.13.346). Verified with a real uv lock/uv sync/pytest
  run (single resolution, no pymicro-vad/pyspeex-noise, 148 passed, 100% coverage) plus ty check and
  ruff — no breakage from the version jump.
• Raised the minimum supported Home Assistant version declared in hacs.json and the README's Requirements
  section from 2024.6.0 to 2026.7.2, matching what the dev/test harness now actually verifies — the old
  floor was carried forward from before this project had any test coverage against it, and there's no
  ongoing verification that anything between 2024.6.0 and 2026.7.2 still works.
• Removed test-only workarounds that existed solely for running pytest on native Windows, now that dev/test
  runs exclusively inside the devcontainer (#67): the HassEventLoopPolicy._loop_factory/SelectorEventLoop
  patch and the socket.socketpair() TCP-emulation shim in tests/conftest.py (both gated behind
  sys.platform == "win32", so pure dead code once tests never run on Windows), and the
  mock_client_session fixture in tests/test_config_flow.py (verified empirically that all 19
  test_config_flow.py tests still pass without it — the real network-call protection it was layered on top
  of is already handled by the separate per-test fetch_feed_data mock). homeassistant itself is moving
  the same direction (homeassistant.runner now imports POSIX-only stdlib modules unconditionally — see the
  entry above), so maintaining Windows-specific test scaffolding no longer serves any purpose.