Overview / Open gaps
What I would fix first
Written into the repositories with their consequences attached before any interviewer asked, because a gap you have named is a plan and a gap you have hidden is a liability.
| Gap | Consequence | Fix |
|---|---|---|
| No test runner | Zero automated coverage in either project. The lead-capture path — the only revenue path — has no regression tests. | Test the revenue path first: Zod schema, spam gates, and the webhook client’s retry, backoff and timeout behaviour. |
| No error monitoring | On total webhook failure a lead survives only as a log line, while the visitor still sees a thank-you page. Silent loss. | Fallback email queue on total failure, plus alerting. Open TODO in the webhook client since day one. |
| No perf gate on the second site | Riflessi ships without the Lighthouse budget that protects DriftPilot, so regressions reach the live site undetected. | Port the existing config into its CI. Deliberately deferred for launch, recorded with its consequence. |
Both sites are my own studio’s work. I am looking for a senior role on a team where the standards are shared rather than self-imposed.