# Reminder and RSVP repair

The owner requested correction of the missing postal-address setting and rapid
yes/no flips. An audit found that the browser automatically posted either
answer on page load. Email security scanning is a plausible explanation for
the observed pairs, but no scanner identity was established.

The candidate adds explicit browser confirmation, rejects unconfirmed reminder
submissions before the function writes or sends anything, and suppresses repeat
notifications for unchanged answers. New links include the event date. The
ordinary site form keeps its existing registration flow.

The reminder receives the owner's previously authorized OneTouch postal address
as a private environment setting and supplies it in paced delivery configuration.
It records prepared and queued states separately, reuses a failed draft and
checks for existing recipient queues before retrying. The October 22 draft's
delivery metadata is corrected without queueing it or changing its date/copy.

The same 18 isolated regression cases report 13 failures on the pre-change
sources and all pass on the candidate. No actual email, attendee response or
contact cleanup is part of this repair. Existing answers are retained because
the historic link traffic does not establish which changes were intentional.

Local evidence: `/Users/devingator/Documents/AITesting/outputs/founders-break-fix-20261022/`.