this is very simple how the kmods are built:
kmods are built for every arches, every release (and stable)
FreeBSD:X:arch/kmods_quarterly are the kmods from the quarterly ports branch for the X branch (X being stable or main) of the source tree (using the weekly pkgbase repo which are always published in a predictable manner)
FreeBSD:X:arch/kmods_latest are the kmods from the main ports branch for the X branch (X being stable or main) of the source tree (using the weekly pkgbase repo)
FreeBSD:X:arch/kmods_quarterly_Y are the kmods from the quarterly ports branch for the X.Y releng branch of the source tree (using the releng pkgbase repo)
FreeBSD:X:arch/kmods_latest_Y are the kmods from the main ports branch for the X.Y releng branch of the source tree (using the releng pkgbase repo)

let's say I see a security issue, which affects my use case, I would switch temporary on latest and switch back on weekly a couple of days later.
We can also align the EN/SA release date on the weekly or the other way around, so the next weekly happen few hours after the EN/SA are issued

I think it is, if you run, stable or current, you are supposed to know what you are doing.

yes it will also affect current

I have readded the macos CI and fix the code that needs fixing, I still consider we should use the installed libcurl when building on macos so I haven't fixed the libcurl part.

there was a CI for macos, but because libatf and kyua broke, we removed mac for the ci.

it is not cache so I suspect it would work on arm64 but I can t test

I disagree and fixed the stup of developers@ so now it accepts mails in BCC? if not, please ping me.