Removal plan and data declarations (dry run, no data touched)

Engine plan-removal dry run

simca-pack plan-removal compares the old and new spec and prints what would be archived or deleted; it changes nothing

Depends on: PKGR-0001

Engine removal plan defaults every element to keep

Choices are explicit per element (--keep, --toss); unnamed elements are kept; a choice for an element that is not removed is a blocker

Depends on: PKGR-0001

Engine removal plan orders dependents first

Removed elements are ordered so that dependents leave before the elements they depend on

Depends on: PKGR-0001

Engine removal plan states toss requirements

For each element the plan states backup-before-delete, the id to type, whether the extra acknowledgement is required and whether an export is offered

Depends on: PKGR-0001

Engine removal plan hash

The plan has a content hash; orders refer to it, so an order for another plan is refused

Depends on: PKGR-0001

Engine removal order validation

An order needs an explicit entry for every removed element; missing entries are invalid, never toss and never skip

Depends on: PKGR-0001

Engine blocks toss that would break a remaining reader

If a remaining element reads the tables of an element marked toss, the plan is blocked

Depends on: PKGR-0001

Engine blocks toss for elements without a data declaration

An element that does not declare its data can only be kept

Depends on: PKGR-0001

Pack data block (database, owned tables, data class)

Each pack declares which database it uses, the tables it owns with a class (config, reference, transactional, ledger, personal, derived) and what it reads from others

Depends on: PKGR-0001

Engine checks data declarations against the migrations

The paired check scans the SQL: every created table is declared, every declared table exists, no table has two owners, foreign keys point to declared tables of dependencies, Logistics tables stay in its own database

Depends on: PKGR-0001

Engine derives readers from the declarations

Who reads an element's data is derived from the readers' declarations, so the owner does not have to list them; a reader must depend on the owner

Depends on: PKGR-0001