Yes, a bunch of you have seen some of this already and will bitch out about it. No, I don't care.
Here is a gallery displaying the problem with the Google Pixel color profile. As you can see, the JPG came out just fine (the apps correctly read it in sRGB), but the RAW file was defaulted to GP, and has terrible banding and chromatic aberration in the blown-out highlight portion of the photo. Once switched in Lightroom to another color profile (Adobe RGB), the issue completely disappears, and the photo can be edited as normal.
The RAWs display in GP in Google Photos, Google Files, and Lightroom, but if I check the color profile, it is unassigned. This usually means programs will default to reading it in sRGB, but something about the way Google has their proprietary color profile integrated into the phone causes all the apps to read RAW images in GP instead, ruining highlights until you forcibly choose another color profile. Lightroom will sometimes briefly default to a normal color profile, but will switch to Google Pixel as soon as you zoom or change a setting until you open the profiles section and change it away from GP.
If you're shooting in RAW, you'll need to change the color profile before editing in Lightroom on a Google Pixel. And there is no way to preview them in Google Photos in anything other than GP, as far as I can tell. Maybe Google Photos can display the P3 profile if you enable that in the camera settings (don't have an easy way to check right now, because Photos doesn't actually tell you which profile it's using), but Lightroom does not. It just defaults back to Google Pixel even if P3 is enabled.
Why? God fucking knows. But hopefully this helps someone else who's rage searching to figure out why their photos look like shit on a new phone. If someone from Google sees this, fix your shit. There's no way this is an intended UI/UX experience.