Oh my gosh. It really is fixed! I traced the bug report back to this forum post:
It didn't show up in any of our search engine queries because the original poster just attached a screenshot of the error. Thank you so much @personalizedrefriger for the PR that fixed this issue! And thank you @mrjo118 once again for helping me to diagnose this. It turns out the fix was already in progress elsewhere, but hey, we learned about Nextcloud DAV, right?
