fix(google): sync task due dates as to-do dates, not link schedules

Google Tasks were synced with a link `schedules` entry built from the
task's due date. Link schedules are shared, calendar-event-shaped
timing, so tasks incorrectly rendered as agenda events — and because a
due date has no end time, the schedule was open-ended, which agenda
views handle poorly.

Tasks are personal to-dos: an open task now sets `todo: true` on the
saved link (with `todoDate` when the task has a due date), which files
it into the connection owner's to-do list scheduled on its due date.
Completed tasks are unchanged — the "done" status already clears the
owner's to-do state.

Adds transformTask unit tests covering due-date, no-due-date, and
completed tasks.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: KrisBraun

connectors/google/src/tasks/sync.test.ts

@@ -19,6 +19,7 @@ import {
   syncBatchFn,
   periodicSyncBatchFn,
   onLinkUpdatedFn,
+  transformTask,
   type SyncState,
   type PeriodicSyncState,
   type TasksSyncHost,
@@ -175,3 +176,50 @@ describe("onLinkUpdatedFn — deleted task/list (404)", () => {
     ).rejects.toThrow(/500/);
   });
 });
+
+describe("transformTask — to-do mapping (no link schedules)", () => {
+  const baseTask = {
+    id: "task-1",
+    title: "Buy milk",
+    status: "needsAction" as const,
+    updated: "2026-07-01T12:00:00.000Z",
+    position: "0001",
+    selfLink: "https://tasks.googleapis.com/tasks/v1/task-1",
+  };
+
+  it("maps an open task with a due date to todo + todoDate", () => {
+    const link = transformTask(
+      { ...baseTask, due: "2026-07-15T00:00:00.000Z" },
+      LIST_ID,
+      false,
+      [],
+      null
+    );
+    expect(link.todo).toBe(true);
+    expect(link.todoDate).toBe("2026-07-15");
+    // Tasks must never carry link schedules: those are shared,
+    // calendar-event-shaped, and would render the task in the agenda.
+    expect(link.schedules).toBeUndefined();
+  });
+
+  it("maps an open task without a due date to todo (Now bucket)", () => {
+    const link = transformTask(baseTask, LIST_ID, false, [], null);
+    expect(link.todo).toBe(true);
+    expect(link.todoDate).toBeUndefined();
+    expect(link.schedules).toBeUndefined();
+  });
+
+  it("leaves to-do state untouched for completed tasks (done status handles it)", () => {
+    const link = transformTask(
+      { ...baseTask, status: "completed", due: "2026-07-15T00:00:00.000Z" },
+      LIST_ID,
+      false,
+      [],
+      null
+    );
+    expect(link.status).toBe("done");
+    expect(link.todo).toBeUndefined();
+    expect(link.todoDate).toBeUndefined();
+    expect(link.schedules).toBeUndefined();
+  });
+});

connectors/google/src/tasks/sync.ts

@@ -523,13 +523,17 @@ export function transformTask(
     status: task.status === "completed" ? "done" : "open",
     notes,
     preview: task.notes?.slice(0, 200) || null,
-    ...(task.due
+    // Google Tasks are the user's personal to-dos, never calendar events:
+    // surface an open task as the connection owner's to-do (per-user
+    // thread_state), with the due date as its to-do date when present. A
+    // link `schedules` entry is wrong here — it creates a *shared* schedule
+    // with calendar-event semantics, which renders the task in the agenda.
+    // Completed tasks need nothing: the "done" status already clears the
+    // assignee's to-do state via the platform's done-status handling.
+    ...(task.status !== "completed"
       ? {
-          schedules: [
-            {
-              start: task.due.split("T")[0],
-            },
-          ],
+          todo: true,
+          ...(task.due ? { todoDate: task.due.split("T")[0] } : {}),
         }
       : {}),
     ...(initialSync ? { unread: false } : {}),