devlog 003 - making Onara launch-ready

Date: 2026-06-19

Since devlog 002, I mostly worked on turning Onara from “it works” into something closer to launch-ready.

what I worked on

billing + accounts

I added more real account controls:

• cancel subscription from billing
• plan limits
• better account page
• better checkout layout
• Google-login warning if someone tries password login on a Google account

Google account -> use Continue with Google
Password account -> normal email/password login

generated sites

I worked on making the sites Onara creates more useful after launch:

• contact form lead emails
• better email HTML
• Pro code download
• cancellation placeholder pages
• Google Reviews refresh job
• support email surfaces

contact form -> Onara lead email -> site owner inbox

pipeline fixes

I fixed more backend/build issues:

• longer pipeline timeout
• better health monitor support
• fixed /health HEAD checks
• fixed broken generated HTML cases
• improved Google Maps region filtering back toward DC / VA

GET /health -> 200 OK
HEAD /health -> 200 OK

launch cleanup

I added launch stuff that real products need:

• privacy policy
• terms of service
• support page
• favicon/logo polish
• SEO metadata
• .env.example updates
• docs for production fixes

AI + training data

I also added the start of a cleaner AI improvement system:

• user consent copy
• opt-out/delete handling
• training example storage
• QA-approved examples only
• no saving random bad generated sites into RAG

good QA result -> redact -> save as training example
bad result -> do not save

biggest change

Onara is not just generating sites now. It is starting to act like a real app with billing, support, cancellation, reviews, contact leads, account limits, and safer AI improvement rules.

still left

• finish production deploy polish
• make generated site quality more consistent
• keep fixing slow render/build issues
• launch testing
• outreach assets