Release v1.14.0 · themotionmachine/OmniFocus-MCP

What's Changed

Repeating tasks and projects can now be created and edited (#116). Previously no write tool could set a repetition rule, so every recurring item an assistant created arrived inert and needed a manual trip to the OmniFocus inspector. add_omnifocus_task, add_project, and each batch_add_items item now accept a repeat object; edit_item accepts newRepeat (pass null to clear). You describe the schedule and the server compiles the ICS recurrence rule:
```
{ "method": "start-after-completion", "unit": "week" }
{ "method": "fixed", "unit": "week", "steps": 2, "weekdays": ["TU","TH"] }
```
method is worth choosing deliberately — with fixed, occurrences appear on schedule whether or not the last was completed, so a missed week leaves a backlog; with start-after-completion, the next occurrence is scheduled from when you actually finish, so the habit simply resumes. Positional rules ("third Tuesday") and end conditions (COUNT/UNTIL) are not supported and report a clear error. See Repeating items.
Clients attached to an outdated daemon are told, in-band (#113). After an upgrade, a long-lived client keeps its old daemon indefinitely, and nothing used to say so. While a newer daemon is serving, each tool result now carries a one-line notice to reconnect. Liveness-probed so an orphaned socket can't nag, throttled, and skipped for isolated instances.

query_omnifocus returns the actual repetition rule (#115). The repetitionRule field emitted the literal string "[object Task.RepetitionRule]" — the object wrapper rather than the rule — so a client could tell that an item repeated but never how. It now returns the ICS string (e.g. FREQ=WEEKLY;INTERVAL=2), alongside a new repetitionMethod field (Fixed / DeferUntilDate / DueDate). Available on tasks and projects.

Full Changelog: v1.13.0...v1.14.0