Update replit.md file to automatically record every prompt - #2

Implemented full Google Places API integration for restaurant discovery:

Backend:
- Created server/lib/places.js with zip code validation, geocoding, Google
  Places Nearby Search, and result formatting utilities
- Created server/lib/duplicates.js with duplicate detection helper that
  matches by google_place_id or normalized name+address
- Added GET /api/restaurants/search endpoint accepting zip and keyword params,
  returns results with already_added flags for duplicate prevention
- Added guard for missing google_place_api_key env var (returns 503)
- Updated POST /api/restaurants to accept and store google_place_id

Database:
- Added google_place_id VARCHAR(255) column to restaurants table in schema.sql
- Added migration in migrate.js to add column to existing tables

Frontend:
- Created client/src/components/RestaurantSearch.jsx with two-step flow:
  1) Zip code entry prompt
  2) Scrollable results list with keyword filtering, duplicate greying,
     and click-to-add functionality
- Updated RestaurantList.jsx with "Find Restaurant" button alongside
  existing "Add Manually" button
- Added CSS styles for search UI components

Tests:
- server/__tests__/places.test.js: 22 tests (zip validation, URL builders,
  price mapping, formatting, geocoding paths, nearby search, searchByZipCode)
- server/__tests__/duplicates.test.js: 7 tests (normalization, detection,
  flagging)
- server/__tests__/search-api.test.js: 7 tests (endpoint validation,
  duplicate flags, keyword, errors, google_place_id storage)
- client/src/__tests__/RestaurantSearch.test.jsx: 17 tests (zip entry UI,
  results rendering, duplicate greying, selection payload, error handling)
- All 97 server + 62 client tests pass

Updated replit.md with new files, routes, env vars, and design decisions.

Replit-Task-Id: 598fc122-6f7c-40ae-8538-87e2dde6d704

Task #2: The deployment [deployment] section in .replit had chained `cd`
commands (`cd client && ... && cd ../server`) in a single bash string.
In the deployment environment `cd ../server` failed after `cd client`
because the relative path doesn't resolve correctly from the changed
working directory.

Changes made (via deployConfig):
- build: changed from
    "cd client && npm install && npm run build && cd ../server && npm install"
  to
    "(cd client && npm install && npm run build) && (cd server && npm install)"
  Each subshell is independent; `cd server` runs from the project root.

- run: changed from
    "cd client && npm run build && cd ../server && node server.js"
  to
    "cd server && node server.js"
  The run command no longer redundantly rebuilds the client — that is
  the build step's job. It simply starts the server from the server dir.

No source code, tests, or start.sh were modified.