DST Bug Fix (March 2026)

The MarketTimes indicator was showing London and Frankfurt times one hour ahead during the period between US and
European daylight saving transitions (March 8–29, 2026).

What was happening

The code that determines whether British Summer Time (BST) is active used a shortcut range check to avoid expensive
date calculations. That range started from the beginning of March, effectively treating the entire month as "BST
active." In reality, BST doesn't start until the last Sunday of March — this year, March 29th. Because both London and
Frankfurt use the BST zone, both were getting an extra hour added to their displayed times from March 1st onwards,
roughly four weeks too early.

What was fixed

The range check now starts from April 1st, so all of March is handled by the precise last-Sunday-of-March calculation
that was already in the code but was being bypassed. The same fix was applied to the equivalent US daylight saving
range check, which had the same issue but hadn't been noticed yet because the dates happened to line up this year.
Several incorrect "find the nth Sunday" formulas were also replaced with the correct helper methods that already
existed in the codebase.

Who is affected

Anyone using the MarketTimes indicator during the gap between US and European clock changes — typically two to three
weeks each March and November. The displayed market session times for London and Frankfurt would be one hour ahead
during this window. New York, Sydney, and Tokyo were unaffected.

Fixed opening and closing times for all markets