F-003 fix: Sanitize SQL dump for safe dev use

work/artifacts/F-003/implementer.md

@@ -0,0 +1,32 @@
+# Implementer Artefact — Feature: F-003
+
+## Summary
+Replaced the tracked raw SQL snapshot with a small sanitized development baseline.
+Kept the same tracked SQL path for compatibility.
+Added docs for safe local SQL handling and private raw dump storage outside git.
+
+## Changes
+- replaced `project/sql/db-25052026.sql` content with sanitized schema and synthetic seed data
+- added `project/sql/README.md`
+- updated `.gitignore` with ignored private SQL path
+- updated `project/README.md`
+- updated design docs for development baseline
+
+## Evidence
+- tracked SQL file size changed from about `229M` to `6.8K`
+- data risk scan on tracked SQL file found no customer/order/production URL patterns
+- sanitized SQL baseline contains `11` table definitions
+- sanitized SQL baseline contains `10` seed insert blocks
+- `./scripts/verify.sh` -> OK
+
+## Checks run
+- `ls -lh project/sql/db-25052026.sql`
+- `head -n 40 project/sql/db-25052026.sql`
+- `rg -n "(@|CLIENTE|order_id=|mercadodevida\.es|stripe|hotmail|gmail|phone=|oo6478022A|admin_natural)" project/sql/db-25052026.sql`
+- `python3` table and insert count check on `project/sql/db-25052026.sql`
+- `./scripts/verify.sh`
+
+## Notes
+- Current tracked tree is safe for local module work.
+- Earlier raw dump still exists in git history from past commits and would need history rewrite if full purge is required.
+- Private raw snapshots should stay outside git or under ignored local paths only.