refactor: centralise user timezone as standalone setting #10

Merged
bvandeusen merged 0 commits from dev into main 2026-03-25 20:38:48 -04:00
bvandeusen commented 2026-03-25 20:38:38 -04:00 (Migrated from git.fabledsword.com)

Summary

  • Browser timezone synced to user_settings["user_timezone"] on every login/page load
  • Briefing scheduler reads from user_timezone setting; briefing_config.timezone kept as fallback only
  • LLM context falls back to stored user_timezone when not sent in request (covers MCP/API calls)
  • Removed timezone field from BriefingConfig interface and all briefing UI — no longer a manual setting
## Summary - Browser timezone synced to `user_settings["user_timezone"]` on every login/page load - Briefing scheduler reads from `user_timezone` setting; `briefing_config.timezone` kept as fallback only - LLM context falls back to stored `user_timezone` when not sent in request (covers MCP/API calls) - Removed `timezone` field from `BriefingConfig` interface and all briefing UI — no longer a manual setting
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bvandeusen/FabledScribe#10