fix: remove misspelled selector default and notify on monitor downgrade

[bd73-com]

Summary

Fixes two open issues:

• Bug: Selector field pre-filled with misspelled placeholder text #254 — Cleared the misspelled "name of the selctor" default value from the CSS Selector field in CreateMonitorDialog. Users now see the proper placeholder instead of a pre-filled typo.
• Bug: No user notification when monitors are downgraded from hourly to daily #253 — Added sendTierDowngradeEmail() to notify users when their monitors are switched from hourly to daily frequency after a subscription cancellation or tier downgrade.

Closes #254
Closes #253

Changes

UI (client)

• Cleared bogus selector default value in CreateMonitorDialog.tsx

Email notification (server/services/email.ts)

• Added sendTierDowngradeEmail() with proper HTML escaping, plaintext sanitization, and safe href handling
• Includes ResendUsageTracker.recordUsage() for accurate Resend cap accounting
• Early return guard for empty monitorNames array
• Fallback "(unnamed monitor)" for empty monitor names
• Safe error extraction with String(error?.message ?? error)

Storage (server/storage.ts)

• Changed downgradeHourlyMonitors() return type from number to { count: number; monitorNames: string[] } to provide monitor names for the email

Webhook handlers (server/webhookHandlers.ts)

• Wired sendTierDowngradeEmail into all 3 downgrade paths (inactive subscription, tier change, subscription deleted)
• Uses .catch() fire-and-forget pattern so email failures never block webhook processing

Tests

• 11 new tests for sendTierDowngradeEmail (cap check, no API key, no email, single/plural monitors, notificationEmail preference, error handling, empty array guard)
• 2 new tests for webhook handler downgrade email send/no-send behavior
• Updated existing storage and webhook tests for new return type

How to test

1. npm run check && npm run test — all 1738 tests pass
2. npm run build — production build succeeds
3. Open CreateMonitorDialog and verify selector field shows placeholder .price-tag or #main-content instead of pre-filled text
4. Cancel a Pro subscription (or simulate via Stripe test webhook) and verify a downgrade notification email is sent listing affected monitors

https://claude.ai/code/session_01EaiPVsbd2waiYqem5rzKSY

[coderabbitai]

Warning

Rate limit exceeded

@bd73-com has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 8 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 18928464-d577-42eb-8daa-6f72ba5a459d

📥 Commits

Reviewing files that changed from the base of the PR and between e639b71 and c2c36ae.

📒 Files selected for processing (7)

• client/src/components/CreateMonitorDialog.tsx
• server/services/email.test.ts
• server/services/email.ts
• server/storage.test.ts
• server/storage.ts
• server/webhookHandlers.test.ts
• server/webhookHandlers.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/fix-github-issues-cz4fc

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}