.gcal.json`. The times are\n clamped to that day, so an event running through it reads `0000-2400`.\n A multi-day event appears under every day it covers.\n- `cat` an event for the unmodified Calendar API payload, including\n attendees, description, location and the original start/end with offsets.\n- `calendar.json` carries the calendar's accessRole and, in\n `bucketTimeZone`, the zone the day directories are bucketed in. That zone\n is mount-wide, so every calendar's `2026-08-11/` covers the same 24 hours.\n- On a calendar shared as free/busy only, Google returns no titles at all,\n so events render as `busy`.\n\nActing on it:\n\n- `rm` an event file to delete that event.\n- Everything else goes through the `gws calendar` CLI, which takes the ids\n the tree renders:\n `gws calendar events insert --params '{\"calendarId\":\"primary\"}' --json ...`\n `gws calendar events patch --params '{\"calendarId\":\"primary\",\"eventId\":\"...\"}'`\n `gws calendar freebusy query --json '{\"timeMin\":...,\"timeMax\":...,\"items\":[{\"id\":\"primary\"}]}'`\n- A written event must carry an explicit UTC offset or timeZone; an\n ambiguous local time is not interpreted for you.\n"; export declare const GCAL_WRITE_PROMPT = "Deleting an event file removes it from the calendar for\nevery attendee. Creating and editing events goes through `gws calendar`.\n"; //# sourceMappingURL=prompt.d.ts.map

export declare const GCAL_PROMPT = "Google Calendar is mounted as one directory per calendar, one\ndirectory per local day, and one JSON file per event.\n\n //primary/calendar.json\n //primary/2026-08-11/__0900-1030_Team_Standup.gcal.json\n //Engineering__team@group.calendar.google.com/2026-08-11/...\n\nReading the tree:\n\n- `ls /` lists the calendars. The primary one is always spelled\n `primary`; every other directory ends in `__`.\n- `ls /primary/` lists ONLY the days that have an event, and ONLY\n within a rolling window around today (30 days back, 90 forward). This is\n a window, not the whole calendar. To look outside it, glob a date:\n `ls /primary/2025-12-*` pushes its own range down to the API.\n- Any well-formed date resolves even when it holds nothing, so\n `ls /primary/2027-03-04/` succeeds and prints nothing. An empty\n listing means the day is free, not that the day is missing.\n- A file name is `___.gcal.json`. The times are\n clamped to that day, so an event running through it reads `0000-2400`.\n A multi-day event appears under every day it covers.\n- `cat` an event for the unmodified Calendar API payload, including\n attendees, description, location and the original start/end with offsets.\n- `calendar.json` carries the calendar's accessRole and, in\n `bucketTimeZone`, the zone the day directories are bucketed in. That zone\n is mount-wide, so every calendar's `2026-08-11/` covers the same 24 hours.\n- On a calendar shared as free/busy only, Google returns no titles at all,\n so events render as `busy`.\n\nActing on it:\n\n- `rm` an event file to delete that event.\n- Everything else goes through the `gws calendar` CLI, which takes the ids\n the tree renders:\n `gws calendar events insert --params '{\"calendarId\":\"primary\"}' --json ...`\n `gws calendar events patch --params '{\"calendarId\":\"primary\",\"eventId\":\"...\"}'`\n `gws calendar freebusy query --json '{\"timeMin\":...,\"timeMax\":...,\"items\":[{\"id\":\"primary\"}]}'`\n- A written event must carry an explicit UTC offset or timeZone; an\n ambiguous local time is not interpreted for you.\n"; export declare const GCAL_WRITE_PROMPT = "Deleting an event file removes it from the calendar for\nevery attendee. Creating and editing events goes through `gws calendar`.\n"; //# sourceMappingURL=prompt.d.ts.map