Back to Signal Feed
ProductionTracked since May 16, 2026

Mulch CLI upgrade makes `ml prune` non-destructive by default

Overstory’s dependency bump to `@os-eco/mulch-cli` 0.8.0 is mainly about safer record lifecycle handling: `ml prune` now defaults to soft-archiving stale records instead of deleting them, so cleanup becomes reversible when operators hit a bad classification. This is the key behavioral shift that changes how teams can recover from maintenance mistakes.

@os-eco/mulch-climl prunesoft-archive.mulch/archive

What Happened

  • Overstory’s dependency bump to `@os-eco/mulch-cli` 0.8.0 is mainly about safer record lifecycle handling: `ml prune` now defaults to soft-archiving stale records instead of deleting them, so cleanup becomes reversible when operators hit a bad classification. This is the key behavioral shift that changes how teams can recover from maintenance mistakes.
  • Overstory’s dependency bump to `@os-eco/mulch-cli` 0.8.0 is mainly about safer record lifecycle handling: `ml prune` now defaults to soft-archiving stale records instead of deleting them, so cleanup becomes reversible when operators hit a bad classification. This is the key behavioral shift that changes how teams can recover from maintenance mistakes.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Upgrades overstory’s mulch-cli dependency to 0.8.0, where the prune lifecycle behavior changes from hard deletion to soft archive by default; stale records are retained in archive files with lifecycle metadata, enabling controlled recovery instead of immediate data loss.

Why Track This

Why It Matters

Repo operators and maintainers using `ml prune` can now recover from overly aggressive cleanup runs, because stale records are preserved in archive files instead of being deleted, reducing operational risk when maintaining shared knowledge data. The release also adds explicit archived-state tracking (`status: "archived"`, `archived_at`) and restoration support, improving rollback visibility and recovery flow. Watch for scripted cleanup workflows that assumed deletion, monitor archive growth, and validate cross-domain restore behavior so recovery does not become ambiguous.

Impact

Repo operators and maintainers using `ml prune` can now recover from overly aggressive cleanup runs, because stale records are preserved in archive files instead of being deleted, reducing operational risk when maintaining shared knowledge data. The release also adds explicit archived-state tracking (`status: "archived"`, `archived_at`) and restoration support, improving rollback visibility and recovery flow. Watch for scripted cleanup workflows that assumed deletion, monitor archive growth, and validate cross-domain restore behavior so recovery does not become ambiguous.

What To Watch Next

  • Watch whether @os-eco/mulch-cli becomes a repeated pattern.
  • Track follow-up changes around Model Routing and Gateways.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: scripts_assuming_hard_delete_after_prune, archive_storage_growth.
Open Topic TimelineOpen Technical EventOpen Original Sourcescripts_assuming_hard_delete_after_prune / archive_storage_growth / restore_cross_domain_ambiguity

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

jayminwest/overstory PR #150: chore(deps): bump @os-eco/mulch-cli from 0.6.5 to 0.8.0

Version bump to `@os-eco/mulch-cli` 0.8.0 introduces soft-archive default for `ml prune`, storing stale records in `.mulch/archive/<domain>.jsonl` with `status: "archived"` and `archived_at`, and adds recovery paths.