X position on comped adjustment layer double moves

OK this took a long time to track down. Does BMD pay a bug bounty?

I work in Open Gate ("OG") a lot, and use adjustment layers to shift underlying footage. My final step before output is to make a composite of the OG clips and their adjustment layers, because this renders back to the source pixels (if you're not aware of this, my "discovery" of this is outlined in detail on my post "What's your workaround for transform presets?" viewtopic.php?f=21&t=216874#p1127793 )

Anyway I had a new issue in Resolve 20 beta that I hadn't been able to track down, and was hoping it'd be addressed before release. Now that v20 is out, I've found that the bug is still there, and I finally tracked it down.

This affects Vertical timelines. It does not matter if the Project settings are vertical, or if a project has been changed from project default. It does not seem to matter what the resolution of the source media is (I usually am in OG, but in the sample provided I used UHD footage to remove variables).

1. Create a vertical timeline (1920 x 1080 with Vertical checkbox enabled).

2. Place a clip on the timeline, set Scaling to Fill. Do not move the clip (Transform). Place an adjustment layer on top, and shift the X position. Comp the two clips. The underlying clip moves further in the X position.

3. Repeat the above, but this time move the video clip, even setting X to 0.001. Once comped, it does not move, as expected.

4. Repeat again, this time setting Scaling to Crop. Do not move the clip. Once comped, it does not move, as expected.

I have provided a sample project with media; this is a 95MB download.

https://www.dropbox.com/t/ehX0eoAhi4ZJRNEc

I assume this is related to the other X position bug I posted, "Bug: beta 4, animated subtitles X position not honored" viewtopic.php?f=21&t=221967 since that was also found while in vertical timelines, and a Composite Clip is apparently a Fusion Comp, as is the subtitle text from the above post.