fix(publish): gate the beta rollout trigger on asset readiness, not just list visibility

The beta.3 trigger no-opped: the instance's channel resolver downloads
each candidate's status.json to read buildMacos, and freshly-uploaded
assets 404 briefly — the candidate got skipped and the previous beta
won. Probe the status.json URL until it serves before triggering.