Catalog section · LNCH
12 planned items in Simca Launcher (Steam-like): Offline Mode, User-Initiated Updates, Package Spec, Sign-in.
When elements are unticked, one screen lists each removed element, the tables it holds and what happens to them; nothing is applied until the customer confirms
Depends on: LNCH-0001
Each removed element starts as KEEP (archived, read-only, restorable); a plan file cannot change that default
Depends on: LNCH-0001
Deleting an element's data requires typing that element's id; no checkbox alone is enough
Depends on: LNCH-0001
Deleting ledger-class or personal-class data needs a second explicit acknowledgement on top of the typed id
Depends on: LNCH-0001
There is no toss-all button and no toss by omission; each element is decided on its own line
Depends on: LNCH-0001
Before a toss the customer can export the element's tables to a folder (JSON lines); the export is optional, the backup is not
Depends on: LNCH-0001
Unticked elements that remain because a remaining element depends on them are listed as information, not as an error
Depends on: LNCH-0001
A plan with blockers (for example a toss that would break a remaining reader) cannot be confirmed; the reasons are shown in plain language
Depends on: LNCH-0001
Ticking an element again brings its kept data back exactly as it was, with no import step
Depends on: LNCH-0001
A screen lists kept (archived) data per element with size and date, and lets the customer restore it or delete it later with the same confirmations and a backup first
Depends on: LNCH-0001
After the run the customer sees what was kept, what was deleted, and where the pre-delete backup is
Depends on: LNCH-0001
The order handed to the app carries the plan hash and one explicit entry per removed element; the app refuses anything else
Depends on: LNCH-0001