Overstory updated @os-eco/mulch-cli from 0.6.5 to 0.8.0, adopting the new non-destructive lifecycle behavior where `ml prune` now soft-archives stale records instead of deleting them.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
The PR’s primary technical change is the v0.8.0 lifecycle update: record cleanup is changed to write stale items into `.mulch/archive/<domain>.jsonl` by default, and a matching `ml restore <id>` path was added to move recovered records back into active expertise files. Hard deletion remains available through `--hard` only.
Operators and developers using mulch now avoid irreversible cleanup losses during maintenance, because stale records are preserved in an archive instead of being removed outright and can be restored when needed. This is especially important for shared knowledge bases where over-pruning can remove useful context. Track archive growth and cleanup policy, and verify restore behavior in multi-domain setups where ambiguous IDs can still fail, so you know when recovery workflows become operational bottlenecks.
Operators and developers using mulch now avoid irreversible cleanup losses during maintenance, because stale records are preserved in an archive instead of being removed outright and can be restored when needed. This is especially important for shared knowledge bases where over-pruning can remove useful context. Track archive growth and cleanup policy, and verify restore behavior in multi-domain setups where ambiguous IDs can still fail, so you know when recovery workflows become operational bottlenecks.