UAEThrive Project Hub

We are ready to start a controlled live-page rollout for UAEThrive.

CONSTRAINTS — do not violate these under any circumstances:
- Do not start mass migration.
- Do not remove or redirect any existing WordPress/indexed URLs.
- Do not write directly to production Supabase or change RLS.
- Do not enable GHL workflows, cron jobs, GitHub Actions, or any external
  sending without explicit approval.
- Do not deploy to production automatically.
- Do not merge to main. Create a branch, commit, push, open a PR only.

CONTEXT FROM LAST AUDIT (branch claude/zen-gauss-UVc1K, 5 June 2026):
- Build is currently FAILING: VenueDirectoryRoute.tsx has TS errors —
  SurfaceCard does not accept children prop (PR #39, unmerged).
- VITE_GHL_WEBHOOK_URL env var is unset — Add Listing and Claim Listing
  forms silently fail to reach GHL.
- Enquiry Worker (uaethrive-enquiry.alan-3e1.workers.dev) has zero
  references in src/ — listing profile CTAs still point to old WordPress URLs.
- /admin/* routes have no authentication guard.
- PR #54 (public listing safety gates) is open but not merged.
- PRs #51, #52, #53, #55 are confirmed merged into main.
- Confirmed merge head: 14784c2

STEP 1 — REPO STATE CHECK (report only, no changes):
1. Current branch and git status.
2. Latest commit SHA and message.
3. Confirm PRs #51–55 are reflected in local main.
4. Confirm whether PR #54 is merged or still open.
5. Run the build. Report pass or fail and exact errors if failing.

STEP 2 — PR 1: PRE-LAUNCH FIXES
Fix these in a single PR. Name it: "Pre-launch fixes: build, admin auth, listing safety"

a) Fix VenueDirectoryRoute.tsx TS error — SurfaceCard children prop
   (type the prop or wrap children). Confirm build passes after fix.
b) Add authentication guard to /admin/* routes using existing Supabase auth.
c) Fix listingQueries.ts fallback query (lines 44–49) — hard-fail on
   schema error, never return unfiltered records.
d) Suppress blank-title records in toItem() — filter null/empty titles
   rather than falling back to "Untitled Listing".

Build must pass before PR 1 is opened.

STEP 3 — PR 2: CONTROLLED LIVE-PAGE ROLLOUT FOUNDATION
Once PR 1 is reviewed and approved, create a second PR.
Name it: "Controlled live-page rollout foundation"

Homepage:
- Audit HomePageRoute.tsx for placeholder copy, broken links, missing CTAs.
- Confirm SEO title, meta description, canonical, H1, Open Graph tags.
- Add Listing CTA and Browse Businesses CTA above the fold.
- Add JSON-LD Organization schema if not already present.

Add Listing + Claim Listing:
- Verify VITE_GHL_WEBHOOK_URL is referenced correctly in ghlWebhook.ts.
- Add visible error state if GHL submission fails — do not show success
  if the webhook call errors.
- Confirm thank-you pages are noindex.

Listing profile (/listing/:slug):
- Remove these two CTAs linking to old WordPress URLs:
    /add-your-free-business-listing-uaethrive/
    /free-business-listing-uae-expand-your-local-reach-with-uae-thrive/
- Replace with:
    "Enquire" button — POST to https://uaethrive-enquiry.alan-3e1.workers.dev
    Pass: listing_name and listing_slug in request body.
    Show inline success message on submit. No page reload.
    "Claim this listing" button — internal link to /claim-listing
- Free listings must NOT expose: direct phone, WhatsApp, website URL,
  multiple images, or any premium-only fields.
- Add JSON-LD LocalBusiness schema using listing data.
- Confirm published/approved status filter is always applied.

Footer:
- Replace placeholder links with real routes where they exist, or
  # anchor + TODO comment where they don't.
- Add minimal Privacy Policy + Terms copy ("This page is being updated")
  — cannot be blank shells in the footer.
- Confirm /add-listing and /claim-listing footer links are correct.

Build check:
- Run npm run build after all changes.
- Build must pass before PR 2 is opened.
- If it fails, fix before opening.

PR output required for both PRs:
- Branch name.
- List of changed files.
- Build result (pass/fail, error output if failing).
- Risks or items needing review before merge.
- PR URL.

The goal is a stable foundation for controlled live-page rollout.
Not mass migration. WordPress remains live throughout.