the part your builder can't show you.Instrument your whole codebase with one Codex prompt.

Add server-side event logging to this app using logs.so.

1. First, study what this app actually does. Read the codebase and map its real
   features and the moments that matter in THIS product — not a generic checklist.
   Every app is different: a photo tool cares about renders and exports, a
   marketplace about listings and orders, an AI app about generations and credits.
   Write a short list of the events worth knowing about before you log anything.
   Signups and payments are the baseline, not the whole story.

2. Send events by POSTing JSON to https://api.logs.so/v2/log with header
   Authorization: LOGS_SO_API_KEY (read from an environment variable — never
   hardcode it, never expose it to the browser).
   Body: { "project": "<WORKSPACE_ID>", "channel": "<channel>", "event": "<short title>",
           "description": "<details>", "user_id": "<user email/id>",
           "tags": { <relevant ids/amounts> } }

3. Create one small server-side helper (e.g. lib/logsso.ts) wrapping this call.
   It must never throw, never block the response (fire-and-forget), and no-op
   when LOGS_SO_API_KEY is unset.

4. Instrument the events you found in step 1, SERVER-SIDE ONLY:
   ✅ Product moments → channel "product": the app's own key features being used,
      named in the product's own language. Plus signups → "signups" and
      payments/subscriptions → "revenue".
   ❌ Failures — these matter most → channel "failures": every catch block in API
      routes and server actions, webhook handlers that fail or fail signature
      verification, declined payments, cron jobs that throw or don't complete,
      failed external API calls.

5. Prefix every event name with an emoji: 💰 revenue, ✅ success, ❌ failure, ⚠️ warning.

6. Always set "user_id" to the user's email or id — that's how the feed ties each
   event to a person. Put amounts, plan names, and object ids in tags. Just don't
   log secrets, passwords, tokens, or card numbers.

When done, list every file you changed and every event now tracked.

Note: Run this inside the repo with Codex: sweep existing catch blocks, webhook handlers, and cron jobs and instrument them all.