Platform confirms no event-envelope or lead-lifecycle schema change is needed for re-emitting lead.handoff.context.recorded with replacement lesson context; the v1 anyOf branch already carries first_lesson_id and credit_reservation_id

Platform confirms: no event-envelope or lead-lifecycle schema change is needed for re-emitting lead.handoff.context.recorded with the replacement lesson context. The lead.handoff.context.recorded-v1.json schema already carries first_lesson_id and credit_reservation_id in its anyOf branch for single-lesson closes; re-emitting the event with updated values is conformant with v1 as written. The event envelope carries a new event_id on each emission by construction, so re-emission is correct envelope behavior with no special handling. No version bump to the lead-lifecycle contract is required by this rebooking path. Sales can proceed with the re-emit as described.