Registry: HomeAutomation-Config operational conformance completed - #335
Merged
Conversation
The entry recorded the operational rollout as pending; lint CI and the dispatch-only publisher were already live, and the #21 conformance carry (repo-config operational baseline, adapted self-audit, Dependabot merge-bot) landed on develop 2026-07-16 (54637c4), rulesets/settings verified in sync. The legacy Vantage/ subtree note is updated to stripped (verified: no such tree on develop). Remaining owner task (App secret pair in both stores) is recorded - the merge-bot is inert until then. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the fleet registry metadata for HomeAutomation-Config to reflect that operational conformance work has landed, removing stale onboarding-pending notes and recording the remaining owner action item.
Changes:
- Replace the stale “Operational rollout pending” drift note with a conformance-complete status note (including date and PR reference).
- Update the legacy
Vantage/subtree note to record it as already stripped. - Record the remaining owner task: missing
CODEGEN_APP_CLIENT_ID/CODEGEN_APP_PRIVATE_KEYin secret stores, leaving the merge-bot inert until set.
ptr727
added a commit
that referenced
this pull request
Jul 18, 2026
…esolved (#348) Reconciles the ESPHome-Config registry entry after its conformance standup (ESPHome-Config#46) and the Dependabot ecosystem fix (ESPHome-Config#49 / promotion #50) completed - same close-out pattern as #329/#335. The second `driftNote` recorded the operational rollout as pending and Dependabot as `devcontainers`-only. Both are resolved and **verified from the live repo** before dropping the note: - esphome-config validation job feeds the required check; `version.json` + `publish-release.yml` present; **2.0.12** released 2026-07-18; `develop` is ground truth. - `.github/dependabot.yml` declares `github-actions` **dual-target** on both `develop` and `main`. - `python3 spec/audit.py ESPHome-Config` (with the #346 check now on develop) -> **clean**; no `dependabot` DRIFT. The first note (ESPHome device config consumed by the ESPHome-NonRoot image) stays - still true. `spec/validate.py` passes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jul 18, 2026
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.
Reconciles the HomeAutomation-Config registry entry after the #21 conformance carry landed on its develop (54637c4, 2026-07-16) - same close-out pattern as #329 did for Vantage-Config.
spec/validate.pypasses.🤖 Generated with Claude Code