Go-to-market

Testing & Demo

How the project is demonstrated, monitored and kept honest — the demo pipeline, health surfaces, QA hardening and deploy infrastructure.

Demo pipeline

/demo/play

Auto-play scripted product tour using a crafted demo-review bank (no live scrape). Used for LemonSqueezy approval + marketing video.

/api/healthPublic — commit hash, DB latency, status (used to confirm deploys)

/admin/healthAPI uptime, queue, scraper, DB

/api/admin/cron-healthPer-cron last-run + status

/api/admin/scraper-healthVPS scraper reachability

/api/admin/secrets-checkConfirms required env secrets are loaded

✓Email queue: exponential backoff (5m / 30m) + dead-letter view (?status=failed) + manual retry

✓Webhook idempotency: recordWebhookOnce() PK-collision guard on all providers

✓Credit consumption: atomic SQL guard prevents concurrent over-spend

✓GDPR geo-block: EU/EEA/UK/CH skipped across execute + launch + sequence senders

✓Cache-leak headers: no-store + Vary on private API routes

✓Cron self-heal: audit-retry re-runs stuck jobs every 3 min

✓Deploy gate: tsc must pass before push (no failure-email spam)

Auto-deploy

Push to main → GitHub Actions → npm run cf:deploy (~3-5 min)

Concurrency lock

deploy-main group, cancel-in-progress — latest commit wins

Retry

Deploy step retries up to 3× on transient failure

Smoke test

Non-blocking post-deploy check (continue-on-error)