Reorganize seeder presets into purpose-based folders and remove obsolete presets#7176
Reorganize seeder presets into purpose-based folders and remove obsolete presets#7176theMickster merged 2 commits intomainfrom
Conversation
|
Claude finished @theMickster's task in 2m 15s —— View job Re-Review: Reorganize seeder presets into purpose-based foldersSummaryThe fix commit (4aae641) correctly updates all 8 moved preset files to use All previous findings addressed:
No new issues found. No security, performance, or production code concerns -- all changes remain within Approved -- ready to merge. |
|
Great job! No new security vulnerabilities introduced in this pull request |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7176 +/- ##
=======================================
Coverage 56.88% 56.88%
=======================================
Files 2028 2028
Lines 88826 88830 +4
Branches 7918 7918
=======================================
+ Hits 50528 50531 +3
- Misses 36468 36469 +1
Partials 1830 1830 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|




🎟️ Tracking
PM-31023 - Relational Density Modeling
PM-32777 - Baked-In Density Preset Profiles
📔 Objective
Why the re-organization or presets?
The seeder is still early-adoption — breaking preset names now costs nearly nothing, but doing it after teams build scripts around them has cost. Purpose-based folders (features/qa/scale/validation) make preset discovery self-documenting so engineers don't need to read a README to find the right one. Consolidating docs into Seeds/docs/ eliminates duplication across scattered READMEs and separates everyday usage from developer-only verification content.