fix(ci): re-point validate-action references at the ecosystem repos - #60
Merged
Conversation
`hyperpolymath/k9-validate-action` and `hyperpolymath/a2ml-validate-action`
no longer exist as standalone repositories. Both were consolidated INTO
`k9-ecosystem` / `a2ml-ecosystem` as real top-level directories and the
originals deleted. The content is intact — 302 and 306 files respectively —
only these references are stale.
Any workflow reaching them fails at job setup with:
Unable to resolve action hyperpolymath/k9-validate-action,
repository not found
GitHub resolves an action held in a subdirectory as `owner/repo/path@ref`, so
this is a path change, not a restore:
hyperpolymath/a2ml-validate-action@<old>
-> hyperpolymath/a2ml-ecosystem@aa4b836b
hyperpolymath/k9-validate-action@<old>
-> hyperpolymath/k9-ecosystem@89f3c270
Both targets are verified to hold a real `action.yml`
('Validate A2ML Manifests' / 'Validate K9 Configurations').
This surfaced only because `dogfood-gate.yml` was itself invalid YAML in 71
repos, so the workflow had never run and never attempted to resolve these
actions. Repairing the parse error exposed the stale reference beneath it.
Verified before push: every edited file still parses and still yields a
`jobs:` mapping, and no `*-validate-action@` reference remains. 1
file(s) changed, all under .github/workflows.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
hyperpolymath
added a commit
that referenced
this pull request
Jul 28, 2026
`.githooks` is missing from the placement guard's ALLOW list, while `.github`, `.claude`, `.machine_readable`, `.bot_directives`, `.well-known` and `.hypatia` are all present. It is repo infrastructure, not database content, and it **has** to sit at the worktree root — that is where git resolves `core.hooksPath`. ## This is now load-bearing, not theoretical #59 landed `.githooks/validate-a2ml.sh` and `.githooks/validate-k9.sh`, and `dogfood-gate.yml` on `main` runs both. They are tracked today, so **the next PR that adds a file under `.githooks/` fails the guard** with *"Misplaced content"* — which is exactly what happened on the #59 branch itself. ## Not a policy decision — an omission `rsr-template-repo`'s own `root-allow.txt` carries a comment recording the identical gap for the identical directory: > Tracked since #141 (pre-push Dogfood Gate) but never allow-listed, so `scripts/check-root-shape.sh` failed on this repo itself and on every repo instantiated from it. Same directory, same oversight, different gate. ## Verified it still discriminates Not just "passes more" — the #58 tightening is intact: | path | verdict | |---|---| | `.githooks/validate-a2ml.sh` | **ALLOW** | | `docs/y.adoc` | ALLOW | | `verisimdb/x.res` | warn (grandfathered) | | `lithoglyph/new.zig` | **ERROR** ← #58 tightening holds | | `random/thing.rs` | **ERROR** | ## A correction to my earlier PR descriptions In #59 I wrote that `hyperpolymath/k9-validate-action` and `a2ml-validate-action` "have never existed". **That was wrong.** As your #60 establishes, they were real and were *consolidated* into `k9-ecosystem` (681 KB) and `a2ml-ecosystem` (910 KB) as top-level directories, with the standalone repos deleted. The 404 was real; my inference from it was not. That matters, because it means `owner/repo/path@ref` was always an available fix — which is what #60 does. `dogfood-gate.yml` currently uses the in-repo `.githooks` scripts from #59; **both approaches work**, and which one this repo should keep is your call. If you prefer the ecosystem actions there too, the `.githooks` copies become redundant and this PR is only needed for as long as they are tracked. 🤖 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
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.
hyperpolymath/k9-validate-actionandhyperpolymath/a2ml-validate-actionno longer exist as standalone repositories. Both were consolidated intok9-ecosystem/a2ml-ecosystemas real top-level directories and the originals deleted.The content is intact — 302 and 306 files respectively. Only these references are stale.
Any workflow reaching them fails at job setup:
The fix — a path change, not a restore
GitHub resolves an action held in a subdirectory as
owner/repo/path@ref:Both targets verified to hold a real
action.yml— Validate A2ML Manifests and Validate K9 Configurations.How this stayed hidden
dogfood-gate.ymlwas itself invalid YAML in 71 repos, so the workflow had never run and never attempted to resolve these actions. Repairing the parse error exposed the stale reference underneath — one layer of silent breakage concealing another.Verified before push
jobs:mapping*-validate-action@reference remains.github/workflows🤖 Generated with Claude Code