Lightroom Classic: exported 360 JPG keeps source GPano pixel dimensions after resize

Version / OS: Lightroom Classic 16.0, Windows 11

Description: When a DNG/TIF containing Google Photo Sphere (XMP-GPano) metadata is exported as a smaller JPG, the GPano pixel-size tags are copied across unchanged. The exported file’s real dimensions no longer match them, so it is an invalid 360 file for strict readers. Facebook for example no longer sees it as a valid 360 file.

Steps to reproduce:

1. Import a full equirectangular 2:1 DNG with GPano tags (mine: 18250×9125, stitched in PanoVolo 1.13.0).
2. Export as JPG, resized to 8000×4000 (metadata set to “All Metadata”).
3. Read the JPG with ExifTool.

Expected: FullPanoWidthPixels, FullPanoHeightPixels, CroppedAreaImageWidthPixels and CroppedAreaImageHeightPixels are updated to 8000 and 4000 to match the file.

Actual: All four still say 18250 and 9125. The file is 8000×4000, and the tags describe a sphere 2.3 times larger than the image.

Impact: Panorama readers that check these values can reject the file or read it as a partial panorama, and I have to correct the tags in every export with a separate tool.

ExifTool output for the TIF and the JPG attached.