Official builds in the LineageOS realm as much as I recall give you periodical automatic builds by the LineageOS build system which the maintainer for the respective device didn’t stop because of expected or known trouble.
Builds can OTA update via the updater within the same underlying Android version.
Community builds in the /e/OS realm give you periodical builds by the /e/OS build system the /e/OS developers feel confident about to release.
Builds can OTA update via the updater within the same underlying Android version.
On devices which have both flavours, official builds in the /e/OS realm usually are community builds which get kind of promoted to official after community users used them for a while and no serious trouble showed up.
With official builds there’s a chance that the /e/OS developers might prepare OTA upgrades via the updater from one underlying Android version to the next if technically possible, but there’s no guarantee, since it’s still complicated.
I can understand wanting /e/OS “official” releases, but “official” LineageOS is simply not the same thing.
Don’t compare just the wording, look at the substance.
It isn’t from /e/OS based on Android 12 on, as Rooted debugging and SafetyNet can coexist since then … SafetyNet on /e/OS Community "dev" devices - let it in or not?