Not really. I update the first message in this thread, but there is no extra announcement anywhere. As I build currently 4 different branches/versions for R7800 in varying order several times a week, any announcements would quickly spam the thread. And as most builds have not that many relevant changes in the gradually developing main OpenWrt, there is not much reason to spam.
I am also not commenting changes in the OpenWrt bit, as everybody can check the recent changes directly from there.
How to switch back to ct firmware?
Reinstall the build sysupgrade.bin file
copy it from /rom/lib/firmware as it was included in the flashed firmware
You own this thread and you are the boss and it's your decision. But, if I was doing builds, I will post a message that the new build is up - just an one liner. Anyways, you can decide what is best. Thanks for supporting R7800 and appreciate all your efforts.
Is it the right set of commands to quickly revert to CT firmware?
opkg remove ath10k-firmware-qca9984
opkg install ath10k-firmware-qca9984-ct
cd /lib/firmware/ath10k/QCA9984/hw1.0/
mv firmware-6.bin firmware-6.bin.bk && mv firmware-5.bin.bk firmware-5.bin
Is your directory correct (root/rom/lib vs. root/lib)? Or are they the same?
Assuming that you use a build that originally had CT firmware, just one command is needed, as everything in the original firmware image is permanently in /rom directory. All your later changes (and deletions) are in /overlay/upper. Thanks to the overlayfs file system you see /rom + /overlay combined as /. For example, the original /etc/banner is in /rom/etc/banner and if you edit /etc/banner, the new file gets stored as /overlay/upper/etc/banner and when you access /etc/banner, the overlayfs gives you /overlay/upper/etc/banner.
Thus restoring the original CT firmware just requires:
cp /rom/lib/firmware/ath10k/QCA9984/hw1.0/firmware-5.bin /lib/firmware/ath10k/QCA9984/hw1.0/
That will read the original CT firmware from /rom and replace the current one in /lib/firmware/...
Well, it would have been 473 messages in the last three years. (based on my logs I have actually flashed 636 different successful builds for my R7800 in that time).
The point is that most of the builds contain no significant changes. Note that I have usually posted a message when there has been something special, but lately there has not been much R7800-specific change from me. And I am not going to try to summarize the OpenWrt commit changelog. Most of the builds just show that the recent gradual changes in LuCI, packages, whatever still work.
it is fine the way it is now: besides checking every now and then if there is a new built, we have at the same time the chance to read the latest comments as well. 
PS: keep up the good work @hnyman, I'm using your built since I've got this router, and love it. There are bugs every now and then, but I do appreciate your work! 
@hnyman I'm stuck on build r11035 using your scripts after running updateNmake.sh, any idea why? I did some changes in createbuildinfo.sh and did a make clean... I also changed some r7800 build related stuff in make menuconfig...
Well, do the git updating manually (git pull), read error messages and fix conflicts.
Mmmm correct, I must have missed the conflicts error messages. More clear when just using git pull.
the latest stable openwrt-19.07 09/29 build sqm still maxed out at 75-80mbps for my 100mbps line... solid build otherwise
I will add an explicit check for git pull failure to the scripts.
--- hnscripts/updateNmake.sh
+++ hnscripts/updateNmake.sh
@@ -5,6 +5,7 @@
umask 0022
echo "...update main source..."
git pull
+[ "$?" -ne 0 ] && echo "Updating the main OpenWrt source code failed." && exit 1
echo "...update feeds..."
./scripts/feeds update -a
[ "$?" -ne 0 ] && echo "Updating the feeds failed." && exit 1
(I added the error checking feature to the actual OpenWrt scripts/feeds script in 2015 and have included a check for that failure since then in my buildscripts, but I will now also add a check for the generic git command failure in the main source git pull step.)
imo you should try using RPS and XPS, will probably get you over 100mbps at any rate. simplest is to set to 3, i experimented with setting it to the opposite CPU that the interrupt was on, seemed to make a slight difference to the SIRQ, but not much. i need to connect it to upstream Gig line again to test properly.
already tried
Which interface(s) should I set the values on? The one that have the public IP?
on Kong's build he just sets it on everything. i set it on everything starting with eth0 or eth1, so not very scientific :). oh, and ifb4eth0.2.
The filenames always started with R7800-owrt1907 but today's build, I see that it's start with wrt3200acm-owrt1907-r10591...-sysupgrade.bin. Is this for R7800?