i confirm this is now working on v2026.4.0-latest +289
so the GitHub compare between this and when the bug was reported is
that shows the likely commit that fixed this bug
i confirm this is now working on v2026.4.0-latest +289
so the GitHub compare between this and when the bug was reported is
that shows the likely commit that fixed this bug