Just encountered this with a near-fresh Tahoe 26.6 install, with Siri never enabled, no AI etc, so it's still a thing today. Was trying to just copy or tar a home folder to move elsewhere, left it to cook and came back to an error hitting one of these files. Just an FYI since I hadn't come across it before, deeply irritating to have another way Apple has kneecapped basic control by the owner over their own files. I find this one is particularly inexplicable though, other instances involve use of filesystem mechanisms (fs flags, sealed volumes etc) in space that, while it should still be subject to owner modification at their own risk if desired, is at least "Apple territory" (/System and so on). Here though it's in your own user home folder, and totally mysterious.