mulmoclaude 1.20.0 → 1.21.0

package/README.md

@@ -156,8 +156,8 @@ Recommended: ≥ 32 characters of random data (shorter values trigger a startup
 - **Marp slides** — `marp: true` frontmatter on any markdown file renders a slide deck in the canvas with PDF export. Custom themes via `config/marp-themes/<name>.css`.
 - **Auto memory** — the agent maintains a typed memory layout (`conversations/memory/<type>/<topic>.md`) and reads it ambient-style.
 - **Web Push on task finish** — enable in Settings → Notifications to get a push on your phone when the answer to a question you asked is ready, even with the browser closed. Requires the RemoteHost connection + a registered device (see [`docs/remote-host.md`](https://github.com/receptron/mulmoclaude/blob/main/docs/remote-host.md#web-push-on-task-finish-2086)).
-- **Google (Calendar / Tasks / Drive)** — link your Google account in Settings → Plugins → Google and consent in the browser; no Google Cloud setup needed. The agent then gets a `google` tool covering the full round trip — list, create, edit and delete calendar events and tasks (including putting a completed task back on the list), plus the Drive files it creates — and the phone remote can trigger the same commands.
-- **Google Calendar ↔ collection sync** — a collection can mirror one of your calendars and keep itself current: the first sync starts as soon as you ask for the collection, an hourly pass follows, and a Sync button forces one. It calls the Calendar API directly rather than routing the events through the agent, so keeping it fresh costs no tokens. A **Push to Google** button beside it sends the other way, creating events for records you added and updating ones you edited — it never deletes, and it skips anything edited on both sides rather than picking a winner. Ask for **two-way sync** and the collection pushes on the same schedule it pulls on, as one cycle, so there is no button to forget; a record the push could not send is then left alone by the pull instead of being overwritten. Without it the pull is automatic and the push is a button, so push before you sync — a pull overwrites a locally edited record as soon as Google reports a change to that event. Event **notes and location** travel in both directions alongside the title, times and colour. **The refresh token stays on your machine** (`~/.config/mulmo/`) — the sign-in service applies the OAuth client secret Google requires and keeps nothing. Prefer your own OAuth client? Drop a *desktop-app* client JSON in `~/.secrets/` and the whole flow stays local (see [`docs/remote-host.md`](https://github.com/receptron/mulmoclaude/blob/main/docs/remote-host.md)).
+- **Google (Calendar / Tasks / Drive)** — link your Google account in Settings → Plugins → Google and consent in the browser; no Google Cloud setup needed. The agent then gets a `google` tool covering the full round trip — list, create, edit and delete calendar events and tasks (including putting a completed task back on the list), plus the Drive files it creates — and the phone remote can trigger the same commands. Events can be timed or **all-day**: ask for a whole day and you get one, rather than a midnight appointment.
+- **Google Calendar ↔ collection sync** — a collection can mirror one of your calendars and keep itself current: the first sync starts as soon as you ask for the collection, an hourly pass follows, and a Sync button forces one. It calls the Calendar API directly rather than routing the events through the agent, so keeping it fresh costs no tokens. A **Push to Google** button beside it sends the other way, creating events for records you added and updating ones you edited — it skips anything edited on both sides rather than picking a winner. It does not delete unless you ask it to: a collection can opt in so that removing a record removes the event, and even then it refuses any event with attendees rather than withdrawing it from their calendars. Ask for **two-way sync** and the collection pushes on the same schedule it pulls on, as one cycle, so there is no button to forget; a record the push could not send is then left alone by the pull instead of being overwritten. Without it the pull is automatic and the push is a button, so push before you sync — a pull overwrites a locally edited record as soon as Google reports a change to that event. Event **notes and location** travel in both directions alongside the title, times and colour, and the mirror can also carry read-only details — your own RSVP, the meeting link, and which recurring series an occurrence came from. **The refresh token stays on your machine** (`~/.config/mulmo/`) — the sign-in service applies the OAuth client secret Google requires and keeps nothing. Prefer your own OAuth client? Drop a *desktop-app* client JSON in `~/.secrets/` and the whole flow stays local (see [`docs/remote-host.md`](https://github.com/receptron/mulmoclaude/blob/main/docs/remote-host.md)).
 
 ## Plugin authoring (`--dev-plugin`)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mulmoclaude",
-  "version": "1.20.0",
+  "version": "1.21.0",
   "description": "MulmoClaude — GUI-chat with Claude Code + long-term memory. One command to start.",
   "type": "module",
   "bin": {
@@ -36,17 +36,17 @@
     "@mulmochat-plugin/ui-image": "^0.4.1",
     "@mulmoclaude/accounting-plugin": "^4.0.0",
     "@mulmoclaude/chart-plugin": "^4.0.0",
-    "@mulmoclaude/collection-plugin": "^5.0.0",
+    "@mulmoclaude/collection-plugin": "^5.1.0",
     "@mulmoclaude/common": "^1.3.0",
-    "@mulmoclaude/core": "^5.1.0",
+    "@mulmoclaude/core": "^5.3.0",
     "@mulmoclaude/form-plugin": "^2.0.0",
-    "@mulmoclaude/google-plugin": "^4.0.0",
+    "@mulmoclaude/google-plugin": "^4.1.0",
     "@mulmoclaude/html-plugin": "^5.0.0",
     "@mulmoclaude/markdown-plugin": "^5.0.0",
     "@mulmoclaude/markdown-utils": "^3.0.0",
     "@mulmoclaude/mulmoscript-plugin": "^5.0.0",
     "@mulmoclaude/shapescript-plugin": "^7.0.0",
-    "@mulmoclaude/spotify-plugin": "^2.0.1",
+    "@mulmoclaude/spotify-plugin": "^2.0.2",
     "@mulmoclaude/x-plugin": "^1.0.4",
     "@receptron/task-scheduler": "^1.0.3",
     "cors": "^2.8.6",

package/server/api/routes/collectionCalendarPush.ts

@@ -9,8 +9,11 @@ export interface CollectionPushBody {
   updated: number;
   /** Edited on both sides — skipped so neither version is lost. */
   conflicts: number;
-  /** Records deleted locally. Reported only: v1 never deletes in Google. */
+  /** Records deleted locally, whether or not the deletion carried. */
   localDeletes: number;
+  /** Of those, how many were deleted in Google too — `0` unless the collection
+   *  opted in with `propagateDeletes` (#3234). */
+  deletedInGoogle: number;
   /** Records that could not be pushed as they stand, each with its reason. */
   skipped: string[];
   errors: string[];
@@ -24,7 +27,16 @@ export const PUSH_NOT_DECLARED_ERROR = "this collection does not declare a `goog
 export const pushReadOnlyError = (accessRole: string): string =>
   `you only have ${accessRole || "read"} access to this calendar — pushing needs owner or writer access`;
 
-const empty = (errors: string[]): CollectionPushBody => ({ pushed: true, created: 0, updated: 0, conflicts: 0, localDeletes: 0, skipped: [], errors });
+const empty = (errors: string[]): CollectionPushBody => ({
+  pushed: true,
+  created: 0,
+  updated: 0,
+  conflicts: 0,
+  localDeletes: 0,
+  deletedInGoogle: 0,
+  skipped: [],
+  errors,
+});
 
 const fromResult = (result: CalendarCollectionPushResult): CollectionPushBody => ({
   pushed: true,
@@ -32,6 +44,7 @@ const fromResult = (result: CalendarCollectionPushResult): CollectionPushBody =>
   updated: result.updated,
   conflicts: result.conflicts,
   localDeletes: result.localDeletes,
+  deletedInGoogle: result.deletedInGoogle,
   skipped: result.skipped,
   errors: result.errors,
 });