feat(presets): consume the unified preset stack - #3
Merged
Conversation
Fetch bundled and saved presets through the effect-scoped SDK projection. Preserve the canonical effect and preset pair through selection, services, and master-light resume so bundled presets follow the same path as saved presets. Require the SDK release that introduces the unified preset endpoints and cover duplicate labels, services, coordinator loading, and end-to-end apply. Co-Authored-By: Parfit (Codex subagent) <noreply@openai.com>
Keep the published integration requirement on the forthcoming 0.3.2 SDK, while allowing the editable development checkout to retain its release-owned 0.3.1 version stamp. CI and release validation now fetch the exact commit that contains the effect-scoped preset stack.
Catalog and state refreshes can complete in either order after an effect switch. Carry the effect provenance with each preset stack and suppress options until it matches current state, preventing stale preset applies.
Keep CI and release validation on the reviewed Hypercolor head so the editable SDK and bundled preset identity checks are resolved together.
Keep Home Assistant verification and release builds on the exact reviewed Hypercolor commit that defines the unified preset client contract. Co-Authored-By: Nova (OpenAI Codex) <noreply@openai.com>
Keep integration and release verification on the exact Hypercolor head after the preset-key implementation was brought into Biome compliance. Co-Authored-By: Nova (OpenAI Codex) <noreply@openai.com>
Advance integration and release verification to the exact Hypercolor commit that aligns every Rust and TypeScript preset-key separator. Co-Authored-By: Nova (OpenAI Codex) <noreply@openai.com>
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
1 participant
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.
What changed
Home Assistant now consumes Hypercolor's effect-scoped preset stack through the typed Python SDK introduced by hyperb1iss/hypercolor#153.
The preset selector displays bundled and saved entries together, preserves their canonical effect and preset identity, disambiguates duplicate display names, and applies either origin through the unified route. Catalog responses carry the effect they were fetched for, so options stay hidden during an effect-switch race until catalog and active state agree.
Master-light resume and preset services also retain the full effect and preset pair. Saved preset creation and deletion remain library CRUD operations.
CI and release validation pin the exact reviewed Hypercolor commit,
25067d621c9756388fe13e850fcd2a9f90389870, until the SDK release containing this contract is published.Why
The integration previously fetched and applied only saved presets. Bundled presets were invisible, and the selector, service, and resume paths could not preserve a canonical reference. The unified contract removes that split and makes both origins behave identically for Home Assistant users.
Verification