Update: I can confirm the issue is still reproducible on macOS 26 beta 2.