refactor: centralise user timezone as standalone setting #10

2026-03-25T20:38:38-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

bvandeusen referenced this issue from a commit

2026-07-25 22:48:03 -04:00

fix(acl): make the visibility predicates pure builders; repair CI

bvandeusen referenced this issue from a commit

2026-07-28 12:55:08 -04:00

fix(ci): use uv sync --frozen — --locked needs a lock this box can't regenerate

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bvandeusen/FabledScribe#10