What we’ve shipped

The analytics endpoint used to crash with a 500 whenever a referenced table wasn't there yet, taking down the whole dashboard. Now the affected card reads zero-state and self-hides; every other metric still renders. Same treatment for the nudge "send" button — if the log table is missing, the email still goes out and you get a success response, with a loud warning logged so the gap gets noticed and fixed.

GET /api/admin/analytics was throwing NeonDbError because a migration that was supposed to create the retention_email_sends table silently never ran. The admin Overview nudge effectiveness card and the Analytics tab's cohort sparkline depended on it, so both were broken until this patch. Fixed end-to-end.

Previously it linked to /settings?focus=telegram, which isn't a real route — users landed on the generic settings page and had to hunt for Telegram manually. Now it opens /settings/telegram directly, and if you're not signed in, you're bounced through sign-in and returned to that exact page after login.

Before, it used browser history, which was unreliable — depending on how you arrived at Settings, it could drop you on the sign-in page (which immediately redirects back into Settings), leaving you stuck in a loop. Now "Back" just means "leave Settings," which is what the button label says.

Before, every user who signed up and hit /stream fast enough left their invite code looking unclaimed in the admin dashboard, even though signup worked fine. A race between our user-row fallback and the Clerk webhook meant invite consumption was silently skipped. Fixed, and backfilled the orphaned history so the admin view is accurate end to end.

The Invite Codes tab shows a → Name link next to each claimed row, so you can tell at a glance which code belongs to which user without drilling in.

If you typed something and hit N to create a new note before the debounced save fired, the debounced PATCH is now flushed with keepalive: true on unmount. Nothing drops.

Per-mount cache plus AbortController on rapid nav.

In the admin Users tab there's a new mail-icon button per user. Clicking it sends a warm, manually-triggered email that pitches the Telegram companion + daily devotional with one CTA and leaves a reply loop open so you learn what's in their way. Guarded so it won't send to anyone who already has Telegram linked.

If you've already nudged someone in the last 14 days, the admin tells you up front ("Last nudge sent 3 days ago") and requires an explicit override to send again. No more accidental double-taps.

The Overview tab now shows "X% linked Telegram after nudge" with the raw numbers as soon as you've sent at least one. Tells you whether the email actually moves the needle.

The Analytics tab has a new 8-week sparkline showing the share of each signup cohort that's linked Telegram. Latest cohort highlighted, with an up/down arrow vs the prior cohort so you can read the trend in a glance.

Inter and Lora fonts are now self-hosted via next/font/google instead of fetched from Google on every cold load. LCP drops by roughly 100-300ms depending on network.

The "Join the waitlist" button is now the primary filled CTA on hero and footer, and "I have an invite code" drops to outlined secondary, matching the roughly 95/5 split of who actually has a code. A one-line clarifier ("We'll email you when a spot opens. One email.") kills the implicit newsletter objection.

Each step — Capture, Study, and Share — shows a visual so you can see what Selah looks like before you sign up.

On Telegram, the companion pushes it straight into the chat. On web, it surfaces a preview with a link to the full reading. No more "head to the app" dead-ends.

New database changes run as part of the Vercel build — no more copy-pasting SQL into Neon by hand, no more forgetting.

Visit selah.so/changelog anytime to see what's shipped, in plain English. Bookmark it to follow along.

with a dedicated page for devotional settings. The menu now slides between groups instead of jumping between pages, and your devotional timing, timezone, and theme all live together in one place.

Ask "what's this week's theme?" and it answers directly instead of saying it can't see that.

Say "now" when changing themes and the fresh devotional lands in your Telegram chat right away — no waiting until tomorrow's scheduled time.

Before, if a cron-written entry existed under the old theme, the companion would keep serving it even after a pivot. Now the old entry is cleared on confirm and a fresh one is written under the new theme on next fetch.

It used to rationalize stale chat history by inventing a parallel arc. Now it treats the DB as the single source of truth and the current week has exactly one theme, period.

If Claude returns an empty response (rare, but it happens), the reformat tries once more with an explicit nudge before surfacing a "try again" message. No more blank modals.

If today's entry was already written under your old theme, changing themes replaces it with a fresh entry for the new one. Before, you could end up reading a devotional about the old topic even after a successful switch.

Timestamps at selah.so/changelog now read "today", "yesterday", or "3 days ago" instead of "17 hours ago" — more honest since entries are dated by day, not by hour.

Saying "done", "wrap up", or "finish the prep" now saves your note every time, and the Enrich/Format card shows up when you expect it.

It won't claim to finish a task it didn't actually complete.

A setting was blocking our internal tools from seeing what's happening in the app, which meant we were slower to spot bugs. Fixed.

Ask it to "add a point about Romans 8 to my sermon prep note" or "tighten up the intro" and it actually does it. Works from the web companion and from Telegram.

Send /notes in the bot and you get a browsable list. Tap one to open a thread where every message you send gets appended to that note. Great for capturing thoughts on the go without opening the app.

When the companion or Telegram modifies a note, an Undo button appears at the top of the note page with a diff summary ("Added 2 paragraphs to Introduction · from Companion"). One tap reverts the change. Nothing is permanent unless you want it to be.

If you have a note open in the web editor and Telegram edits it underneath you, we show a banner with a Refresh button so you don't accidentally overwrite each other's work.

Every AI edit gets logged with before/after content, source surface (web or Telegram), and a plain-English diff summary. Foundation for the fuller history panel we're planning.

If a Clerk user's email matched a pre-existing user row with a different id (legacy Neon-auth leftover), the fallback insert silently no-op'd and every downstream foreign-key insert (user_onboarding, notes) blew up. Now we detect the collision explicitly and throw a clear error pointing at the migration script.

ts` — voice path no longer sends the 👀 reaction twice (one Telegram API call saved per voice message)

ts` — diff summary generation, section-level updates, append/replace helpers shared by companion + Telegram

ts — new note_edits` table: userId, noteId, sourceSurface, contentBefore, contentAfter, diffSummary, revertedAt

ts — append_to_note, update_note_section, revert_last_edit` tools for the companion pipeline

tsx` — undo button, stale-version banner, polling for concurrent edits

ts` — GET latest un-reverted edit, POST to revert

ts — /notes` command, inline-keyboard note picker, append-mode callback routing, undo callback

ts` — temporary auth diagnostic endpoint (to be removed after dev stabilizes)

ts — Whisper API wrapper, raw-fetch (no openai SDK), discriminated TranscribeResult`, exhaustive failure-reason mapping

ts — downloadTelegramFile(fileId) for two-step getFile` → file fetch

ts — voice/audio dispatch in handleMessage, transcribeIncomingVoice helper, 🎙️` transcript confirmation message

ts — ensureUserInDb now detects email collisions against stale user rows and surfaces a descriptive error instead of silently no-opping via .onConflictDoNothing()`

ts — /api/debug/* added to public route patterns (Next 16 private-folder _debug` convention forced the rename)

Tap-and-hold the mic in Telegram, talk, release. The companion downloads the voice note, transcribes it via OpenAI Whisper, echoes the transcript back so you can verify (🎙️ "your words"), then routes it through the same companion pipeline as a typed message. Captures, prayers, slash commands — everything works.

Forward an audio file from another chat and it gets transcribed the same way.

Voice notes that are empty, too long (>10 min), or fail transcription get a clear message ("I had trouble transcribing that — try again or send text") instead of silent dropping.

Reuses the existing OPENAI_API_KEY (already used for embeddings).