dc32f0cfe84def651e0e I'm wondering why does this bug feature brick the device instead of just refusing to boot? That's very hostile.
So from what I've gathered, how the anti rollback feature is supposed to work - it flashes the bootloader to the secondary slot, and if the phone bootloops later, it deletes the snapshot/configuration changes and reverts to the old config on the primary slot. If there's no bootloop, it merges the changes to the primary slot.
But for some reason, when implemented on Pixels 6/8, the potential for a hard brick rises radically and the phone enters some kind of emergency recovery mode where it's detected if connected to the OS, but you can't power on, fastboot, use recovery or anything. I'm not finding any concrete reason for why this occurs, but it is clearly related to which slot is flashed, when and how.
Apparently google have decided that they can make bank whether or not they address the issue and can afford to give the finger to affected users instead of make public their recovery mode tools for restoring these 'hard' bricked phones to working condition.