Update the example data used for local development
Example data written for an older database structure, updated so a new setup produces a working application.
The ticket
Update development seed data to match the current schema and produce a usable application state.
Acceptance criteria
- The seed runs clean against the latest migration
- It produces enough data to exercise the main flows
- It contains no real personal data
- Running it twice does not fail or duplicate
What lands as proof
A clean run against a freshly migrated database, ending in an application somebody can actually use.
Why teams defer it
- Everyone's local database was seeded before the schema moved, so nobody hits the break.
- Deciding what a useful seed contains needs product knowledge, not just schema knowledge.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: update development seed data to match the current schema and produce a usable application state. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means the seed runs clean against the latest migration, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.