Plan a reversible package uninstall

Inputs: [INSTALL MANIFEST], [CURRENT FILE LIST], [USER DATA RULES]. Classify package-owned, shared and user-created paths. Design uninstall behaviour that preserves data and reports leftovers. Output: An ownership table, dry-run checklist and uninstall tests. Check: No user file is removed merely because it sits under the install directory. If essential information is missing, identify it rather than filling the gap with a guess. Require explicit ownership evidence for each proposed removal and retain uncertain paths.