release/1.0 carried SAFETY-04 and TEL-01 but still declared version: "0.2.1" - identical to what is installed and running on the house (tagged v0.2.1). Home Assistant keys add-on updates off the version string, so the update would never have been offered.
Two files: config.yaml version, and a CHANGELOG entry for 0.3.0. No code, no option defaults.
Defaults confirmed unchanged, since these are what will run live: meter_source: "off", integrator_max_w: 0, target_grid_w: -10. SAFETY-04's control law is the only behavioural change reaching the house at these defaults, and it carries a 4,928-case equivalence proof against the previous law.
Suites unchanged: 55 / 122 / 18 / 21.
Rollback point: tag v0.2.1 on master.
`release/1.0` carried SAFETY-04 and TEL-01 but still declared `version: "0.2.1"` - identical to what is installed and running on the house (tagged `v0.2.1`). Home Assistant keys add-on updates off the version string, so the update would never have been offered.
Two files: `config.yaml` version, and a CHANGELOG entry for 0.3.0. No code, no option defaults.
Defaults confirmed unchanged, since these are what will run live: `meter_source: "off"`, `integrator_max_w: 0`, `target_grid_w: -10`. SAFETY-04's control law is the only behavioural change reaching the house at these defaults, and it carries a 4,928-case equivalence proof against the previous law.
Suites unchanged: 55 / 122 / 18 / 21.
Rollback point: tag `v0.2.1` on master.
Fixes the version collision noticed while planning DEPLOY-01: release/1.0
still carried version 0.2.1, identical to what is already running on the
live system, so Home Assistant would not have offered the update at all.
- config.yaml: version 0.2.1 -> 0.3.0 (minor: TEL-01 adds a feature,
SAFETY-04 changes the control law's internals)
- CHANGELOG.md: 0.3.0 entry for SAFETY-04 and TEL-01, in the existing voice
No code under app/ touched, no option defaults changed. Verified:
meter_source: off, integrator_max_w: 0, target_grid_w: -10 all unchanged.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Du77usMj8XNKNFZGmUiWDa
This branch is already included in the target branch. There is nothing to merge.
This branch is out-of-date with the base branch
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
release/1.0carried SAFETY-04 and TEL-01 but still declaredversion: "0.2.1"- identical to what is installed and running on the house (taggedv0.2.1). Home Assistant keys add-on updates off the version string, so the update would never have been offered.Two files:
config.yamlversion, and a CHANGELOG entry for 0.3.0. No code, no option defaults.Defaults confirmed unchanged, since these are what will run live:
meter_source: "off",integrator_max_w: 0,target_grid_w: -10. SAFETY-04's control law is the only behavioural change reaching the house at these defaults, and it carries a 4,928-case equivalence proof against the previous law.Suites unchanged: 55 / 122 / 18 / 21.
Rollback point: tag
v0.2.1on master.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.