How does detaspace manage regional time‑zone conversions during daylight‑saving transitions?

Applications often receive date‑time values from users in various regional zones and must store or compare them in a unified format.

When the source zone observes daylight saving time, certain local times become ambiguous (overlap) or nonexistent (gap) during the transition, and the platform must decide how to map these values without losing the user's intention.

How does detaspace expose the underlying zone‑rule data so developers can detect overlap or gap conditions? What options exist for choosing the earlier or later offset when an ambiguous time is encountered? Is there a built‑in way to serialize a time‑zone‑aware value together with its rule set for later reconstruction?