[REQ] Add runtime chore entity sync for dashboard-driven chore changes

[ccpk1]

Problem or use case

Following the later discussion on closed issue #96, this looks less like one remaining update_chore bug and more like a broader runtime limitation.

Today, when chore membership or other chore-backed entity structure changes, ChoreOps relies on a full integration reload to rebuild the affected entities. That is a normal Home Assistant pattern, but it becomes disruptive for dashboard-driven chore changes because the dashboard depends on those live entities and helper surfaces.

When a reload happens during an assignment change, the page can be left stale or temporarily broken until the user manually refreshes. The late comments in #96 suggest the most fragile cases are adding or removing assignees from a chore.

Proposed solution

Add a targeted runtime synchronization path for chore-backed entities so ChoreOps can handle live chore graph changes without depending on a full integration reload for those specific operations.

This should cover chore create, update, and delete, including live add/remove/update of assignee-specific sensors, buttons, and dashboard helper surfaces. Full integration reload should remain available where it is still the right tool, but it should stop being the only backend path for chore CRUD cases that need smoother live behavior.

Expected outcome

• Dashboard-driven chore updates stop leaving the page in a broken or stale state.
• Users no longer need a manual page refresh after chore assignment changes.
• Backend behavior becomes more consistent across service calls, dashboard actions, and config/options flows.
• Chore CRUD becomes a stronger foundation for more interactive native UI patterns in the future.

Alternatives considered

• Adding delays or wait templates after dashboard scripts
• Forcing browser refresh with browser_mod
• Navigating away and back to the dashboard
• Continuing to patch isolated update_chore edge cases instead of addressing the runtime entity lifecycle directly

Additional context

• Feature area: Integration logic/state
• In the latest discussion on [ISSUE] Choreops.update_chore Causes dashboard to be null #96, the current understanding was that chore create/update/delete flows trigger integration reload because the system must recreate or remove user-specific entities when chore membership changes.
• That original reload-centric design appears intentional and standards-aligned with normal Home Assistant integration lifecycle patterns, not an accidental shortcut.
• The new ask is to move one step beyond that baseline for chore CRUD specifically, because ChoreOps now behaves more like an interactive application surface than a mostly static entity set.
• There is already active planning around this direction in the repo, but it would still be useful to track it as a user-facing enhancement request tied back to the field report and dashboard use case.
• @Crazypkr your follow-up testing and examples in [ISSUE] Choreops.update_chore Causes dashboard to be null #96 were the key reason this broader backend limitation became clear.

[ccpk1]

@Crazypkr - I've just pushed 1.0.8-beta.1 release which implements a live runtime sync for chore updates, moves, and deletions. This should officially kill the "integration reload" and keep your dashboard entities from going unavailable when you trigger those rotation scripts.

⚠️ A Note on Complexity and Testing

Because chores are essentially the heartbeat of the entire integration, this architectural shift from "reloading" to "live syncing" carries a lot of weight. Moving to a runtime sync touches everything from the entity registry to state management and dashboard helpers.

Because of that underlying complexity, there is a much higher potential for unexpected regressions compared to a standard update. To be transparent: I haven’t had the bandwidth to run this through every possible scenario yet.

Since this refactor hits such a core part of the system, it really needs some miles on it to ensure it’s rock-solid. If you have some time to give it a thorough spin in your specific environment, your feedback would be incredibly helpful in identifying any edge cases before this goes to a stable release.

---

🛠️ How to Test (HACS)

If you're up for helping validate this, you can grab the beta through HACS:

1. Navigate to the ChoreOps repository in HACS.
2. Click the three dots (⋮) and select Redownload (or check for updates).
3. In the version selection menu, toggle "Show beta versions".
4. Select 1.0.8-beta.1 from the list and install.

As always, I’m specifically looking for any "ghost" entities, missing buttons, or dashboard cards that still feel stale after an update. Thanks for the help!

[Crazypkr]

Incredible, its fixed. No more errors!

[ccpk1]

Good to hear initial indications are positive. My limited tests were showing it working properly, but like I mentioned, there is a pretty high risk of regressions because of all the changes and surfaces these touch. I didn't actually plan on making all these changes right away, but once I figured out how it could work, I figured why not just continue while I had it all fresh in my head.