The pinned reusable workflow (@c9dab69d) hardcoded
`docker://…/steve/gadfly:sha-b37cd09` into the step URI. That tag was
never pushed to the registry, so every review in this repo failed in
~1s on "failed to resolve reference … not found" — a red workflow that
reads exactly like a review which found nothing (PR #28, run 7056).
@8adeeea runs the reviewer as the job container and resolves its tag per
run — inputs.reviewer_tag then vars.GADFLY_REVIEWER_TAG then the baked
sha-b850e35 — so the hardcoded-dead-tag failure cannot recur, and
retagging the reviewer needs no commit here. Both sha-b850e35 and
sha-8adeeea are present in the registry.
Gadfly config is read from main, so this has to land on main to take
effect for any PR's review.
steve