@mulmoclaude/core 4.10.0 → 5.0.1

package/dist/google/index.js

@@ -5,7 +5,7 @@ import { n as writeFileAtomic } from "../root-BcS4-Kge.js";
 import { fetchWithTimeout } from "../utils/fetch.js";
 import { d as parseIsoDate, f as parseIsoDateTime } from "../itemId-4P9S_ehz.js";
 import { t as mergeIntoExisting } from "../project-B0j_Vf_Q.js";
-import { _t as createForwardingLogger, d as storeFor, n as discoverCollections, rt as getWorkspaceRoot, vt as createHostSlot } from "../discovery-BR8gifOX.js";
+import { _t as createForwardingLogger, d as storeFor, n as discoverCollections, rt as getWorkspaceRoot, vt as createHostSlot } from "../discovery-CBjI1lx9.js";
 import { t as mulmoConfigDir } from "../paths-CkJxNZ7T.js";
 import { promises } from "node:fs";
 import path, { join } from "node:path";
@@ -629,7 +629,13 @@ var toEventSummary = (value) => {
 		status: stringField(record, "status"),
 		colorId: stringField(record, "colorId"),
 		description: stringField(record, "description"),
-		location: stringField(record, "location")
+		location: stringField(record, "location"),
+		recurringEventId: stringField(record, "recurringEventId"),
+		originalStartTime: eventTime$1(record.originalStartTime),
+		updated: stringField(record, "updated"),
+		transparency: stringField(record, "transparency"),
+		eventType: stringField(record, "eventType"),
+		hangoutLink: stringField(record, "hangoutLink")
 	};
 };
 var toCalendarSummary = (value) => {
@@ -1435,10 +1441,14 @@ function toCollectionRecord(event, map, primaryKey, fields) {
 }
 //#endregion
 //#region src/google/pushPlan.ts
-/** The event fields Google lets a caller write. `htmlLink` and `status` are
-*  read-only, so a record column mapped to either is ignored here rather than
-*  rejected — the mapping was authored for the pull, and a push has no business
-*  invalidating it. */
+/** The event fields Google lets a caller write — a SUBSET of what the pull can
+*  read (`GOOGLE_CALENDAR_SOURCE_FIELDS`). A column mapped to one of the
+*  pull-only fields is ignored here rather than rejected: the mapping was
+*  authored for the pull, and a push has no business invalidating it.
+*
+*  `satisfies` is what keeps the two lists honest. A field pushable but not
+*  pullable could never have its baseline rebuilt from a pull, so "unchanged"
+*  would stop meaning anything — this fails the build instead of shipping. */
 var PUSHABLE_SOURCE_FIELDS = [
 	"summary",
 	"start",
@@ -1496,13 +1506,28 @@ var comparableText = (value) => {
 	const text = fieldText(value);
 	return SECONDLESS_DATETIME_RE.test(text) ? `${text}${WHOLE_MINUTE}` : text;
 };
+/** The event fields a baseline does NOT carry, because none of them is pushable
+*  — the baseline exists to answer "did the local side change a field we could
+*  send?", and a pull-only field is by definition not one.
+*
+*  Typed as the exact complement of `ShadowEvent` + `id`, so a field added to
+*  `CalendarEventSummary` without being made pushable must be zeroed here or
+*  the build fails. */
+var UNPUSHABLE_EVENT_FIELDS = {
+	htmlLink: "",
+	status: "",
+	recurringEventId: "",
+	originalStartTime: "",
+	updated: "",
+	transparency: "",
+	eventType: "",
+	hangoutLink: ""
+};
 /** A baseline shaped as the event it came from, so the comparison can run
-*  through the very projection that wrote the record. `htmlLink`/`status` are
-*  never pushable, so their absence from the baseline cannot matter. */
+*  through the very projection that wrote the record. */
 var asEventSummary = (eventId, shadow) => ({
 	id: eventId,
-	htmlLink: "",
-	status: "",
+	...UNPUSHABLE_EVENT_FIELDS,
 	...shadow
 });
 /** What the record WOULD hold if nobody had edited it since the baseline.