Back to Signal Feed
ProductionTracked since May 16, 2026

mulch-cli 0.8.0 upgrade adds non-destructive prune by default

Overstory’s dependency bump from `@os-eco/mulch-cli` 0.6.5 to 0.8.0 adopts the version’s new default for `ml prune`: stale records are moved to `.mulch/archive/<domain>.jsonl` instead of being immediately deleted, with hard deletion now behind `--hard`.

@os-eco/mulch-climl prunesoft-archive.mulch/archive/<domain>.jsonl

What Happened

  • Overstory’s dependency bump from `@os-eco/mulch-cli` 0.6.5 to 0.8.0 adopts the version’s new default for `ml prune`: stale records are moved to `.mulch/archive/<domain>.jsonl` instead of being immediately deleted, with hard deletion now behind `--hard`.
  • Overstory’s dependency bump from `@os-eco/mulch-cli` 0.6.5 to 0.8.0 adopts the version’s new default for `ml prune`: stale records are moved to `.mulch/archive/<domain>.jsonl` instead of being immediately deleted, with hard deletion now behind `--hard`.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Introduces a safer record lifecycle: prune becomes recoverable by default, routing old/stale entries into a dedicated archive file with status metadata, while deletion is explicit via `--hard`, which prevents accidental irreversible cleanup from a normal pruning pass.

Why Track This

Why It Matters

For teams running mulch-based knowledge workflows, a prune operation is less destructive by default, so one bad classification or cleanup run is less likely to wipe out useful records permanently. Technically, the upgrade changes default prune semantics to archive records as `status: archived` with `archived_at` metadata and enables rehydration via `ml restore`, so operators should watch archive growth, restore reliability under heavy churn, and any ID-ambiguity behavior when reactivating records.

Impact

For teams running mulch-based knowledge workflows, a prune operation is less destructive by default, so one bad classification or cleanup run is less likely to wipe out useful records permanently. Technically, the upgrade changes default prune semantics to archive records as `status: archived` with `archived_at` metadata and enables rehydration via `ml restore`, so operators should watch archive growth, restore reliability under heavy churn, and any ID-ambiguity behavior when reactivating records.

What To Watch Next

  • Watch whether @os-eco/mulch-cli becomes a repeated pattern.
  • Track follow-up changes around AI Governance and Compliance.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: archive_size_bloat, restore_latency_under_load.
Open Topic TimelineOpen Technical EventOpen Original Sourcearchive_size_bloat / restore_latency_under_load / cross_domain_id_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

The PR bumps mulch-cli to 0.8.0, whose release notes describe default soft-archive prune behavior and recovery tooling.