Trello Butler scheduled rules drift across time zones without a board-level anchor

In current Trello Butler, calendar-style scheduled rules execute server-side, but the effective time zone governing those schedules appears to be inherited from the rule author's profile rather than an explicit board-level setting. On boards with members across multiple time zones, this creates a mismatch: the same rule can appear to run at different local hours without any visible change to the rule definition, and there is no documented way to anchor it to a single canonical zone.

Daylight saving time transitions add further ambiguity in the current scheduling model. A wall-clock rule may shift relative to UTC during DST changes, yet the behavior is not clearly specified. Because execution is server-side, the browser's local time zone does not influence when a rule fires, which makes ad-hoc manual testing unreliable. Additionally, when a board is copied or created from a template, Butler rules are carried over but retain the original author's scheduling context instead of adopting the copying user's zone.

Is there a documented method to pin a Butler schedule to a canonical time zone independent of the author's profile? How do existing rules behave across DST boundaries, and does board copying preserve or reset the inherited scheduling context? What controlled verification approach can confirm which time zone actually drives execution?