JTBD-PK-04 · Package developer
Remove a package without losing its data
partially supported. Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.
What the catalogue records
removing the import removes actions, schema block and Admin section; the tables and rows are left untouched. There is no uninstall, no data migration and no cleanup command — orphaned tables stay orphaned
Evidence
This row carries no test path of its own in the structured index. The matrix records the evidence for it in a block shared with neighbouring rows, which jobs.json does not split per row — so read docs/benchmarks/CRM_JTBD_MATRIX.md for it. The status above was set from that evidence, not from its absence.
What this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Package developer
- Create and compose a custom local domain package — validated end to end
- Depend on another package without importing its source — validated end to end
- Validate a package before booting it — partially supported
- Scaffold a new package from a template — not supported
- Install a package from a registry or marketplace — not supported
- Run an untrusted package safely — not supported