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

work/current.md

@@ -1,27 +1,25 @@
 # Current session
 
-- Active feature: `F-002` — `Remove secrets and externalize config`
+- Active feature: `F-003` — `Sanitize SQL dump for safe dev use`
 - Start: `2026-05-25`
 - Orchestrator: `leader`
 
 ## Plan
-- Write SDD, ADR, and BDD trace for config externalization.
-- Add one config loader for legacy PHP module.
-- Remove hard-coded DB and OpenAI secrets from versioned PHP files.
-- Centralize URLs and external endpoints in local config.
-- Run `./scripts/verify.sh` and security scan.
+- Write SDD, ADR, and BDD trace for safe SQL baseline.
+- Replace raw production-like SQL dump with sanitized dev baseline.
+- Document safe local data handling.
+- Run `./scripts/verify.sh` and data-risk checks.
 
 ## Log
-- Feature `F-001` is blocked by security gate because secrets remain in repo.
-- Created follow-up ticket `F-002`.
-- Switched active work item to `F-002`.
-- Wrote SDD, ADR, and BDD trace for config externalization.
-- Added shared config loader and local config template for legacy PHP module.
-- Removed hard-coded DB and OpenAI secrets from tracked PHP files.
-- Replaced inline production URLs in tracked PHP files with config lookups.
-- Ran verify and security scans.
-- Reviewer, security, QA, and documenter artifacts for `F-002` are on disk.
+- Feature `F-002` was closed and published.
+- Publish artifact exists at `work/artifacts/F-002/publish.json`.
+- Created follow-up ticket `F-003` for SQL dump sanitization.
+- Switched active work item to `F-003`.
+- Wrote SDD, ADR, and BDD trace for safe SQL baseline.
+- Replaced tracked raw SQL snapshot with sanitized development baseline.
+- Added SQL handling docs and ignored private SQL path guidance.
+- Ran verify and data-risk scans.
+- Reviewer, security, QA, and documenter artifacts for `F-003` are on disk.
 
 ## Next step
-- Publish `F-002`.
-- Create follow-up ticket for SQL dump sanitization.
+- Publish `F-003`.