use model 0.2.1 for timed recurring due offsets

Author: callumalpass

docs/releases/unreleased.md

@@ -35,3 +35,4 @@ When a change has user-facing documentation, include a canonical tasknotes.dev l
 ## Fixed
 
 - (#1995) Fixed Bases Calendar views showing both a materialized occurrence note and its matching virtual recurring task instance. Thanks to @rdefaccio for reporting this.
+- (Discussion #1994) Fixed timed recurring tasks failing to advance their due dates when due-date offset preservation is enabled. Thanks to @mgrecar for raising this.

package-lock.json

@@ -87,7 +87,7 @@
 		"@fullcalendar/multimonth": "^6.1.17",
 		"@fullcalendar/timegrid": "^6.1.17",
 		"@modelcontextprotocol/sdk": "^1.12.1",
-		"@tasknotes/model": "0.2.0",
+		"@tasknotes/model": "0.2.1",
 		"chrono-node": "^2.7.5",
 		"date-fns": "^4.1.0",
 		"ical.js": "^2.2.1",

package.json

@@ -43,6 +43,23 @@ describe("core/recurrence", () => {
 		});
 	});
 
+	it("preserves due offset for timed recurring tasks", () => {
+		const result = updateToNextScheduledOccurrence({
+			title: "Timed recurring task with due offset",
+			recurrence: "DTSTART:20260328T103000;FREQ=DAILY",
+			recurrence_anchor: "scheduled",
+			scheduled: "2026-03-28T10:30",
+			due: "2026-03-29T10:30",
+			complete_instances: ["2026-03-28"],
+			skipped_instances: [],
+		});
+
+		expect(result).toEqual({
+			scheduled: "2026-03-29T10:30",
+			due: "2026-03-30T10:30",
+		});
+	});
+
 	it("adds DTSTART without depending on a full TaskInfo object", () => {
 		const recurrence = addDTSTARTToRecurrenceRule({
 			recurrence: "FREQ=DAILY;INTERVAL=2",