This looks like a limitation of Oracle’s native TRUNC(date) function … causing loss of the timezone information.

Yes, that’s right.

I’m not sure but how we might be able to get around this

It should in principle be possible to work around this by converting to UTC before calling trunc and then converting back to the original timezone after. But it’s something we should only do when we know we actually have a timezone to worry about.