Vercel + Supabase Deploy & Verify

> This skill is tuned for a specific personal project (a multi-surface site: marketing + CRM + customer portal, originally עוגנים ישיר / oganimy.co.il), but the patterns generalize. Fork it and swap project name, domain, Supabase project ref, and admin emails. The canonical-bug-fixes sections are the real gold — keep them when adopting.

What This Is (Reference Layout)

A project at /projects// with:

• Marketing site — /index.html, styles.css, app.js, widget/ (embedded AI chat).
• CRM — /crm/index.html, /crm/crm.js (large vanilla-JS app), staff-only.
• Portal — /portal/index.html, /portal/portal.js, customer-facing.
• Serverless APIs — /api/*.js (Vercel functions; 12-function Hobby plan cap).
• Onboarding wizard — /onboarding/.
• Universal form renderer — /render.html.

Hosted on Vercel, aliased to a custom domain (e.g. https://example.com). DB: a Supabase project ().

Standard Deploy Workflow

cd <workspace>/projects/<my-project>

# 1. Edit the file(s).
# 2. Lint-check anything that isn't HTML/CSS:
node -c crm/crm.js portal/portal.js api/<changed>.js

# 3. Bump the version query on every <script>/<link> tag you touched in
#    the relevant index.html (see "Cache busting" below).

# 4. Deploy.
VERCEL_TOKEN=$(cat ~/.openclaw/credentials/vercel/token) \
  npx vercel deploy --prod --yes

# 5. Verify the new code is live.
curl -sL https://example.com/crm/crm.js | grep -c "<marker-from-your-change>"

Deploy usually finishes in 15–25 s. Look for Aliased: https://example.com in the output.

Cache Busting (Critical)

Vercel's CDN caches crm.js, portal.js, and crm.css aggressively. Use a ?v=YYYYMMDD- query string on every