fix(package-record): record candidates to RustFS; the guard now finds its own files

sean commented

2026-09-10 07:53:18 +00:00

Owner

binjovi-package-record in zdns-builder and zig-builder still set their mc alias against minio.minio.svc.cluster.local; that tenant was deleted 2026-09-10, so the next zdns, zelnet or zerotea build would fail at the record step. Both images go to VERSION 7. The endpoint assertion in check-binjovi-server-package.sh now SEARCHES for every file under images/ that runs mc alias set instead of listing seven publisher tools that could never include these two, with a floor that fails if the search stops matching, and a comment-blind refutation. Four negative controls run and confirmed. The three worker_image pins in binjovi-plans follow. https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76

sean added 1 commit

2026-09-10 07:53:18 +00:00

fix(package-record): record candidates to RustFS; the guard now finds its own files

binjovi/ci Binjovi failed the frozen plan

Details

73b1cda711

`binjovi-package-record` in zdns-builder and zig-builder still set their mc
alias against `http://minio.minio.svc.cluster.local`. That tenant was
deleted on 2026-09-10, so the next zdns, zelnet or zerotea build would have
failed at the record step -- the point where a lane writes its candidate
files and manifest to `workflows/<project>/candidates/<build-id>/`. These
were the last two `mc alias set` sites in this repository naming MinIO;
every tool in binjovi-package-publisher moved in VERSION 9.

WHY THE GUARD MISSED IT, WHICH IS THE MORE USEFUL HALF. The endpoint
assertion looped over seven tool names inside binjovi-package-publisher and
its comment claimed it covered "every script that talks to the store". It
could not: these two live in different images and no list contained them. A
list cannot cover a file nobody remembers to add. The assertion now SEARCHES
-- every file under images/ that runs `mc alias set` must name the RustFS
ClusterIP with its explicit port and must not name MinIO or the headless
Service -- and a floor fails the guard if the search itself stops matching,
so a refactor cannot quietly reduce it to asserting nothing.

The refutation reads the comment-stripped body. Its first draft failed on a
comment that explained why the headless name is forbidden, which is a guard
teaching people to delete the explanation.

Both images go to VERSION 7, pinned here. The three worker_image pins in
sean/binjovi-plans (zdns v19, zelnet v17, zerotea v19) move to the new
digests in the release that follows this one.

Controls, each run and confirmed: the MinIO endpoint restored; the headless
name alone; the headless name beside a correct endpoint; and a comment
naming both, which must NOT fire.

Claude-Session: https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76

sean force-pushed sean/package-record-rustfs from 73b1cda711

binjovi/ci Binjovi failed the frozen plan

Details

to a7fc8a0e23

binjovi/ci Binjovi failed the frozen plan

Details

2026-09-10 07:59:40 +00:00

Compare

sean force-pushed sean/package-record-rustfs from a7fc8a0e23

binjovi/ci Binjovi failed the frozen plan

Details

to 760009ca0f