[BenCodez]

Summary

Consolidate the duplicated Bukkit/proxy time arithmetic and harden time-change lifecycle handling without changing configured offsets or event order.

• add TimeCalculation as the shared timezone/hour-offset/week-number implementation
• add clock-aware constructor overloads so time behavior can be tested deterministically while existing constructors keep system-clock behavior
• use the shared calculation in both TimeChecker and BungeeTimeChecker
• retain locale-based week numbering and the existing week-day offset semantics
• fall back to the local clock zone with a warning when a configured zone is invalid
• guarantee Bukkit activeProcessing and proxy processing flags are reset in finally
• fix the proxy failure mode where an exception from timeChanged(...) could leave processing permanently stuck
• make proxy shutdown null-safe and timer-load logging independent of the Bukkit singleton
• replace raw time-processing stack traces with contextual logging/debug paths

Tests

• fixed-clock timezone/DST and hour-offset calculation
• week calculation with configured day offset
• regression proving a failed proxy time-change does not leave future processing blocked

Existing day/week/month public APIs and event ordering remain intact.

[chatgpt-codex-connector]

You have reached your Codex usage limits for security reviews. Please try again later.