calendar-synclisted

# Calendar Sync Turns a repo's git commit history for a given day into time-blocked events on that repo's own Google Calendar. Fully autonomous — no approval gate, full CRUD freedom on the target calendar once it's correctly resolved. ## Inputs - `$ARGUMENTS`: Optional date or date range to sync (e.g. "yesterday", "2026-07-10", "2026-07-08 to 2026-07-10"). Defaults to today if omitted. ## Goal Every distinct chunk of work done in the repo during the target date range has exactly one correctly-timed, correctly-titled, >=20-minute event on the repo's mapped calendar — with no duplicates and no events left on the wrong (personal primary) calendar. ## Steps ### 1. Resolve scope and date range Determine the repo root (`git rev-parse --show-toplevel` from cwd) and parse `$ARGUMENTS` into a concrete start/end timestamp range, defaulting to today 00:00–23:59 in the user's local timezone. **Success criteria**: repo root path and a concrete `[start, end]` timestamp range. ### 2. Resolve the target calendar (do not default to primary) Read `~/Desktop/Valor/projects.json`, match the repo root against each project's `working_directory` to find the project slug (e.g. `cyndra-consulting` → `cyndra`). Read `~/Desktop/Valor/calendar_config.json`'s `calendars` map and look up that slug to get the Google Calendar ID. Fall back to the map's `"default"` entry only if no project match is found. **Rules**: - Never silently fall back to the personal primary/"Valor Engels" calendar for a repo