v1.1.0 — Google Calendar integration

Highlights

Google Calendar integration, end to end

Link your Google account once — then use Calendar from the chat agent, the settings screen, and your phone:

• Local desktop OAuth (loopback + PKCE) — the refresh token is stored only on your machine, never sent to any cloud (the gcloud / gh CLI trust model). One consent covers calendar.events, tasks, and drive.file (Tasks / Drive tools follow in #2115). (#2110)
• Settings → Plugins → Google — link / status / unlink UI with actionable guidance for missing or ambiguous OAuth client credentials. (#2113)
• Chat agent google tool — new @mulmoclaude/google-plugin preset: "add this to my calendar" just works; when the account isn't linked the agent guides you through linking via the new error-recovery help. (#2120)
• Phone remote commands — google.calendar.createEvent / listEvents over the Firestore command channel; the token stays on the host. (#2110)

mulmoScript: per-beat generate / play (#2119)

Generate or play each beat individually from the script editor, with real generation errors surfaced.

Collections engine consolidation (#2116, #2118)

Collection rollups; manageCollection extracted into @mulmoclaude/core/collection/server so both hosts share one engine. Malformed stored files now downgrade to a row rejection instead of failing a whole merge-mode put.

📦 npm: mulmoclaude@1.1.0

Full Changelog

See CHANGELOG.md for the complete list.