FA-59382 / Subscription proration billing / Member archive

Month-end anchored renewal dates: anchor day drift · case 02

After a short month, renewals stay on the 28th or 30th for the rest of the subscription.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

Input {anchor [y,m,d], n, interval months}. Renewal i (1..n) falls interval*i months after the anchor month, on the anchor day clamped to that month's length (so a 31st anchor returns to the 31st whenever possible). Return the list of [y, m, d].

Why this case matters

Month-end anchors must not drift to the 28th after February, and leap years change the clamp.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression 0	`[[2025, 1, 29], [2025, 2, 28], [2025, 3, 28], [2025, 4, 28], [2025, 5, 28], [2025, 6, 28], [2025, 7, 28], [2025, 8, 28], [2025, 9, 28], [2025, 10, 28]]`	`[[2025, 1, 29], [2025, 2, 28], [2025, 3, 29], [2025, 4, 29], [2025, 5, 29], [2025, 6, 29], [2025, 7, 29], [2025, 8, 29], [2025, 9, 29], [2025, 10, 29]]`	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.