The loop ran against real GitHub repositories rather than fixtures, so
the status section can stop hedging — and two of the things it turned up
are traps a reader hits before anything else works: the required status
check is `validate / validate`, and in the combined layout the gate does
not see the repo's own CI announce at all.

Also warns off `0.1.3` and earlier for `--with-skills`, where the missing
`[announce]` table pointed the announce at the public first-party index.