BIG NEW RELEASE: v0.25.0 -- we finally solved the damn deletions problem

[steveyegge]

Hi all,

We've had a problem forever where beads deleted with bd delete would get resurrected when another clone synced. This is because I was refusing to introduce tombstones, since they would quickly overwhelm the issues.jsonl file. But I finally came up with a way to handle deletions properly without tombstones, and implemented it in this release.

The solution: a deletions manifest, basically an append-only extra logfile we keep, which self-heals if it breaks (we can always reconstitute it from the git history). This file can actually be pruned to keep it small, since the risk of resurrection from a stale clone drops exponentially over time. You can dial the pruning to balance your file size with risk of resurrections.

Overall, I'm very pleased with this solution. It's lightweight, it's robust, and we'll finally stop getting resurrected issues all the time. With this, I think we finally have all the major edge cases for merging handled, and beads should finally be low-friction on bd sync most of the time.

As always, the CHANGELOG has the gory details. We added some more support for orchestration systems and other goodies.

[TheEditor]

Given some of the entries in the changelog should files in the /examples/claude-code-skill folder be updated? I'd think at least https://github.com/steveyegge/beads/blob/main/examples/claude-code-skill/references/CLI_REFERENCE.md.