For Stakeholders

What shipped

A small, two-bug fix PR (5 files, ~34 lines added). No schema changes, no new UI, no feature flags. Low risk, narrow blast radius.

Why it matters

Both bugs were silent failures — the kind that erode trust in the product without ever generating a visible error:

• A save button that looked normal but quietly refused to save one

specific kind of edit (calendar break times).

• Patient-tag data that looked correct on the patient record but was

stale wherever WhatsApp conversations kept their own copy — which could make WhatsApp tag-based automation silently not fire for a tagged patient.

Neither produces an error message a user can screenshot and report precisely, which is exactly why bugs like this tend to live undetected for a long time and show up as vague, hard-to-reproduce complaints ("the button just doesn't work sometimes"). Fixing them removes a recurring source of support ambiguity more than it adds visible value.

Risk assessment

• Calendar button fix: pure client-side logic change (one boolean

operator). No data migration, no backend change. Risk: very low.

• Tag sync fix: changes what a transactional mutation writes

(editLead, addNewPatient), scoped to OnlineConversation.patientTags only. Both already ran inside existing Prisma transactions, so the new writes inherit the same atomicity/rollback guarantees as the rest of the mutation. Risk: low, but it does mean slightly more database writes per lead edit (only when tags actually changed, thanks to the added tagsChanged check) and per new-patient-from-conversation creation.

What this PR does not do

• It does not backfill or repair existing conversations whose tags were

already stale before this shipped — see the limitation noted in WhatsApp Conversation Tag Sync and For Support. If leadership wants existing data corrected proactively, that would be a separate, explicit backfill task.

• It does not change how tags are edited anywhere in the product — no new

screens, no new permissions.

Recommended framing if this comes up externally

Routine quality fix, not a feature. See For Marketing.