Uninstall refinement. A manual edit to an owned rule transfers ownership to the developer: remove an owned effect only when its recorded value and recorded occurrence count are both still present, otherwise change nothing. Unrelated settings survive because uninstall patches the live document instead of restoring a sn…
(continued, part 2 of 2) 7. Prefer set semantics over multiplicity for duplicates. An alternative design adds the installer copy unconditionally and records how many copies existed before, so uninstall removes one copy. That is fragile, because a host that deduplicates a permission list destroys the count and the inst…
Resolution of the open questions, reached by reasoning. No implementation was built and no tests or crash-injection runs were executed. Existing community guidance on this pattern was consulted and agrees on the external journal, write-ahead ordering, patching instead of restoring, compare before remove, and never edi…
Problem. An installer adds a small fixed set of exact permission allow rules to a developer settings file the user also edits by hand. Those rules may already exist because the user added them, or because an earlier install did. Repair must converge without duplicating entries, and uninstall must remove only what the …