Session Handoff — LeadScout: rebrand GhostTown → build full lead-gen tool in Base44

Where it started

Sondra dropped a Lovable app zip (GhostTown Finder, a Brian Hanson "PushTen" whitelabel template) and wanted a project started under a "PushTen Templates" umbrella, pushed to Git, then rebuilt in Base44 with Brian's branding stripped. Goal evolved into: get the whole tool actually working against her real GoHighLevel so she can test it. She builds in Base44's UI but wanted Claude to do the building via CLI, not hand her prompts.

Decisions locked + what shipped

• Umbrella + extraction — created PROJECTS/PushTen Templates/; extracted the Lovable code to c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\PushTen Templates\GhostTown Finder\ (folder still named GhostTown Finder; rename to LeadScout deferred — was file-locked).
• Rebrand — GhostTown → LeadScout, neon green → neon electric blue (oklch(0.72 0.19 245)) across the Lovable source. No Brian/Hanson/PushTen strings existed in code.
• Git — Lovable code pushed to private repo github.com/digitalbeachgirl/leadscout (.env gitignored, no secrets committed).
• Scope LOCKED (research-backed) — v1 = nationwide Google Maps lead engine. Fresh Filings deferred to v2 (free daily feed exists only in FL + WA; other states need paid vendors — confirmed via Perplexity).
• Base44 app built — Sondra created "LeadScout" in the builder (app id 6a46ad7a89bffa371e7637da). Ejected to PROJECTS\PushTen Templates\LeadScout-base44\. 6 entities: Campaign, ScrapeJob, Lead, Invite, UsageEvent, WorkspaceSettings.
• Pages built + written to builder source via base44 sandbox write (required base44 login re-auth for sandbox:write scope): src/pages/Campaigns.jsx (create form + Launch scan), Leads.jsx (filter, checkbox-select, Verify, Push, CSV), SettingsPage.jsx (caps + connections + compliance).
• 3 backend functions built + deployed (base44/functions/<name>/entry.ts): scan-campaign (Outscraper), verify-leads (Firecrawl), push-to-ghl (GoHighLevel v2 services.leadconnectorhq.com).
• Secrets set in Base44: OUTSCRAPER_API_KEY, FIRECRAWL_API_KEY, GHL_API_KEY (a PIT), GHL_LOCATION_ID. OUTSCRAPER_API_KEY also saved to master .env.
• Bugs found + fixed during live testing: (1) Outscraper field is website not site — was flagging every business as no-website; (2) verify-leads directory blocklist expanded (HomeAdvisor etc.) + match tightened to domain-only; (3) push-to-ghl name → firstName+lastName split + companyName.
• Verified end-to-end against real accounts: scan created 133 real Palm Beach electrician leads (17 no-website, 5 social, 111 have sites); verify confirms/corrects; push creates GHL contacts (tagged leadscout), test contacts deleted, lead state reset clean. Live app: https://alluring-scout-your-leads.base44.app

Key files for next session

• Plan: c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\PushTen Templates\GhostTown Finder\REBUILD-PLAN-base44.md — the phased plan + locked scope
• c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\PushTen Templates\LeadScout-base44\ — the live Base44 project (edit here → base44 sandbox write for builder + base44 deploy for live)
• ...\LeadScout-base44\base44\functions\scan-campaign\entry.ts, verify-leads\entry.ts, push-to-ghl\entry.ts — the 3 functions
• ...\LeadScout-base44\base44\.app.jsonc — MUST stay pointed at 6a46ad7a89bffa371e7637da (eject defaults it to a throwaway copy 6a46b10699d9700eef138ce8 — do not deploy to the copy)
• c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\PushTen Templates\GhostTown Finder\PROJECT-BRIEF.md, BUILD-PROMPTS-base44.md
• Master .env (OUTSCRAPER_API_KEY added). Memory files touched: none.

Running state

• Background processes: none (login shells blcor1987, b44tt0ji8 completed). Base44 CLI now authed with apps:read apps:write sandbox:write (token at C:\Users\srver\.base44\auth\auth.json).
• Dev servers / ports: none.
• Open worktrees / branches: none. Note: LeadScout-base44/.git has bogus origin file:///app from eject — ignore it; the real pushed repo is the separate GhostTown Finder → github digitalbeachgirl/leadscout.

Verification — how to confirm things still work

• cd "PROJECTS/PushTen Templates/LeadScout-base44" && npx base44 functions list → lists scan-campaign, verify-leads, push-to-ghl
• Live bundle check: curl -s https://alluring-scout-your-leads.base44.app/ | grep -o 'assets/index-[^"]*\.js' then grep that asset for "Push to GHL" / "Launch scan"
• SDK smoke test from LeadScout-base44/: echo 'console.log((await base44.entities.Lead.list("",1)).length)' | npx base44 exec → returns a lead count (133)
• Full UI path: live app → Campaigns → Launch scan; Leads → filter "No website" → select → Verify / Push to GHL; in GHL filter contacts by tag leadscout

Deferred + open questions

• Deferred: bigger scans — functions cap at an 80s time budget (~10 zips/run), so large campaigns truncate; upgrade path is Outscraper async + a public webhook function.
• Deferred: Fresh Filings v2 (FL/WA free via Sunbiz; paid vendor for other states).
• Open: Sondra's real UI test — she was about to test the full flow herself; awaiting her results.
• Open: GHL contactName returns None via API (name IS stored in firstName/lastName/companyName; displays in GHL UI) — confirmed not blocking, left as-is.
• Note: her "Palm Beach Electrical" campaign has a malformed zip 33478. (trailing period).
• Deferred: rename folder GhostTown Finder → LeadScout (was file-locked); recreate LeadScout-base44 git remote if it should be version-controlled.

Pick up here

Wait for Sondra's hands-on UI test result; if it works, offer the bigger-scan (async/webhook) upgrade — if she hits an error, debug via npx base44 functions list / base44 exec / redeploy from LeadScout-base44/.