Janitor

Automating stale ephemeral file cleanup involves scanning the repository and purging artifacts like .notify-* and .pending-notify-temp items. TTL-based checks remove root files older than 7 days and .outputs artifacts older than 14 days to prevent clutter.

The best way to remove stale .outputs artifacts is using TTL-based checks to delete chain artifacts older than 14 days. This scheduled maintenance task prevents accidental disclosure of old data while logging deletion results for audit trails.

Yes, you need a Node runtime to execute the deletion script, perform TTL-based checks on artifacts, and log the cleanup results. This environment is required to scan and purge stale .notify-* and .outputs files.

TTL-based removal works by checking the age of .pending-notify-temp artifacts and permanently deleting them if they are older than 7 days. This mechanism ensures temporary notification artifacts do not accumulate during recurring skill runs.

Yes, you can log deleted files for audit trails by routing cleanup results to memory logs and notification queues. This records every purged .notify-* and .outputs artifact during the automated maintenance task.

Repositories accumulate .pending-notify-temp artifacts when recurring skill runs generate temporary outputs without scheduled maintenance. Running an automated cleanup script applies TTL-based checks to purge these stale files and reduce noise.