mirror of
https://github.com/home-assistant/core.git
synced 2026-08-11 16:11:49 +02:00
Paulus SchoutsenandClaude Fable 5
402e7987bd
The biggest single failure cluster in the compat baseline (~298 suites, 282 reauth + 176 reconfigure failures): a reauth / reconfigure / reset flow calls ConfigFlow._get_reauth_entry() / _get_reconfigure_entry(), which resolve the entry via async_get_known_entry on the flow's hass. That flow runs in the sandbox, whose private hass has never seen the entry main owns — so every such flow raised UnknownEntry on its first step and the proxy aborted it as 'sandbox_flow_error'. FlowInit gains an optional EntrySetup 'entry' field. When the flow context references an entry_id main owns, the proxy serialises that entry (shared entry_to_setup_proto builder, also now used by the entry_setup payload) and the sandbox flow runner seeds a copy into its private config_entries before async_init — so the reauth/reconfigure entry lookups resolve. A plain user/discovery flow (no entry_id) is unchanged. This unblocks those flows from erroring on step one; the terminal async_update_reload_and_abort still mutates the sandbox's private entry copy rather than main's — that entry-writeback crossing is the next lever (see reports/2026-07-08/FINDINGS.md), tracked separately. Regression tests both sides: the proxy attaches main's entry to FlowInit; the runner resolves _get_reconfigure_entry from the seeded copy (stash-verified to fail without the seed). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QCotUYum6AoisyrxshoiJJ