Problem
The nap.ts archival bugs were shipped with 38 tests — but only 2 covered archival, both happy-path. No checklist exists for required edge cases when writing archival/pruning functions.
From
Postmortem action item A6.
Proposed
Add to CONTRIBUTING.md or .squad/skills/nap/SKILL.md: any archival/pruning function MUST test:
- Undated entries (no YYYY-MM-DD in heading)
- All-recent entries (all <30 days old, file over threshold)
- Empty file / single entry
- Mixed dated + undated entries
- Data-loss invariant (before_count = kept + archived)
- Realistic fixture (sample from actual repo's decisions.md)
Owner
Procedures (Prompt Engineer)
Problem
The nap.ts archival bugs were shipped with 38 tests — but only 2 covered archival, both happy-path. No checklist exists for required edge cases when writing archival/pruning functions.
From
Postmortem action item A6.
Proposed
Add to CONTRIBUTING.md or
.squad/skills/nap/SKILL.md: any archival/pruning function MUST test:Owner
Procedures (Prompt Engineer)