16 lines
1.3 KiB
Markdown
16 lines
1.3 KiB
Markdown
# Change: Unify TrueGrowth local data persistence
|
|
|
|
## Why
|
|
TrueGrowth desktop currently stores business data across Electron browser storage, project-local runtime files, desktop runtime files, JSON shadows, and small SQLite stores. Repeated local runs and different ports can make data appear lost because each browser origin and runtime root sees a different persistence estate.
|
|
|
|
## What Changes
|
|
- Add one desktop-local persistence contract centered on a canonical per-user data directory and SQLite ledger.
|
|
- Route Local API business data through the canonical storage layer for tasks, assets, workflow state, social publishing state, runtime settings, and migration records.
|
|
- Add diagnostics, migration, export, and import endpoints so data roots and legacy sources are visible and recoverable.
|
|
- Keep browser storage for UI preferences, caches, and temporary offline queues rather than treating it as the final business-data source.
|
|
- Preserve legacy project-local runtime data by indexing or importing metadata without deleting or moving large output files automatically.
|
|
|
|
## Impact
|
|
- Affected specs: `desktop-local-persistence`
|
|
- Affected code: `scripts/truegrowth-local-api.mjs`, Electron startup environment, local runtime client helpers, storage diagnostics and migration flows
|