Found checking minio before assigning it on novox. Not a novox-side
problem - DNS, daemon.json and the auth handshake are all fine; quay.io's
own token for both quay.io/minio/mc and quay.io/minio/minio (the module's
own pinned server image) comes back with actions:[] and $disabled. Worked
four days ago at the 2026-09-20 rehearsal.
Distinct from issue 064: that one was about the mesh's build environment
reaching a declared vendor image. This is the vendor disabling the image
for everyone, which a declared, pinned digest does nothing to protect
against.
Checks pass.
jschoubben