Hello, I think you may find the solution in your Color settings first. Then open the image again. Because Lr is using another ICC profile than your PSD. Certainly if you're use Tiff to edit your file.
Shortly: Check your color settings in PSD; they may not ignore icc profiles.
Don't believe the document window title: while Photoshop might appear to have opened your images as Raw files, it hasn't really.
You can think of this open image as a "potential TIFF" - it has not been saved yet under ANY particular filename. So PS has no other way to identify it, than by displaying the filename of the Raw it's been converted FROM.
When your LR version is newer than your PS / ACR version, or when using an image editor other than Photoshop, things work differently. And that may be the workflow that you are more familiar with.
In that situation LR renders an image, saves it to TIFF immmediately, THEN tells the image editor to open that for any further changes. This is already a TIFF file, with a known filename, so your document window title displays that.
In this situation, OTOH, LR will not offer the added option of opening a single image into PS "as Smart Object", nor the added options of opening multiple images in PS As Layers, or into PS HDR, or into PS stitching.
the cr2/tiff issue was me seing the cr2 extension and immediately thinking that something's wrong, but like Richard said, it was tiff file after all.
the bigger issue is the added contrast when i'm sending the raw file from lightroom to photoshop with "edit in photoshop" command. and the weird thing is (i just discovered this) that it does that only with raw files from my canon 5d mark ii, but not with the files from my 5d mark iv or sony a7. my workflow hasn't changed in years, and this has been happening in the pas couple of days.
i found a workaround - export in lightroom as tiff, check the "add to this catalog" option and then send it to photoshop with "edit in photoshop". this doesn't change the contrast, but it is a little bit of a pain.
btw, my working color space is prophoto both in lr and ps, so there is no mismatch there.
just to check - your image is opening directly into PS from LR - not via an ACR window?
ACR should be ignoring its own processing defaults, in this instance where LR is invoking an external edit - (it's ACR which has rendered an unsaved image, LR which has rendered a pre-saved image) - and ACR just employs LR's processing metadata as-is using whatever Process Version that requires.
Besides the main "Edit in PS" option you can also set up an additional editor program in the lower part of the LR external editing settings dialog. You can point to the Photoshop program executable within your system, select a preferred combination of colourspace, bit depth, file type, save it as a suitably named external editing preset. Make and save as many of these as you want, within this same dialog area. Then this preset can be invoked (from the context menu in Develop) to Edit In PS to those specifications.
So: this option forces the method which LR would otherwise only fall back on, if it had failed to send to a version-compatible ACR.
but this is a quick way to choose on the fly whether you'll be externally editing in 8-bit or 16-bit, ProPhoto or whatever, as best suits each instance. Also you can then easily compare the one method with the other, and as to different colourspaces, so far as what then happens at the Photoshop end. Maybe it's the profile policy there, in PS Color Settings for example.
Of course, the visually exact same thing should be happening at the PS end either way - but this may depend on some PS settings including those relating to ACR.