docs: fix stale Docker paths and park region counts

Update /app/data → /app/backend/data across all docs to match the
volume mount fix from 3c91d9a. Add missing TZ env var to the web
container snippet in OPERATIONS.md. Correct Midwest (6→7) and
West & International (6→5) park counts in ARCHITECTURE.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docs/OPERATIONS.md

@@ -75,6 +75,7 @@ services:
     environment:
       - NODE_ENV=production
       - BACKEND_URL=http://backend:3001    # Docker internal networking
+      - TZ=America/New_York
     restart: unless-stopped
 
   backend:
@@ -82,7 +83,7 @@ services:
     ports:
       - "3001:3001"
     volumes:
-      - park_data:/app/data                # SQLite database persistence
+      - park_data:/app/backend/data         # SQLite database persistence
     environment:
       - NODE_ENV=production
       - TZ=America/New_York                # Timezone for cron schedules
@@ -211,22 +212,22 @@ docker compose pull && docker compose up -d
 
 ### What to Back Up
 
-The SQLite database at `/app/data/parks.db` inside the `park_data` Docker volume. WAL journal files (`parks.db-wal` and `parks.db-shm`) must be included for a consistent backup.
+The SQLite database at `/app/backend/data/parks.db` inside the `park_data` Docker volume. WAL journal files (`parks.db-wal` and `parks.db-shm`) must be included for a consistent backup.
 
 ### Backup Methods
 
 **Method 1: Copy from the container**
 ```bash
-docker compose cp backend:/app/data/parks.db ./backup/parks.db
-docker compose cp backend:/app/data/parks.db-wal ./backup/parks.db-wal 2>/dev/null
-docker compose cp backend:/app/data/parks.db-shm ./backup/parks.db-shm 2>/dev/null
+docker compose cp backend:/app/backend/data/parks.db ./backup/parks.db
+docker compose cp backend:/app/backend/data/parks.db-wal ./backup/parks.db-wal 2>/dev/null
+docker compose cp backend:/app/backend/data/parks.db-shm ./backup/parks.db-shm 2>/dev/null
 ```
 
 **Method 2: Mount the volume to the host**
 Add a bind mount in `docker-compose.yml`:
 ```yaml
 volumes:
-  - ./data:/app/data
+  - ./data:/app/backend/data
 ```
 
 ### Restore
@@ -442,7 +443,7 @@ If the database becomes corrupted (unlikely with SQLite WAL mode, but possible a
 1. Stop the backend: `docker compose stop backend`
 2. Delete the database files from the volume:
    ```bash
-   docker compose run --rm backend rm -f /app/data/parks.db /app/data/parks.db-wal /app/data/parks.db-shm
+   docker compose run --rm backend rm -f /app/backend/data/parks.db /app/backend/data/parks.db-wal /app/backend/data/parks.db-shm
    ```
 3. Restart: `docker compose start backend` (auto-creates empty database)
 4. Re-scrape: `curl -X POST http://localhost:3001/api/scrape/trigger?scope=full`