Skip to content

[Issue]: Improve pruning dry-run summaries and reporting #20

@MrAdder

Description

@MrAdder

Issue Type

Feature request

Summary

Make pruning output more informative so users can understand what would be removed or was removed more easily.

Problem / Context

Pruning already exists, but the operational feedback can be expanded to better support dry runs, reporting, and retention review.

Proposed Solution

Add clearer dry-run summaries and reporting details for pruning activity, especially around counts, scope, and matching criteria.

Acceptance Criteria

  • Dry-run output is more informative and easier to interpret.
  • Real pruning runs provide useful summary information.
  • The command remains simple to use and backward-compatible.

Implementation Notes

Review the prune command output and how best to expose summary information without creating noisy logs.

Testing Notes

Extend pruning command tests to cover the new summary and reporting behavior.

Additional Context

This should improve retention workflows without changing retention semantics.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions