fix(time): read timezone from config.yaml as UTF-8

[Tianworld]

hermes_time falls back to config.yaml for HERMES_TIMEZONE. The file was opened without encoding, so on Windows valid UTF-8 YAML could fail to parse and the configured timezone would be ignored.

Made with Cursor

[alt-glitch]

Likely duplicate of #15519 — same root cause: missing encoding='utf-8' on open() calls, covered by the broader cross-platform fix.

[teknium1]

Thanks for the focused Windows compatibility fix.

Automated hermes-sweeper review found this is already implemented on main:

• hermes_time.py:55 now uses read_raw_config(), whose config file open is explicitly UTF-8 at hermes_cli/config.py:6668; its local fallback is also explicit UTF-8 at hermes_time.py:61.
• Commit cbce5e93fcb9a923ab71f45d2a0f0f172dd54967 made the same hermes_time.py change as part of the broader Windows UTF-8 file-open sweep.
• That commit shipped in v2026.5.16.
• This matches the existing maintainer duplicate note pointing to fix: add explicit encoding="utf-8" to open() calls for cross-platform safety #15519; the later duplicate PR fix(hermes_time): read config yaml as utf-8 #17740 was also closed as implemented on main.

Closing as already implemented on main.