Problem
Archival thresholds are hardcoded constants in nap.ts (20KB, 30 days). Different projects have different write rates. Active projects need lower thresholds; stable projects can tolerate higher ones.
From
Flight + EECOM reviews of #20 (solution A5).
Proposed Schema
{
"decisions": {
"maxSizeKB": 15,
"archiveAfterDays": 30,
"archiveImplementedAfterDays": 7,
"autoArchiveImplemented": true,
"maxEntries": 75,
"warnAtSizeKB": 10
}
}
nap.ts reads from config.json, falls back to current hardcoded defaults.
Owner
EECOM (Core Dev)
Problem
Archival thresholds are hardcoded constants in nap.ts (20KB, 30 days). Different projects have different write rates. Active projects need lower thresholds; stable projects can tolerate higher ones.
From
Flight + EECOM reviews of #20 (solution A5).
Proposed Schema
{ "decisions": { "maxSizeKB": 15, "archiveAfterDays": 30, "archiveImplementedAfterDays": 7, "autoArchiveImplemented": true, "maxEntries": 75, "warnAtSizeKB": 10 } }nap.ts reads from config.json, falls back to current hardcoded defaults.
Owner
EECOM (Core Dev)