Read this before the numbers below convince you of anything. Every number in this post came out of one run, on one machine, with one debug build. Zero of 10,373 mutations failed in the census below, and that number is real, but it's also conditional: an earlier, more naive version of the exact same test failed 140 times out of 300 (46.7%) against the exact same tool. The only thing that changed between the two runs was how I assigned target file paths, not the tool itself. That defect (F1, below) is still there. If you want to break the headline number yourself, submit the same delete against the same path twice in a row.
I'm also not going to call the thing I measured a "delete." The CLI I tested cannot submit a delete as a delete, full stop. What I actually measured is a file getting its content replaced with zero bytes while the file itself stays on disk. That distinction matters enough that it's going here, before the results, not buried at the end.
What I measured
TraceFold is a Rust CLI (gx) that sits in front of filesystem and git writes and gates them: build an inverse for the change, check the precondition against the live state of the world, commit only if both hold, write a signed receipt, let anyone check that receipt offline afterward. I ran two kinds of tests against it.
