FabledScribe

Files

T

bvandeusen 62dbb8d496 refactor: centralise user timezone as a standalone setting

Browser timezone is now synced to user_settings["user_timezone"] on
every login/page load (App.vue). The briefing scheduler and LLM context
both read from this single source, falling back to the legacy
briefing_config.timezone for existing users during migration.

- App.vue: PUT /api/settings with browser IANA timezone on startAppServices
- routes/chat.py: fall back to stored user_timezone when not sent in request
- briefing_scheduler: read user_timezone setting; briefing_config.timezone
  kept as fallback only
- routes/briefing.py: pass tz_override from user_timezone to live-patched scheduler
- Remove timezone field from BriefingConfig interface and all briefing UI

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-25 20:17:51 -04:00

models

feat(rag): RAG scoping and context isolation controls

2026-03-25 17:44:39 -04:00

routes

refactor: centralise user timezone as a standalone setting

2026-03-25 20:17:51 -04:00

services

refactor: centralise user timezone as a standalone setting

2026-03-25 20:17:51 -04:00

static

Initial commit: note-taking/task-tracking app with LLM integration scaffold