Kann Proofling weg?

Build a self-hosted testimonial automation app inspired by Proofling.
Use Node.js 22, TypeScript, Fastify, better-sqlite3, server-rendered HTML, and vanilla CSS.
Keep it single-tenant and deployable as one small service on a VPS.

- Add an .env.example for ADMIN_PASSWORD, APP_URL, STRIPE_WEBHOOK_SECRET, and RESEND_API_KEY.
- Create POST /webhooks/stripe and verify Stripe signatures before processing events.
- Idempotently store completed checkout customers and ignore duplicate webhook deliveries.
- Let the admin configure an ask delay, one optional follow-up delay, sender name, and message copy.
- Run a database-backed worker every minute; queued jobs must survive restarts and retry with backoff.
- Send email through Resend, with MAIL_MODE=log for local development without an API key.
- Give each customer an expiring signed /r/:token response link; never expose sequential database IDs.
- Collect name, role, company, optional 1-5 rating, testimonial text, avatar, and explicit publication consent.
- Resize avatars to 128px WebP, discard originals, and reject oversized or non-image uploads.
- Add a Basic Auth /admin page with pending, approved, private, and failed-delivery views.
- Allow approve, unpublish, delete, and resend; nothing public appears before approval and consent.
- Render a mobile-friendly /wall page with approved cards, dark mode, and honest buyer-context badges.
- Serve /embed.js so one script plus a div creates a sandboxed, auto-resizing wall on another site.
- Expose approved data at /proof.json and /proof.md without private contact details.
- Exclude multi-user accounts, billing, non-Stripe integrations, video, AI rewriting, and referrals.
- Add tests for signature verification, webhook idempotency, scheduling, consent gates, and public filtering.
- Include SQLite migrations, seed data, a Dockerfile, and a README covering setup, backups, and permissions.