agent-dag 3.3.0 → 3.5.0

package/release-notes.json

@@ -31,6 +31,22 @@
     "about a defect in the type, and the suite refuses both it and no space at",
     "all."
   ],
+  "3.5.0": [
+    {
+      "title": "⚡ The figures move when the work happens",
+      "body": "Reading your usage off the logs is not free — measured here, one reading is 7.8 seconds of CPU, because ccusage walks every transcript on the machine whatever period you asked for. Once a minute is affordable; once every ten seconds would be three quarters of a core, permanently, for numbers that move slowly.\n\nSo the reading stays on a minute and the deck fills the gap with what it already knows. Every hook event carries its session's running total, so the panel adds whatever has been spent since the last reading and counts up to it. The headline now moves when a turn finishes rather than on the clock, and it costs nothing extra.\n\nIt only ever adds. A session leaving the canvas cannot pull the figure down, and the next reading corrects whatever the estimate got wrong — the tokens are exact, and the dollars in between are priced by the deck's own table.\n\nTwo smaller things with it: pressing today, month or all now counts between the two figures instead of swapping them, and coming back to the tab only re-reads if what is on screen is actually stale."
+    }
+  ],
+  "3.4.0": [
+    {
+      "title": "🔢 The figures count to their new value, once a minute",
+      "body": "The Usage panel re-reads its numbers every minute now rather than every five, and it is a real minute — the server used to hold a reading for two, so a shorter poll would have handed the same figure back.\n\nAnd they no longer teleport. Replaced in a single frame, $170 → $269 says only \"this is different now\": no direction, no sense of how much, and nothing at all if your eye was a few pixels away. Counted over a fifth of a second, the same change says up, and roughly how far.\n\nWhat deliberately does not count: the first paint, a change of period — \"today\" and \"all time\" are different quantities rather than one that moved — the tables, a change too small to read, and anything at all if you have reduced motion on or the tab is in the background."
+    },
+    {
+      "title": "🧹 The board's own figure is out of the Usage panel",
+      "body": "3.3.0 put the canvas's live spend on its own labelled line, under whichever period you had chosen. In front of a panel that answers today, this month and all time from the logs on disk, that second money figure answers a question nobody asked at that moment — and it invited a comparison it could never win, $7,385 on the board beneath $170 for today.\n\nIt is gone. The board's tokens and cost are still on the topbar, with the sentence that explains why they fall on their own, and the panel still shows them when ccusage cannot answer at all."
+    }
+  ],
   "3.3.0": [
     {
       "title": "📊 The Usage panel answers for a period, not just for the board",

package/src/server/ccusage.mjs

@@ -19,7 +19,12 @@ import { killTree, pathLookup, shimPath, spawnSpec } from "./exec.mjs";
 import { oneLine, termColumns } from "./term.mjs";
 import { PRODUCT } from "./brand.mjs";
 
-const CACHE_MS = 120_000; // 2 min — modal is manual-open; cheap to keep warm
+// 60s, and it is the panel's poll interval rather than a number of its own: the
+// Usage panel asks once a minute and expects a reading that has actually moved,
+// so a longer cache would hand the same figure back and make the interval a
+// lie. Two tabs polling out of phase still share one run, which is what the
+// cache is for here. The modal is manual-open and unaffected either way.
+const CACHE_MS = 60_000;
 const TIMEOUT_MS = 90_000;
 const INSTALL_TIMEOUT_MS = 120_000; // first-run npm install can be slow
 const UPDATE_CHECK_MS = 24 * 3600_000; // check npm for a newer ccusage once/day