Blockers, and the steps to clear each.

The self-audit put Trust at 5 out of 10 and Social at 5 out of 10, the two lowest scores on the landing, and both carry heavy weight. A first-time visitor finds no name, no contact, and no privacy policy, so the page earns interest and then hands them a reason to hesitate at the last step.

1. Decide how you want to be named on the page: your real name, a small team in Singapore, or a company name.
2. Pick a contact email you will actually read, for example hello@yourdomain.
3. Tell me whether you already have a privacy policy. If not, I will draft a short honest one: coldeye keeps the URL you submit and the report, and nothing else.
4. Send me those three. I add the "Who is behind coldeye" line, the footer email, and the Privacy link. The wording is already drafted in docs/COPY-PROPOSAL.md.

Social proof is the other 5 out of 10. There is not one testimonial, client logo, or honest usage number, so a stranger has only your claims to weigh.

1. Ask two or three real users for one sentence each on a specific thing the report caught that they had missed.
2. Get a name and a company for each, plus permission to show it.
3. Send them over. I place them in the testimonial row that is already stubbed into the landing.
4. Optional, once the number is honest: I add "Read N pages so far" with the real count.

The queue table is named firsteyes_waitlist. Anyone who opens the network tab sees both "firsteyes" and "waitlist", which reads as a clone and as a waitlist you are not actually running.

1. This change is mostly mine, but it touches the live worker and the form at the same moment, so it needs a short window with no audit mid-run.
2. Pick a quiet ten minutes and tell me.
3. I create the renamed table in Supabase, copy the rows across, point the worker and the form at it, deploy, then drop the old table. Your Supabase access is already set up on my side.

The hosted queue is drained by a launchd worker on your machine. If the Mac sleeps or the worker stops, a submitted audit sits in the queue and never finishes, and the visitor waits on a report that never arrives.

1. Check the worker is loaded and look for com.leo.firsteyes-worker:
   launchctl list | grep firsteyes
2. If it is missing, reload it:
   launchctl load ~/Library/LaunchAgents/com.leo.firsteyes-worker.plist
3. When you expect traffic, keep the Mac awake with a terminal running:
   caffeinate -s
4. If you want reports to run with your Mac off, that is a move to a hosted worker, which we can scope on its own.

The /copy tool calls OpenAI, which spends your credit. It is already gated to same-site use, caches each page, and caps output, and a best-effort per-instance limit is in place. A determined caller could still spoof the referer and hit many different pages, so a shared limit that holds across every serverless instance is the proper fix.

1. Nothing needed from you unless you want to pick the store.
2. I add a Supabase-backed (or Vercel KV) sliding-window limit keyed by IP, so the cap holds across all instances, not just one warm one.
3. Until then, the referer gate, the per-page cache, and the per-instance limit keep casual abuse in check.

Minor and cosmetic. The full-page screenshot has no set height, so a long report shifts down a little while the image loads in.

1. Nothing needed from you.
2. I read the real image size at build time and set the width and height on the screenshot, which removes the shift. I will fold it into the next change.