create an event, newest day first, and a URL you can read

three small things, one of which turned out to be a bug in what shipped an hour
ago.

CREATE. a POST to /_officer/event, and the SIDECAR builds the file — the browser
sends title, when and where. a UID, a DTSTAMP and a UTC timestamp each have
exactly one correct form, and that belongs next to the parser that reads them
back, not in a react component. it writes the minimum a VEVENT can legally be:
no recurrence, no alarms, no attendees. this app cannot show those, and a field
the list cannot display is a field that silently disappears on the next edit.

times go in as UTC. the alternative is DTSTART;TZID plus a VTIMEZONE block
defining that zone's rules, and a subtly wrong VTIMEZONE moves an event by an
hour twice a year. UTC needs no definition and every client renders it local.
all-day is the other trap: RFC 5545 makes DTEND EXCLUSIVE, so a one-day event on
the 29th ends on the 30th — write the 29th and some clients draw nothing at all.
the form takes the last day a person means and the builder adds the day.

NEWEST DAY ON TOP. a calendar accumulates years, so ascending opened on whatever
was imported first and this week was a scroll away. within a day the order stays
chronological, because that is what a day is.

?collection=ra-guide, NOT ?collection=%2Fdav%2F1%2Fra-guide%2F. the path is
/dav/<userId>/<name>/, so the escaped form spent six characters on slashes to
say `ra-guide` and put the owner's user id in a URL people paste at each other.
the name is unique within a user, which is all a selector needs, and the full
path is recovered from the collections list the screen already loaded. a full
path in the param still resolves, because somebody's bookmark has one.

AND THE BUG. setProperty replaced a property's first line and left its
continuation lines behind. a value over 75 octets is FOLDED onto lines starting
with a space — so editing a long summary left the old tail folded onto the new
value, and each edit inherited the last one's ending. it only bites on long
values, which is why the first round of testing missed it. the fix consumes the
whole folded run and folds what it writes; both are now under test, including
the accent-near-the-boundary case that a naive slice(0,75) cuts in half.

verified live: both event shapes written and read back, escaping round-tripped,
and a long summary edited twice with no accumulation.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043

skills/calendar-and-contacts/SKILL.md

@@ -59,6 +59,26 @@ The machine's clock is the owner's timezone. Parse what they said with plain `da
 
 ## Create an event
 
+**The short way, for an ordinary event.** One POST, and the sidecar writes the file — it mints the UID
+and the filename, converts to UTC, escapes the text and folds any line over 75 octets. All the parts
+below that are easy to get subtly wrong.
+
+```bash
+curl -s -H "Authorization: Bearer $OFFICER_AGENT_KEY" -H "Host: $OFFICER_API_HOST" \
+  -H 'content-type: application/json' -X POST "$OFFICER_API_URL/api/caldav/_officer/event" \
+  -d '{"collection":"/dav/1/personal/","summary":"Dinner with my wife","location":"Cervejaria Ramiro",
+       "start":"2026-08-29T19:00:00Z","end":"2026-08-29T21:00:00Z","allDay":false}'
+# {"href":"/dav/1/personal/<uuid>.ics"}
+```
+
+All-day takes plain dates and no times: `{"start":"2026-08-29","allDay":true}`. `end` is the LAST day as
+a person means it — the exclusive DTEND is this route's problem, not yours.
+
+It writes a minimal VEVENT and nothing else. **Anything with a recurrence rule, an alarm or attendees
+has to be written by hand**, below.
+
+## Create an event by hand
+
 The filename must be `<UID>.ics`, and iCalendar lines are **CRLF-terminated**. `DTSTAMP` is required.
 
 ```bash
@@ -73,7 +93,12 @@ printf "BEGIN:VCALENDAR\r\nVERSION:2.0\r\nPRODID:-//Officer//agent//EN\r\nBEGIN:
 ```
 
 An **all-day** event uses dates, not times, and DTEND is the day AFTER:
-`DTSTART;VALUE=DATE:20260829` with `DTEND;VALUE=DATE:20260830`.
+`DTSTART;VALUE=DATE:20260829` with `DTEND;VALUE=DATE:20260830`. Writing the same day produces a
+zero-length event that some clients simply do not draw.
+
+Two more that bite when writing by hand, and are why the JSON route above exists: a comma, semicolon or
+backslash inside a SUMMARY must be backslash-escaped or it splits the value, and a content line over 75
+octets must be folded onto a continuation line starting with one space.
 
 ## Look something up