FA-59395 / Subscription proration billing / Member archive

Month-end anchored renewal dates: leap-year month length · case 05

Renewals in February of a leap year land on the 28th instead of the 29th.

Member previewVariant 5 · 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	`[[2020, 2, 28], [2020, 8, 31], [2021, 2, 28], [2021, 8, 31], [2022, 2, 28], [2022, 8, 31], [2023, 2, 28], [2023, 8, 31], [2024, 2, 28], [2024, 8, 31], [2025, 2, 28], [2025, 8, 31]]`	`[[2020, 2, 29], [2020, 8, 31], [2021, 2, 28], [2021, 8, 31], [2022, 2, 28], [2022, 8, 31], [2023, 2, 28], [2023, 8, 31], [2024, 2, 29], [2024, 8, 31], [2025, 2, 28], [2025, 8, 31]]`	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.