Dogfood Gate red on every run: a2ml-validate-action and k9-validate-action are 404

[hyperpolymath]

Not caused by any PR here — estate-level, and it will make main red on its next push.

Measured

$ curl -o /dev/null -w "%{http_code}" https://github.com/hyperpolymath/a2ml-validate-action   -> 404
$ curl -o /dev/null -w "%{http_code}" https://github.com/hyperpolymath/k9-validate-action     -> 404

.github/workflows/dogfood-gate.yml consumes both:

line 43:  uses: hyperpolymath/a2ml-validate-action@0f8081cd... # main
line 92:  uses: hyperpolymath/k9-validate-action@b4b4bd64...   # main

Runner error:

##[error]Unable to resolve action hyperpolymath/a2ml-validate-action, repository not found
##[error]Unable to resolve action hyperpolymath/k9-validate-action, repository not found

When it broke

Dogfood Gate run	Result
2026-07-21	success
2026-07-24 08:40 (main)	success
2026-07-27 (first run since)	failure

So both action repos disappeared between 24 and 27 July — renamed, deleted, or made
private. main has simply not been pushed since, which is the only reason it still shows
green.

Why it is easy to misread

Two jobs fail with an identical "repository not found", which reads like a permissions or
token problem. It is neither — the referenced repos do not resolve at all. Note also that
Actions will not follow a repository rename in a uses: reference even though the REST
API silently will, so a rename is fully sufficient to cause this.

To fix

1. Establish what happened to both repos (renamed? deleted? private?).
2. If renamed — update uses: in dogfood-gate.yml; Actions cannot follow it by itself.
3. If gone — either restore them, or replace those two jobs with inline validation.
4. Estate sweep: any other repo consuming these two actions has the same latent failure.