Public Access

Files

T

pguerrerox dc7686f507 chore: improve postal data import observability

Add progress logging and a status script for postal imports and neighbor builds, and ignore local raw and generated postal datasets.

2026-04-12 23:22:36 +00:00

Changelog

All notable changes to this project are documented in this file.

2026-04-12

Improved local development networking by making API env loading work with .env.local, adding LAN-friendly API URL fallback behavior, and fixing development CORS handling.
Fixed local research inserts so nullable Google Places coordinates no longer break business upserts.
Improved postal data tooling with streaming imports, clearer CRS validation, progress logs, and a status command for checking imported areas and adjacency counts.

Added postal-area import and adjacency build scripts for US ZIP/ZCTA and Canada FSA datasets.
Added a dedicated Deep Research view with map pin placement, propagation preview overlays, batch history, and bundled map navigation.
Added backend deep-research preview, batch creation, and batch detail APIs, reusing the existing research engine to create one child search per postal area.

Removed stale local metadata, placeholder postal seeding code, and leftover Supabase-era repository artifacts.

Migrated the app from a Supabase runtime to a local Fastify API with PostgreSQL, PostGIS, and cookie-based session auth.
Reworked the research experience with the Leads4less branding, the renamed Research view, a top-form layout, and a filterable grid of research jobs.
Added local API wiring for research, dashboard, and map flows while keeping selected-job map behavior and broader lead retrieval support.

Added local backend scaffolding under server/ for auth, health checks, search routes, database access, and worker startup.
Added local database migrations and scripts under db/, including the first PostGIS-enabled schema and migration runner.
Added shared app types and frontend API/auth helpers for the local stack.

Removed the Supabase browser client, Edge Function runtime, and Supabase migration artifacts from the active app stack.

Initial Leads4Less app with React and Vite.
Supabase-backed authentication, lead storage, and search job persistence.
Research, dashboard, and map views for running searches, browsing leads, and visualizing results on Google Maps.