Execution roadmap after v2026.03.02: PR1 -> PR2 -> PR3

[jbjardine]

Hi everyone,

Now that the regression fix is merged and released in v2026.03.02, here is the execution roadmap for the next steps.

Why split into 3 phases:

1. keep each PR focused and easier to review
2. reduce regression risk
3. make IRL validation easier between steps

Phase 1 (PR1):

• ConfigFlow + DataUpdateCoordinator + YAML import migration

Phase 2 (PR2):

• dedicated read-only sensors
• temporary compatibility window for legacy climate attributes (2 releases)

Phase 3 (PR3):

• manual reset service (advanced service v1)

How we will run this:

1. one scope per PR
2. one beta per phase before stable
3. merge to stable only after clear feedback

Tracking:

• roadmap issue: Roadmap: ConfigFlow, dedicated sensors, and manual reset service #68
• PR1 draft: ConfigFlow + coordinator architecture with YAML import migration #67

If some of you can test on real stove hardware during each beta, that would help a lot.
Thanks again for the collaboration.

[jbjardine]

Quick sync note so the roadmap discussion stays aligned with the current state 🙂

• #72 is now merged
• PR1 / #67 has been refreshed on current main
• PR1 beta is now published for validation
• #79 remains part of PR1 beta validation
• #76 stays as a separate follow-up after PR1, so PR1 feedback stays easier to interpret

Operational tracking remains in #68, and beta / test feedback can go on #67.

Thanks again for all the collaboration 🙂