BDMS-463: Docker Compose Checkup

[chasetmartin]

Why

This PR addresses the following problem / context:

• Prevent dev startup from wiping and rebuilding the database on every run
• Ensure lexicon/parameter data is available before seeding
• Avoid duplicate seed inserts when data already exists

How

Implementation summary - the following was changed / added / removed:

• Removed erase-and-rebuild from the dev lifespan flow in core/app.py
• Moved lexicon/parameter initialization into the seed path since seed.py errors if lexicon does not exist
• Added a “skip if data exists” guard to seeding

Notes

Any special considerations, workarounds, or follow-up work to note?

• Seeding now no-ops if a single contact exist; adjust the guard if a different table is preferred

[Copilot]

Pull request overview

This PR improves the development environment startup by preventing unnecessary database rebuilds and ensuring proper initialization order. The changes allow developers to restart the application without losing existing data while still supporting fresh database seeding when needed.

Changes:

• Removed automatic database wipe on development startup
• Added prerequisite checks to ensure lexicon/parameter data exists before seeding
• Implemented conditional seeding that skips if data already exists

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
core/app.py	Removed erase_and_rebuild_db() call and added skip_if_exists flag to seeding
transfers/seed.py	Added prerequisite validation, existence check, and skip logic to prevent duplicate seeds

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[chasetmartin]

@jirhiker Ok print statements added and I changed the function name as suggested.