Add the HomeAutomation-Config audit report and reconcile its registry entry - #724
Merged
Merged
Conversation
… entry First committed report for the repository, graded at main and at the develop convergence in flight after its 2026-08-15 resync. The stale driftNote about a README that self-flagged committed secrets is deleted, since the secrets left the checkout and the README no longer mentions them, and the conformance matrix gains the repository as the reference for the operational config shape.
There was a problem hiding this comment.
Pull request overview
Adds the first committed audit report for the HomeAutomation-Config repository and updates fleet metadata to reflect the now-completed secrets hygiene work and the new “operational config” reference.
Changes:
- Add
reports/homeautomation-config/audit.mdcapturing audit results for bothmainanddevelopstates. - Update the conformance matrix to reference HomeAutomation-Config as the first audited
operationalworkflow model repo. - Remove the now-stale “README self-flags previously-committed secrets” drift note from the registry entry.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| reports/homeautomation-config/audit.md | New audit report covering drift, dimensions, findings, and escalations for HomeAutomation-Config. |
| reports/conformance-matrix.md | Sets HomeAutomation-Config as the reference repo for the operational config row and records the audit date. |
| registry/repos.json | Removes an obsolete drift note about previously committed secrets from the HomeAutomation-Config entry. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
Suppressed comments (3)
reports/homeautomation-config/audit.md:24
- This evidence pointer refers to
test-pull-request.yml:31without its.github/workflows/directory. Since other entries in this report use full workflow paths, using the full path here would keep evidence pointers consistent and unambiguous.
| linter-parity | pass | pass | pass | `.github/workflows/validate-task.yml:30-50` runs markdownlint-cli2, cspell (README and HISTORY scope), actionlint, and editorconfig-checker as pinned action wrappers or Docker, one config per linter at the root. `test-pull-request.yml:31` carries the ruleset-bound `Check pull request workflow status job` |
reports/homeautomation-config/audit.md:28
- This row mixes bare workflow filenames (e.g.
test-pull-request.yml:9-12,publish-release.yml:4,merge-bot-pull-request.yml) with fully-qualified paths elsewhere in the report. Using full.github/...paths here improves clarity and keeps the report consistent.
| workflow (WORKFLOW.md 5A/5B) | pass | pass | pass | Operational model: `test-pull-request.yml:9-12` runs on `push` to `develop` (advisory) and `pull_request` into `main` (the enforced gate). `publish-release.yml:4` is `workflow_dispatch` only, matching `releaseTrigger: dispatch-only`. `merge-bot-pull-request.yml` uses `actions/create-github-app-token` (SHA-pinned) with the client-id input, matching the baseline mechanism note. `dependabot.yml` declares `github-actions` for both `main` and `develop` |
reports/homeautomation-config/audit.md:20
- In this Dimensions row, the evidence pointer uses
publish-release.yml:55without the.github/workflows/prefix, while nearby evidence pointers include the full path. Using the full path here avoids ambiguity and keeps the report internally consistent.
This issue also appears in the following locations of the same file:
- line 24
- line 28
| source-only (`sourceonly.nbgv.retained`) | pass | pass | pass | `version.json` retained (hub byte form after #51), and `dotnet/nbgv@master` computes the tag inline at `publish-release.yml:55`, the same unpinned form the hub's own publisher and catalog snippet use by design |
Owner
Author
|
Answering the three suppressed findings from the round on 5b84f7a, all the same point (evidence pointers naming |
The develop to main promotion merged, and the re-run at main reads what develop read, so the report grades one state rather than two.
ptr727
added a commit
that referenced
this pull request
Aug 15, 2026
… the Upstream Repo-Layout Segment (#734) Closes #719 Closes #720 Closes #721 Closes #722 Promotes six merged `develop` PRs to `main`: - #732 -- Reconcile the PlexCleaner registry entry and audit report after the 2026-08-15 resync (closes #719). - #731 -- Exempt hub-hosted paths from the prose gate's `dead-path` rule (closes #721). - #730 -- Fix the hub slug and the dead anchor in the canonical `copilot-instructions.md` (closes #720, #722). - #723 -- Refresh the PhotoCleaner audit report after the 0e84805 resync. - #733 -- Add an `upstream/` segment to the repo layout convention (addresses #725, not closed -- the fork-naming variant differs from the issue's proposal). - #724 -- Add the HomeAutomation-Config audit report and reconcile its registry entry. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
The measured half of the HomeAutomation-Config resync, per
RESYNC.md"Ship It": done means measured, not applied.What
reports/homeautomation-config/audit.md, the repository's first committed report. Graded atmain(e10a2cf, run stampaudit run 2026-08-15T14:58:02Z | hub d54862a) and at the convergence in flight ondevelop(c8252c7,audit run 2026-08-15T14:58:25Z | hub d54862a | branch override develop), kept apart because the promotion (ptr727/HomeAutomation-Config#52) was open when the report was written.developis clean on every mechanized check after ptr727/HomeAutomation-Config#51, and the two type checks forsource-onlyplus the cross-cutting dimensions are judged by hand withfile:lineevidence.driftNote(a README that self-flagged committed secrets) is deleted. The secrets left the checkout in ptr727/HomeAutomation-Config#46 and Develop #49 and the README no longer mentions them, so the note described finished work.spec/validate.pypasses.operationalconfig row gains HomeAutomation-Config as its reference repository, since it is now the first operational repository with a committed report.Escalations
All three the run surfaced were already on file from sibling resyncs the same day, so the report cites them rather than opening duplicates: #720 (the canonical
copilot-instructions.mdnaming the hub by slug), #669 (the twoinvestigateworkflow dispositions), #721 (dead-pathon hub-hosted paths in carried text). Corroborating comments were left on #720 and #721.Checks
The CI prose gate set over the changed files and the whole tree is clean, markdownlint and editorconfig-checker are clean,
repo_gate.pyis clean, andspec/validate.pyclassifies 22 repositories cleanly. The report is CRLF like the rest ofreports/.