FA-77332 / Calendar recurrence rules / Member archive

Next due date for a recurring task after completions: catch up · case 02

A scheduled task completed late on its next due date stays due that same day.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

A recurring task first due on first_due repeats every interval_days. Completions are processed in chronological order. mode "regenerate": the next due date is completion + interval. mode "schedule": completing advances to the next scheduled due date, skipping every scheduled date on or before the completion date. If the resulting due date passes until (inclusive bound, may be None), the task has no next due date (None).

Why this case matters

Recurring calendar series are expanded into concrete instances for display, reminders and conflict checks.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
regression: late completion on next due	`"2024-01-08"`	`"2024-01-15"`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.