Regional timestamp stored with unexpected offset in Liquibase TIMESTAMP column

Liquibase delegates timestamp binding to the JDBC driver, so a zone-offset date-time inserted into a TIMESTAMP or TIMESTAMPTZ column can be stored with an unexpected offset. The stored instant may depend on the driver, column type, JVM default time zone, and database session time zone. Offline changelog validation does not detect this runtime shift.

Goal: determine whether Liquibase normalizes regional input values to UTC before binding, or leaves conversion to the driver and database. Exact behavior may vary by Liquibase version and driver release.

• Does Liquibase convert zone-offset timestamps to UTC before JDBC binding for TIMESTAMP columns?
• Is the stored instant stable across different JVM default time zones and database session time zones?
• Does behavior differ between Liquibase versions and between TIMESTAMP and TIMESTAMPTZ columns?