aboutsummaryrefslogtreecommitdiff
path: root/modules/ext/skill-pack-core.js
diff options
context:
space:
mode:
authorAgando <roduccomm@gmail.com>2026-10-23 21:24:04 +0200
committerAgando <roduccomm@gmail.com>2026-10-23 21:24:04 +0200
commit0090606421e32bc492f81f1c533bce9a41845a20 (patch)
treeacd872fa05c7425c426799068bb5773351f891f2 /modules/ext/skill-pack-core.js
parent70d7da9dc07f19661a74b19157473de86819e4eb (diff)
fix(newos4): the audit stops inventing '999d unused' (v4.6.85)
getStaleSkills() returned daysUnused=999 for a skill that had useCount 0 and no lastUsed — a placeholder rendered by the audit as '999d unused', indistinguishable from a measurement. It told the operator to archive procedural memory that had simply never been instrumented. Now: daysUnused null + neverUsed true when there is no lastUsed; real day count otherwise; the audit prints '(never used)'. Verified: probe skill with no telemetry -> {daysUnused: null, neverUsed: true}; one last used 2026-08-01 -> 83; no 999 anywhere in getStaleSkills() or the audit output.
Diffstat (limited to 'modules/ext/skill-pack-core.js')
-rw-r--r--modules/ext/skill-pack-core.js4
1 files changed, 3 insertions, 1 deletions
diff --git a/modules/ext/skill-pack-core.js b/modules/ext/skill-pack-core.js
index 67adf80..cba77b6 100644
--- a/modules/ext/skill-pack-core.js
+++ b/modules/ext/skill-pack-core.js
@@ -1206,7 +1206,9 @@ after the behaviour itself was fixed in v4.6.58.`),
}
for (var s of staleSkills) {
if (!index[s.name] || index[s.name].immune) continue;
- stale.push(s.name + ' (' + s.daysUnused + 'd unused)');
+ stale.push(s.name + (s.daysUnused === null || s.daysUnused === undefined
+ ? ' (never used)'
+ : ' (' + s.daysUnused + 'd unused)'));
}
// 2. Duplicate check (simple Levenshtein on name)