You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ It gives you:
58
58
59
59
Current release: **v2.0.7**.
60
60
61
-
v2.0.7 is the stable release line prepared from `senyo888-patch-1`; v2.0.6 remains the previous stable release on `main` until promotion, tagging, and GitHub release publication are completed.
61
+
v2.0.7 metadata is present on `main`; `senyo888-patch-1`remains the final staging lane for release-validation fixes until those fixes are promoted. HA Lab advisory validation for commit `55dc2b9` passed on 2026-06-23 after the lab-only package deploy and manual restart. Tagging and GitHub release publication remain gated until final validation, promotion, and maintainer approval are complete.
62
62
63
63
---
64
64
@@ -348,6 +348,8 @@ must be reviewable from tracked repository files.
348
348
- PM2.5 aggregate runtime truth now exposes canonical `pm25` aggregate entity IDs when PM2.5 telemetry is configured, including setup-time normalization for existing `pm2_5` aggregate IDs
349
349
- generated-card validation now checks entity references embedded in exported YAML, so stale Manual-card entity IDs are caught by `self_check` / `v205_release_check`
350
350
- generated-card validation now includes entity references embedded inside generated-card JavaScript/string expressions, not just YAML `entity:` rows
351
+
- generated-card release validation now filters JavaScript service names, predicate prefixes, object properties, and entity-prefix strings so false-positive card fragments do not fail release checks
352
+
- HA Lab advisory validation passed for commit `55dc2b9` with identity, HI presence, scenario-matrix read-only baseline, and Stage 3 six-sensor runtime-readiness checks; this remains lab evidence, not release authority
351
353
- PM2.5 aggregate entity-ID normalization now reports blocked canonical-target conflicts through diagnostics, `self_check`, and `v205_release_check`
352
354
- generated V2 Current Air Control cards keep selected command lanes in the chip row while moving unmapped alert/no-automation context into reason text
353
355
- generated V2 Current Air Control cards now render backend `telemetry_unavailable` as explicit degraded state and avoid falling back to `normal` / `READY` when the mode sensor is missing or unavailable
@@ -821,6 +823,8 @@ CO emergency pressure. Details are in
821
823
- fixed PM2.5 aggregate runtime truth so configured PM2.5 telemetry exposes canonical backend-owned PM25 aggregate entities instead of relying on Home Assistant's dotted `pm2_5` name slug
822
824
- hardened generated-card AQ output details so unresolved optional AQ aggregate rows are pruned instead of rendering stale `Entity not found` rows, with generated-card entity reference checks in `self_check` and `v205_release_check`
823
825
- expanded generated-card entity reference checks so stale IDs embedded inside generated-card JavaScript/string expressions are reported, and PM2.5 aggregate entity-ID normalization conflicts are surfaced through diagnostics, `self_check`, and `v205_release_check`
826
+
- filtered generated-card release-validation extraction so JavaScript service names, predicate prefixes, object properties, and entity-prefix strings no longer fail generated-card entity availability checks
827
+
- recorded HA Lab advisory validation for commit `55dc2b9`: lab identity, HI presence/diagnostics, scenario-matrix read-only baseline, and Stage 3 six-sensor runtime-readiness checks passed after lab-only deploy and manual restart; no stable-instance access, HA service calls, helper mutation, dashboard mutation, restart, reload, or output writes were performed by Codex
824
828
- changed generated V2 Current Air Control cards so red control-row styling follows selected alert/CO runtime truth, while degraded or unmapped alert candidates remain in reason text instead of primary chip-row space
825
829
- fixed generated V2 Current Air Control cards so missing or unavailable Air Control Mode telemetry no longer renders as normal/ready, and backend `telemetry_unavailable` is shown as degraded UI truth ahead of stale helper-derived alert or AQ state
826
830
- moved optional Level 1 / Level 2 display-label editing into setup Zones and post-configuration Zone Options before Zone 1 / Zone 2 editing, with diagnostics and generated cards using the same sanitized fallback-aware label source
ha_lab_validation_note: 2026-06-23 HA Lab identity, HI presence, scenario-matrix read-only baseline, and Stage 3 runtime readiness passed for commit 55dc2b9; rendered UI was not validated
34
+
closed: 2026-06-23
31
35
```
32
36
37
+
## Closure Status
38
+
39
+
This proposal is now a historical governance record. The v2.0.7 implementation moved
40
+
red control-row styling to selected alert/CO runtime truth, kept degraded or unmapped
41
+
alert candidates in reason text, and preserved backend lane ordering and entity
42
+
semantics. HA Lab validation remains separate advisory evidence and is not claimed by
43
+
this proposal record as rendered-UI approval. The 2026-06-23 HA Lab run confirmed the
44
+
lab target identity, HI install/diagnostics presence, read-only baseline, and Stage 3
45
+
runtime readiness for commit `55dc2b9`.
46
+
33
47
## Scope
34
48
35
49
Draft a review-gated v2.0.7 proposal for correcting a stable dashboard truth issue
@@ -363,14 +377,15 @@ All lanes converge on a card-template-first proposal. Backend helper work remain
363
377
deferred until there is evidence that card-only logic cannot stay maintainable or
364
378
truthful.
365
379
366
-
## Senyo Approval Gate
380
+
## Senyo Approval Gate (Historical)
367
381
368
-
FINAL VERDICT: PROCEED WITH REVIEW OF THIS PROPOSAL.
382
+
FINAL VERDICT: IMPLEMENTED IN V2.0.7.
369
383
370
-
IMPLEMENTATION ALLOWED: NO.
384
+
IMPLEMENTATION ALLOWED: CLOSED; no further implementation is authorized by this proposal.
371
385
372
-
SENYO REVIEW REQUIRED: YES.
386
+
SENYO RELEASE REVIEW REQUIRED: YES.
373
387
374
-
This proposal may be staged for Senyo review. No implementation, dashboard template
375
-
edit, backend helper, docs promotion, release note, commit, push, or branch switch is
376
-
authorized by this artifact.
388
+
This proposal remains in the repository as the public governance record for the
389
+
implemented UI truth correction. Future changes require a new proposal, issue, or
390
+
release patch with its own validation evidence. This proposal closure does not
391
+
approve tagging, publishing, or GitHub release creation.
0 commit comments