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

spec/sdd/decisions/003-replace-raw-sql-with-sanitized-dev-baseline.md

@@ -0,0 +1,31 @@
+# ADR-003: Replace raw SQL snapshot with sanitized dev baseline
+
+## Status
+Accepted
+
+## Context
+The tracked SQL file under `project/sql/db-25052026.sql` looked like a production snapshot.
+It exposed production-like and sensitive data in the working tree.
+The legacy PHP module still needs a database baseline for local work.
+
+## Decision
+Keep the same tracked SQL path but replace its content with a sanitized development baseline.
+The new baseline contains only the schema and synthetic seed data needed by the legacy PHP module.
+Document how to keep any private raw dump outside git.
+
+## Consequences
+- Good:
+  - active repo tree stops shipping raw sensitive SQL data
+  - local setup remains possible with a smaller safe dataset
+  - module development gets a focused baseline for current pages and worker
+- Bad:
+  - baseline no longer mirrors the full production dataset
+  - some future work may need extra synthetic fixtures
+
+## Alternatives considered
+1. Keep raw dump and add warning only - rejected because data risk remains in tracked files.
+2. Remove all SQL baseline files - rejected because local development would become harder.
+3. Rewrite full git history now - rejected because scope is too large for this feature.
+
+## Date
+2026-05-25