It looks like version 1.5.6 corrected the issue. I was not able to reproduce the issue after updating.
This occurs in the latest official WordPress docker image using the latest WP CLI downloaded at time of bringing the docker image online.
WordPress: 6.4.2
PHP 8.2.13
Chrome: 120.0.6099
Edge: 120.0.2210