F-003 fix: Sanitize SQL dump for safe dev use
This commit is contained in:
25
work/artifacts/F-003/architect.md
Normal file
25
work/artifacts/F-003/architect.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Architect Artefact — Feature: F-003
|
||||
|
||||
## SDD Changes
|
||||
- Added `spec/sdd/decisions/003-replace-raw-sql-with-sanitized-dev-baseline.md`
|
||||
- Extended product, tech, and acceptance specs for F-003
|
||||
- Will update development baseline component doc to reflect sanitized synthetic dataset
|
||||
|
||||
## BDD Coverage
|
||||
- Added `spec/bdd/features/data/sanitized-sql-baseline.feature`
|
||||
- Coverage target:
|
||||
- tracked SQL baseline is sanitized
|
||||
- private local data handling is documented
|
||||
|
||||
## Technical decisions
|
||||
- Keep the current tracked SQL path for compatibility.
|
||||
- Replace raw snapshot content with a small sanitized baseline.
|
||||
- Seed only the tables and sample data needed by the legacy PHP module.
|
||||
|
||||
## Risks found
|
||||
- Raw dump still exists in git history from earlier commits.
|
||||
- Synthetic baseline may not cover every future workflow without more fixtures.
|
||||
|
||||
## Next step
|
||||
- Replace tracked SQL file content with safe synthetic baseline.
|
||||
- Add SQL handling docs and ignored path guidance.
|
||||
Reference in New Issue
Block a user