feat(lattice): project fragments into auto config - #4324
Open
mgazza wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the generic, fragment-published capability-to-PredBat configuration projection layer on top
of #4322.
Noneprojection valuesprovider/user provenance
multi-provider ambiguity
integration can invalidate and cause a fresh all-provider compile with a new immutable plan
digest
The compiler contains no Gateway/GE/Fox/SolaX/Solis brand switch.
Safety
This remains a pure, unregistered, default-off library. Even a projection-complete plan reports
atomic_materializer_missing, and the coordinator suppresses the materializer callback.No production auto-config, Home Assistant, provider runtime, MQTT, or control path is modified.
Public compiled-Lattice publication/versioning, durable adapter registration, runtime override
injection, and the atomic materializer are deliberately separate stacked tranches.
Verification
Fixtures cover Gateway multi-AIO arrays, GE EMS coordinator fan-out, Fox transforms/constants,
Solis explicit
None/absence, correlated local/cloud candidates, user overrides, deterministicordering, invalidation-driven recompilation, and fail-closed conflicts.
Stack