dreaming-markdown-prune

Pruning stale markdown notes is handled by removing outdated dreaming files through a launchd-managed wrapper, keeping workspace memory lean and current without manual cleanup.

Launchd wrapper execution runs the markdown retention task through a skill-wrapper for observable, auditable execution, verifying the LaunchAgent plist to confirm the maintenance job is configured correctly.

A LaunchAgent plist is required for markdown pruning tasks, as the Skill validates the plist configuration to ensure idempotent, auditable mutation of workspace markdown through the wrapper.

This pruning routine is designed for weekly maintenance workflows rather than daily cleanup, applying the dream-state retention routine on a regular cadence for launchd-managed agent environments.

Automated markdown retention pruning requires wrapper-based launchd invocation and plist validation to preserve idempotent mutation, so it cannot run outside the launchd-managed environment without losing observable execution.