fix: missed-reservation email — format its times, and alert on the week actually missed

[pataniaeli]

On the logo, which is what #99 was reported for: not a code bug. Outlook was blocking the images because the sender is not trusted there. Production had the correct <img> and a working URL at the time the email was sent — verified below. Nothing in this PR addresses it, and no Closes line: #99 should be closed on its own merits.

Two real defects in the missed-reservation alert, found while looking for that one.

1. It rendered raw times

Time of Reservation: 18:30:00 to 20:00:00

where every other Chambers email says 6:30 PM to 8:00 PM. This template did not move when the booking emails were rewritten in #84. Verified by rendering both templates from dev side by side. Both shapes the codebase produces are handled now — Postgres returns HH:MM:SS, the forms submit HH:MM.

It also took its date already formatted, via a second copy of the date formatter under a different name (formatDateLong, character-for-character what changes.formatDate already did). That is likely why the raw times survived: the one value the caller prepared looked right, and the two it passed straight through did not. The template formats its own values now and the duplicate is gone. The subject follows the house style — an em dash rather than Chambers Alert - .

The room or table is now named, since the point of the alert is that a room went unused. A body with no leadership on file reads Contacts: None on file rather than trailing off after the colon.

2. It alerted on the wrong week, forever

The weekly caller asked "is anything Missed", then described the alert using the series' start date and time regardless of which week was missed. A series where week 7 was missed told Operational Affairs about week 1 — the same defect as #91, in the one caller that rewrite did not reach.

Worse: a missed week stays Missed, so the condition stayed true permanently. Every later edit to the series sent another alert about a week they had been told about weeks earlier, with the wrong date on it.

movedOccurrences — added by #91 to answer exactly this question — is what this save changed, so a week alerts on the edit that missed it and not again. A series-level Missed is compared against the stored value for the same reason. One alert per missed reservation rather than per save: each missed room is its own incident, and one email naming one of several would hide the rest.

What was checked on the logo

• main contains 9367c83, which pointed LOGO_URL at opsemaillogo.png; there had never been an sga-logo.png, so the footer logo 404'd in every transactional email until v1.14.0.
• Production is serving v1.14.0, and https://chambers.northeasternsga.com/opsemaillogo.png returns 200 image/png, 59,633 bytes, Content-Disposition: inline, CORS open.
• The <img> this template emits is byte-identical to the one in booking-updated, which renders fine.

So the markup and the asset were both correct; the recipient's client declined to load it.

Verification

npm run build, tsc and eslint clean, rebased onto current dev (post-#97). Templates rendered by intercepting Resend, with HH:MM:SS and HH:MM inputs and an empty contacts list; markup checked for balance.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
chambers	Ready	Preview	Sep 10, 2026 12:41am UTC