security(pii): keep customer SQL dumps out of git and the Docker image

customers.sql (610KB phpMyAdmin dump: wp_rmp_users password hashes + real
customer names/emails/phones/addresses) sat untracked but matched NEITHER
.gitignore NOR .dockerignore, and Dockerfile does COPY . . — so it was one
'git add .' from history and already bakeable into the public image.

- .gitignore:  customers*.sql  (schema.sql stays tracked)
- .dockerignore: *.sql  (startup DDL is inline in app/main.py; no .sql needed at runtime)

Working-tree customers.sql shredded. site-update.sql was already gitignored;
now dockerignored too.

NOTE: rebuild+redeploy the image to purge copies already baked into layers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

.dockerignore

@@ -12,3 +12,6 @@ ingest_raw/
 rarw*.txt
 inertia.txt
 *.xlsx
+# SQL dumps — customer/order PII + WP password hashes. Never bake into the image;
+# the app's startup DDL is inline in app/main.py, so no .sql is needed at runtime.
+*.sql

.gitignore

@@ -12,4 +12,5 @@ inertia.txt
 # live-site MariaDB dumps for 3D-store/editor data work — full site export, carries customer/
 # order PII. Local-only; another lane consumes it for robotmonster.party/store racks + editor.
 site-update.sql
+customers*.sql
 *-dump.sql