What web app construction looks like

Jul 16 • General

For those interested in what web app construction looks like, here's what happened this week under the hood. As always, if you come across any tech bugs, let me know and send a screenshot if you're able.

By the way, a huge shout out thank you to our developer genius,

@Michael Byrd

, who went WAY above and beyond this week.

Fixed the Sermon Builder walkthrough freezing after a fumbled confirmation — step completion is now driven by the confirmed field, so a stale step self-heals on the next confirmation

Fixed confirmations dead-ending on "ready to move on" — the AI now opens the next step's coaching in the same reply, using scripted wording and never inventing options

Fixed manuscript generation failing on a desynced walkthrough — blocked generation attempts now heal the step index at the end of the turn

Fixed duplicated chat bubbles caused by sends racing an in-flight response stream, and repaired already-corrupted saved conversations

Fixed repeated coaching messages by pinning the Vertex provider SDK to the last good version, plus a filter that suppresses any verbatim repeated text

Fixed silent content-tool failures behind "manuscript won't generate" reports — unavailable tools now explain themselves and guide the walkthrough forward, mistyped tool parameters are auto-repaired, and AI usage is recorded on aborted streams

Fixed production log issues: client error serialization, /projects hydration mismatch, and AI SDK patch updates

Required every numbered coaching part to be answered before a manuscript section can be drafted

Stripped echoed session-context blocks from model output and healed already-saved histories

Surfaced mid-stream generation failures (e.g. rate limits) with the real reason instead of silently claiming success

Guarded the admin prompt fragment editor against silent save loss — unsaved-changes confirmation when switching fragments, and stale-tab saves now detect conflicts instead of overwriting newer work