Problem
When archiveDecisions() returns null on a file over threshold (because all entries are undated or recent), the nap report says 'nothing to clean up' — indistinguishable from a healthy file under threshold. Users see no warning.
From
Postmortem action item A5, contributing factor CF4.
Proposed Fix
When file is over DECISION_THRESHOLD but archival returns null (no entries archived), emit a warn action in the nap report:
[WARN] decisions.md is 345KB but no entries could be archived (all recent or undated) Consider: squad nap --deep, or manually archive old entries
Distinguish 'nothing needed' from 'cleanup attempted but conditions not met'.
Owner
EECOM (Core Dev)
Problem
When
archiveDecisions()returnsnullon a file over threshold (because all entries are undated or recent), the nap report says 'nothing to clean up' — indistinguishable from a healthy file under threshold. Users see no warning.From
Postmortem action item A5, contributing factor CF4.
Proposed Fix
When file is over
DECISION_THRESHOLDbut archival returns null (no entries archived), emit awarnaction in the nap report:[WARN] decisions.md is 345KB but no entries could be archived (all recent or undated) Consider: squad nap --deep, or manually archive old entriesDistinguish 'nothing needed' from 'cleanup attempted but conditions not met'.
Owner
EECOM (Core Dev)