The first-phase tolerance check in handleCreateScheduleErrors rejected
updates where the caller-supplied starts_at reflected the persisted
(historical) phase start. Downstream Stripe execution anchors phase 0
to the existing schedule's current_phase.start_date anyway, so the
guard only makes sense for creation. Early-return when an existing
stripeSubscriptionSchedule is present, and cover the behavior with a
unit spec.
Made-with: Cursor
66c97b9a38