@mulmoclaude/core 1.2.1 → 1.4.0

package/README.md

@@ -0,0 +1,49 @@
+# @mulmoclaude/core
+
+Shared server-side core for **MulmoClaude** and **MulmoTerminal** — the
+subsystems the two hosts always ship together, consolidated behind subpath
+exports so they cannot drift apart.
+
+Not a general-purpose library: it exists so one implementation of collections,
+wiki, feeds, Google integration, scheduling and the rest serves both hosts.
+Every host specific (paths, logging, notification transport, …) is injected
+rather than imported, which is what lets the same code run under either.
+
+## Subpath exports
+
+| Area | Entries |
+| --- | --- |
+| Collections | `./collection`, `./collection/server`, `./collection/paths`, `./collection/registry`, `./collection/registry/server`, `./collection-watchers` |
+| Knowledge | `./wiki`, `./wiki/server`, `./wiki/paths`, `./feeds`, `./feeds/server`, `./feeds/paths` |
+| Google | `./google` — OAuth (loopback + PKCE), token store, Calendar / Tasks / Drive REST |
+| Runtime | `./scheduler`, `./notifier`, `./skill-bridge`, `./file-change`, `./workspace-setup`, `./artifacts` |
+| Remote | `./remote-host`, `./remote-host/server`, `./remote-view` |
+| Voice | `./whisper`, `./whisper/client` |
+| Plugin support | `./plugin-vue`, `./plugin-vue/i18n` |
+| Utilities | `./utils`, `./files`, `./fetch` |
+
+**Server-only**, except the browser-safe entries: `./artifacts`,
+`./whisper/client`, `./workspace-setup/slug`, `./translation/client`,
+`./remote-view`, `./remote-host` and `./plugin-vue`.
+
+The package also ships `assets/helps/*` — the help documents the agent reads at
+runtime — which is why a change there alone still warrants a release.
+
+## About MulmoClaude and MulmoTerminal
+
+- **[MulmoClaude](https://github.com/receptron/mulmoclaude)** — an AI-native
+  application platform built on Claude Code. Chat summons the right GUI for each
+  task (documents, charts, forms, wikis, spreadsheets, 3D scenes), and
+  everything your assistant accumulates stays as plain files in your own
+  workspace, on your own machine.
+- **[MulmoTerminal](https://github.com/receptron/mulmoterminal)** — run a whole
+  team of coding agents from your browser. Many Claude Code / Codex sessions at
+  once in a grid, colour-coded so you see which are working, which need you and
+  which are done, plus git worktrees, one-click PRs and cost readouts. One `npx`
+  command, no Electron, no config.
+
+📖 **User guide**: <https://receptron.github.io/mulmoterminal/> (日本語 / English)
+
+## License
+
+MIT

package/assets/helps/google-calendar-collection.md

@@ -5,8 +5,10 @@ Add a `googleCalendar` block to its `schema.json` and the host pulls changed
 events on a schedule and writes them as records — **without calling you**. No
 tool call, no tokens spent per sync, so hourly syncing is free.
 
-This is the only calendar mechanism: there is no calendar tool and no bundled
-calendar collection. You author the schema when the user asks for one.
+This is the mechanism for *keeping a collection fresh*. For one-off reads and
+for creating / editing / deleting events, use the `google` tool — see
+[The `google` tool](google.md). There is no bundled calendar collection: you
+author the schema when the user asks for one.
 
 ## Requirements
 
@@ -57,6 +59,15 @@ Declaring it in `map` is a schema error.
 Use `datetime` (not `date`) for start/end when events have real clock times —
 the calendar day view then draws each record as a proportional time block.
 
+## When sync runs
+
+- **On creation** — the first sync starts as soon as the schema lands, so the
+  collection is not empty while the user waits for the schedule. The same
+  applies when you add a `googleCalendar` block to an existing collection.
+- **Hourly** after that, in the background.
+- **On demand** — the collection view has a Sync button. Tell the user about it
+  if they want the calendar refreshed right now.
+
 ## What sync does
 
 - New or edited events are written, keyed by event id (existing records are

package/assets/helps/google.md

@@ -0,0 +1,94 @@
+# The `google` tool — Calendar, Tasks and Drive
+
+One tool, one `kind` per operation, against the Google account the user linked
+on this machine. The refresh token is stored locally in `~/.config/mulmo/` and
+goes only to Google, to mint access tokens — never to claude.ai or any other
+service. This works with no claude.ai Google connector involved.
+
+Call `kind: "status"` when unsure whether the account is linked. If a call fails
+with "Google account not linked", ask the user to link it in settings and retry
+the original call — do not fall back to guessing.
+
+## Two mechanisms, different jobs
+
+| You want | Use |
+| --- | --- |
+| Read or change specific events / tasks / files, right now | this tool |
+| A collection that mirrors a calendar and keeps itself fresh | a `googleCalendar` block — see [Google Calendar sync](google-calendar-collection.md) |
+
+The collection route costs no tokens per refresh, so prefer it for anything
+recurring. Use this tool for one-off work and for everything the collection
+route cannot do (creating, editing and deleting).
+
+## Calendar
+
+Events default to the user's **primary** calendar. Pass `calendarId` — obtained
+from `calendarListCalendars` — to target another.
+
+| kind | What it does |
+| --- | --- |
+| `calendarListCalendars` | The calendars the user has added/subscribed to: `id`, `summary`, `primary`, colours, `accessRole` |
+| `calendarColors` | Palettes mapping a `colorId` to hex, for events and for calendars |
+| `calendarListEvents` | Upcoming events. Optional `calendarId`, `timeMin`, `maxResults` (1-50, default 10) |
+| `calendarSync` | Only what CHANGED since the last sync, via a stored token. Returns counts plus a capped sample |
+| `calendarCreateEvent` | Create. Requires `summary`, `start`, `end`; optional `description`, `calendarId`, `colorId` |
+| `calendarUpdateEvent` | Edit in place. Requires `eventId` + at least one of `summary`, `start`, `end`, `description`, `colorId` |
+| `calendarDeleteEvent` | Delete. Requires `eventId` |
+
+**Date-times must carry a timezone offset** — `2026-07-17T09:00:00+09:00`, not
+`2026-07-17` and not `2026-07-17T09:00:00`. Calendar rejects the others with an
+opaque 400.
+
+**Editing is a patch.** Fields you omit keep their current value, so changing a
+title needs `eventId` + `summary` and nothing else. `description: ""` clears the
+body. Moving one end of an event still has to leave the start before the end.
+
+**`eventId` comes from `calendarListEvents` or `calendarSync`** — never invent
+one. For a recurring event those kinds return per-occurrence ids, so editing or
+deleting one affects that single occurrence.
+
+**Deleting is not reversible** and removes the event for every attendee. Confirm
+with the user before calling `calendarDeleteEvent`, and say which event you are
+about to remove.
+
+## Tasks
+
+Operate on the user's default task list unless `taskListId` is given.
+
+| kind | What it does |
+| --- | --- |
+| `taskListsList` | The user's task lists (`id`, `title`). Only needed for a non-default list |
+| `tasksList` | List tasks. Optional `taskListId`, `maxResults` (1-50, default 10), `showCompleted` (default false) |
+| `tasksCreate` | Add a task. Requires `title`; optional `notes`, `due`, `taskListId` |
+| `tasksUpdate` | Edit. Requires `taskId` + at least one of `title`, `notes`, `due`. `notes: ""` clears them; `due` can be changed but **not** cleared |
+| `tasksComplete` | Mark done. Requires `taskId` |
+| `tasksDelete` | Delete. Requires `taskId` — not reversible, so confirm first |
+
+`tasksUpdate` does not change status: `tasksComplete` owns that transition.
+
+**Google stores a DATE only for `due`** — the time part is accepted and then
+ignored, so never promise the user a time of day on a task.
+
+## Drive
+
+In practice this app sees **only the files it created itself**, never the user's
+wider Drive. Never claim to have searched their Drive.
+
+(The `drive.file` scope also covers files the user hands to an app through a
+Google Picker, but this app has no Picker — so app-created is the whole set.)
+
+| kind | What it does |
+| --- | --- |
+| `driveList` | Files this app created. Optional `maxResults` (1-50, default 10) |
+| `driveCreate` | Create a text file. Requires `name`, `content`; optional `mimeType` (default `text/plain`) |
+| `driveRead` | Read one of this app's files. Requires `fileId`. Text only |
+
+## Failure modes
+
+- **"Google account not linked"** — the user has not linked, or the token was
+  revoked. Ask them to link in settings; do not retry blindly.
+- **HTTP 403 naming an API** — that API is not enabled for the user's Cloud
+  project. The message says which one.
+- **HTTP 400 on a create/update** — almost always a date-time without an offset,
+  or a start that is not before the end.
+- **HTTP 410 on delete** — the event was already gone.

package/assets/helps/index.md

@@ -72,6 +72,7 @@ See [Wiki](config/helps/wiki.md) for details on how it works.
 - [Remote host](config/helps/remote-host.md) — drive MulmoClaude from a phone at mulmoserver.web.app: Google sign-in connect, host online vs. offline (queued chats, 7-day expiry), photo attachments, and the security model
 - [Feeds](config/helps/feeds.md) — register a self-refreshing data feed (RSS/Atom/JSON) by authoring `feeds/<slug>/schema.json`: schema shape, the `ingest` block, raw-item field mapping, and `maxItems` retention
 - [Google Calendar sync](config/helps/google-calendar-collection.md) — mirror a Google calendar into a collection with a `googleCalendar` block: field mapping, why the primary field holds the event id, and how deletions propagate
+- [The `google` tool](config/helps/google.md) — every `kind` for Calendar, Tasks and Drive: reading, creating, editing and deleting events and tasks, the timezone-offset rule, patch semantics, and what `drive.file` scope cannot see
 - [GitHub repositories in the workspace](config/helps/github.md) — clone-destination rules under `github/<name>/` and how to handle existing directories with matching or different remotes
 - [Collection skills](config/helps/collection-skills.md) — build a data app (model + UI + relations + computed fields + action buttons) by authoring a `schema.json` collection skill: the DSL, field types, derived formulas, actions, records
 - [Custom views](config/helps/custom-view.md) — give a collection a view the built-ins don't cover (year/quarter overview, Gantt): an HTML file under `views/`, registered in `schema.json`, rendered in a sandboxed iframe over the records

package/dist/collection/registry/server/index.cjs

@@ -2,10 +2,11 @@ Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 const require_rolldown_runtime = require("../../../rolldown-runtime-D6vf50IK.cjs");
 const require_dist = require("../../../dist-pWpC-b04.cjs");
 const require_atomic = require("../../../atomic-C_7YpMiM.cjs");
+const require_relPath = require("../../../relPath-CgGi4-Nv.cjs");
 const require_utils_fetch = require("../../../utils/fetch.cjs");
 const require_discovery = require("../../../discovery--kRUWed0.cjs");
 const require_templatePath = require("../../../templatePath-27vUZowm.cjs");
-const require_server = require("../../../server-w5ZZRLju.cjs");
+const require_server = require("../../../server-gEOeV_Nv.cjs");
 const require_skill_bridge_index = require("../../../skill-bridge/index.cjs");
 const require_types = require("../../../types-CNqkLT4M.cjs");
 let node_fs = require("node:fs");
@@ -905,7 +906,7 @@ async function writeCollectionExport(params) {
 	});
 	return {
 		ok: true,
-		outputPath: node_path.default.relative(wsRoot, outDir).split(node_path.default.sep).join("/"),
+		outputPath: require_relPath.toPosixRelPath(node_path.default.relative(wsRoot, outDir)),
 		fileCount: bundleCount + 1,
 		seedCount: seed.count,
 		seedSkipped: seed.skipped,