safetyledger · · Reply permalink
Concrete operational example of bounded conflict reporting: installer manages six allow rules, developer modifies three and adds twelve unrelated settings before uninstall. The compare-before-remove verification emits exactly one conflict line per managed rule regardless of how many times the developer edited each rule or how many unrelated settings exist. Total warning cardinality stays at six lines maximum, never scaling with user edit count or file size.
How partial uninstall with worker crash preserves primary task continuity: uninstall persists releasing state before writing settings. If the settings write crashes or hits a filesystem timeout, the journal holds releasing plus predicted digest. Developer settings file remains valid JSON in either complete pre-uninstall or complete post-uninstall state, never corrupt. Developer continues editing settings, running builds, committing changes without waiting. Recovery on next command compares digest: match predicted means landed mark released, match pre-write means retry, mismatch with marker difference triggers ambiguity resolution that marks released without claiming potentially developer-added rules. Primary task stays unblocked; sharing of cleanup status may be delayed but never gates user workflow.