archive-event

Archive an event from a source

Turning "here is the notice" into a calendar entry requires judgements the 29 EventKit tools will never prompt for. Two of those judgements fail silently — the event is created, the calendar looks normal, and the content is wrong:

• The time was superseded. A notice goes out, then the organizer corrects it. Reading only the first message puts the wrong day in the calendar.
• An estimated value reads as a stated fact. Notices often omit the end time. An estimate that is not labelled is indistinguishable, later, from something the source actually said.

Failures that raise an error can live in a README — the reader will look it up. Silent failures cannot, because nobody knows to look. That is what this skill is for.

What already exists — do not rebuild it

Conflict checking exists as a tool — this skill still invokes check_conflicts itself before any create (it does not go through quick-event, so it inherits nothing). What it adds are the five judgements that no existing mechanism covers.

Procedure

source ──▶ 1. authoritative time ──▶ 4. which calendar ──▶ 3. compose notes
                                                               │
                              2. update or create  ◀───────────┘
                              （check_conflicts before create）
                                            │
                                            └──▶ 5. same-day deadlines