Skip to content

Registry: HomeAssistant-Config operational conformance completed - #342

Merged
ptr727 merged 2 commits into
developfrom
registry-homeassistant-config-conformance
Jul 17, 2026
Merged

Registry: HomeAssistant-Config operational conformance completed#342
ptr727 merged 2 commits into
developfrom
registry-homeassistant-config-conformance

Conversation

@ptr727

@ptr727 ptr727 commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Reconcile the stale HomeAssistant-Config registry driftNotes after the #16 operational onboarding. Mirrors the #329 reconciliation for Vantage-Config.

What changed

The prior driftNotes described work that is now complete and planned a groundTruthBranch flip that is declined:

  • "develop is behind main by 2 commits / fast-forward then flip groundTruthBranch to develop" - develop is content-ahead; the flip is declined (see below).
  • "pending: lint CI" - test-pull-request.yml with the Check pull request workflow status job required check is live.
  • "pending: dispatch-only source-release scaffolding (version.json + publish-release.yml)" - both present.

Replaced with a completed-onboarding summary: baseline carried (repo-config operational, AUDIT.md, spec/secrets.json, App-signed Dependabot merge-bot) and promoted develop -> main via HomeAssistant-Config PR #17. Self-audit verified in sync (settings, both rulesets, CODEGEN_APP_* present in both stores).

groundTruthBranch stays main (deliberate)

Kept groundTruthBranch: main, not flipped to develop. develop is the working branch (direct signed commits); main is the promoted stable snapshot the audit should target. This is a deliberate divergence from the other operational repos (Vantage-Config / ESPHome-Config / HomeAutomation-Config use develop); the broader convention question is raised in #340.

Findings note (context, see #341)

The #16 audit block was stale: the CODEGEN_APP_* secrets were already present in both stores and develop was already ahead of main. Only the repo-config/... absent LETTER finding was real, and it is now cleared on main by PR #17.

Validation: jq parses clean, spec/validate.py -> "21 cataloged, 0 backlog repos classify cleanly."

🤖 Generated with Claude Code

Reconcile the stale HomeAssistant-Config driftNotes after the #16 operational
onboarding. The prior note described work now done (develop was behind main,
lint CI pending, publish scaffolding pending) and planned a groundTruthBranch
flip to develop. Replace it with the completed-onboarding summary (baseline
carried and promoted to main via #17), and record that groundTruthBranch stays
main deliberately - develop is the working branch, main the promoted stable
snapshot the audit targets (see #340). Mirrors the #329 reconciliation for
Vantage-Config.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 17, 2026 22:07

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the fleet registry entry for HomeAssistant-Config to reflect that operational onboarding work is complete and to record the deliberate decision to keep groundTruthBranch on main.

Changes:

  • Replaces stale driftNotes content with an onboarding-completed summary and current state of CI/publisher/baseline carry.
  • Records the intentional groundTruthBranch: main decision (and references the fleet-wide discussion issue).

Comment thread registry/repos.json Outdated
Spell out the bare #17 as HomeAssistant-Config #17 so the promotion PR
reference is unambiguous in the fleet registry. Flagged by Copilot on #342.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 17, 2026 22:10
@ptr727
ptr727 merged commit af2f008 into develop Jul 17, 2026
7 checks passed
@ptr727
ptr727 deleted the registry-homeassistant-config-conformance branch July 17, 2026 22:11

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

registry/repos.json:230

  • HomeAssistant-Config #16 / #17 is still ambiguous about whether the references are issues or PRs. Since this note is meant to be durable registry context, spell out issue #16 and PR #17 explicitly to avoid confusion.
            "driftNotes": ["Home Assistant CONFIGURATION (configuration.yaml + automations/blueprints), NOT a HACS integration (no custom_components/manifest.json, no hacs.json).", "Operational onboarding completed 2026-07-17 (HomeAssistant-Config #16): master->main rename + develop created, advisory lint CI (Check pull request workflow status job required check), dispatch-only source release (version.json + NBGV + publish-release.yml), repo-config operational carry (rulesets/settings applied and verified in sync), Dependabot + App merge-bot with the CODEGEN_APP_* pair in both stores, adapted self-audit (AUDIT.md + spec/secrets.json); baseline promoted develop->main via HomeAssistant-Config #17.", "groundTruthBranch intentionally main: develop is the working branch (direct signed commits), main the promoted stable snapshot the audit targets - deliberately not flipped to develop (ptr727/ProjectTemplate#340).", "Private; deployed by git pull into the HA config dir."]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants