Timezone scope limits for admin grids and cron boundaries in Magento

Magento persists date/time values in the database in UTC and converts them to the configured store timezone for storefront and many admin displays. The timezone is configured per store scope in locale options. However, the exact timezone that governs admin order grids, report filters, and cron execution boundaries remains scope- and version-sensitive.

In a multi-store setup with non-UTC timezones, the same UTC instant can appear with different local dates depending on whether the context is storefront, admin, or CLI. This creates ambiguity near local midnight and DST transitions, where a record stored at 23:30 UTC might display as the previous or next day in different interfaces.

When building custom modules or integrations, injecting the framework timezone resolver is preferred over direct PHP date functions, since server time, store time, and UTC can differ within the same request. Yet it remains unclear whether admin users see their account timezone, the store default, or the server timezone for grid filters and report ranges.

Which timezone governs admin grid filters and report boundaries in the target Magento version, and does cron use the server timezone or a store-scoped timezone when evaluating schedule windows?