claude-usage-limits 1.11.7 → 1.13.1

package/skills/usage-limits/scripts/statusline.js

@@ -144,13 +144,14 @@ function planOn(settings, state, options) {
   const opts = options || {};
   const launcher = opts.launcher || launcherFile();
   const existing = current.statusLine === undefined ? null : current.statusLine;
-  // A second "on" must not record our own launcher as the thing to restore.
-  const previous =
-    state && Object.prototype.hasOwnProperty.call(state, 'previous')
-      ? state.previous
-      : isOurs(existing, launcher)
-        ? null
-        : existing;
+  // What "off" must put back is whatever is in the settings right now that is
+  // not ours. A second "on" must not record our own launcher as that thing -
+  // but it must not keep an old memory either: a status line the user set
+  // between two "on" runs was being overwritten and lost, because the first
+  // run's record was trusted over the file in front of us.
+  const remembered =
+    state && Object.prototype.hasOwnProperty.call(state, 'previous') ? state.previous : null;
+  const previous = isOurs(existing, launcher) ? remembered : existing;
   const command = 'node ' + JSON.stringify(launcher);
   const statusLine = { type: 'command', command };
   if (Number.isFinite(opts.refresh) && opts.refresh >= 1) statusLine.refreshInterval = Math.floor(opts.refresh);

package/skills/usage-limits/scripts/tally.js

@@ -46,15 +46,14 @@ function readState() {
   }
 }
 
+// Atomic, because this file is read, changed and written back by the Stop hook
+// of every session at once. A torn read here did not just lose one total: the
+// reader parsed nothing, then wrote its own slot back as the whole file, and
+// every other session's tally went with it.
 function writeState(all) {
-  try {
-    const file = stateFile();
-    fs.mkdirSync(path.dirname(file), { recursive: true });
-    fs.writeFileSync(file, JSON.stringify(all), 'utf8');
-  } catch (err) {
-    // Losing the total costs one re-read of the transcript. Failing the hook
-    // that runs after every reply is not worth avoiding that.
-  }
+  // Never throws: losing the total costs one re-read of the transcript, and
+  // failing the hook that runs after every reply is not worth avoiding that.
+  usage.writeJsonAtomic(stateFile(), all);
 }
 
 function isSession(value) {