Skip to content

feat: Send test notification button on /me#16

Merged
illinigirl merged 1 commit into
mainfrom
feat/me-test-notification
Jul 3, 2026
Merged

feat: Send test notification button on /me#16
illinigirl merged 1 commit into
mainfrom
feat/me-test-notification

Conversation

@illinigirl

Copy link
Copy Markdown
Owner

A self-serve 'is my Pushover working?' button on the My alerts page — pushes a one-off test to the user's saved key. No infra (web already has the SSM token + a send client); session-sub identity, debounced, soft-fails.

🤖 Generated with Claude Code

Self-serve "is my Pushover actually wired up?" check, right where the key
is set. A type="button" (not a form submit) fires a new
sendTestNotification server action that pushes a one-off test to the
user's SAVED key via the existing sendPushoverMessage client.

- No infra: the web already loads the Pushover app token from SSM (used
  today to validate keys) — this just also sends.
- Identity is the session sub (same no-client-user-id contract as
  saveSettings); tests the saved key, so a freshly-typed-but-unsaved key
  prompts "Save first" (button disabled until a key exists).
- Warm-Lambda in-memory debounce swallows rapid double-taps without a DDB
  write; the button also disables mid-flight.
- Send failure is a soft error ("double-check your key"), not a throw.

Tests: signed-out gate, needs-saved-key, sends-to-saved-key, soft-fail on
Pushover error, double-tap debounce.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@illinigirl illinigirl merged commit c6b6bf4 into main Jul 3, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant