Release 0.2.3

Bump the manifest to 0.2.3 for the stale-room policy: unusable room
sensors are left out with weights re-normalized, and an opt-in checkbox
keeps a stale sensor's last value for up to 24 hours. 0.2.2 was never
deployed, so the changelog marks it as such and the 0.2.3 notes point
0.2.1 users at both entries. ROADMAP and AUDIT record the decision and
the open control-design questions (minimum weight coverage, outdoor
temperature outages).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

AUDIT.md

@@ -206,3 +206,22 @@ resets the relay's `last_changed`, so continuity cannot be verified anyway).
 **Verification.** `sh scripts/check.sh` passes in both test environments (pip
 check, 65 offline tests, 18 HA Core tests, compilation, package/translation/changelog
 checks, `git diff --check`). The offline tests also pass on Python 3.9.6.
+
+
+## 0.2.3 — stale-room policy
+
+Decided by the user: pausing everything because one room sensor is unusable is
+not acceptable for future control. An unusable room is now left out and the other
+rooms' weights re-normalized; an opt-in checkbox keeps a stale sensor's last value
+for sensors that report only on change. Two safeguards were added: the keep-last
+option stops after 24 hours without a report, and Status exposes `excluded_rooms`
+and `weight_coverage`, so a forecast based on a small share of the comfort weight
+is visible.
+
+Open for the control design: a minimum `weight_coverage` below which the MPC must
+not decide, and the outdoor-temperature outage policy (still pauses). Simulated
+two-hour bedroom outage: the other room kept learning (7 → 25 samples, previously
+frozen at 7) and the bedroom resumed one poll after reporting again.
+
+**Verification.** `sh scripts/check.sh` passes for HA 2025.12.0 and 2026.2.3 (69
+offline tests, 18 HA Core tests). The offline tests also pass on Python 3.9.6.