BTRFS is designed to go read-only when a problem is detected so you can preserve your data in case the reported damage is real. If you don’t provide:
You don’t know if the BTRFS filesystem is damaged, so you should make sure important data are backed up, then provide as much detail as possible to help understand the why 6.10.9 boots to read-only mode.
Same for me. The most info I was able to get through all of this was the partial log in my original post (which, I have to reiterate, I saw nothing in the logs prior to what I posted that indicated anything abnormal), and the logs posted here and here.
Now that the issue is fixed, there are no such errors in dmesg.