Apollo Persistence Bootstrap

Overview

This domain owns how Apollo boots its local runtime, prepares SQLite, runs migrations, exposes bootstrap metadata, and wires concrete repositories and adapters into AppState. Prefer schema-first changes and keep startup composition explicit.

Workflow

1. Start with the storage contract: migration files, repository queries, and domain/application structs must stay synchronized.
2. Keep SQLite setup in infrastructure. AppState::new composes concrete implementations, but it should not hide schema drift.
3. Update BootstrapSnapshot and related frontend contracts whenever startup metadata changes.
4. Preserve initialization order in src-tauri/src/lib.rs: logging, plugin wiring, database bootstrap, AppState, then window-specific runtime adjustments.
5. When changing repository behavior, update in-memory or temp-file tests before editing production paths.

Implementation Notes

• is the safe entry point for schema readiness.