claude-usage-limits 1.5.2 → 1.5.3

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "usage-limits",
   "displayName": "Usage Limits",
-  "version": "1.5.2",
+  "version": "1.5.3",
   "description": "Puts your remaining Claude Code usage limit into Claude's context before every prompt, so it opens with what fits in the budget instead of starting work that gets cut off. Reports headroom as turns rather than percentages, prices a job before you start it, and detects your plan tier.",
   "author": {
     "name": "Ridelink",

package/README.md

@@ -187,6 +187,11 @@ The split comes from measured spend rather than an assumption that everyone is
 working equally hard, because they usually are not. A session that has gone
 quiet for a quarter of an hour is not counted as competing.
 
+Every session's spend also feeds the reading itself, not just the split. The
+percentage is corrected using all spend recorded since the snapshot was taken,
+whichever window produced it, so another Claude burning budget in the next
+terminal moves your number too.
+
 ## Which limit it watches
 
 Two windows run at once and the 5-hour one is usually what actually stops you,
@@ -497,7 +502,7 @@ test/                             node --test, no dependencies
 node --test
 ```
 
-164 tests over the pricing, the window arithmetic, plan and credit detection,
+179 tests over the pricing, the window arithmetic, plan and credit detection,
 the status line, the before-prompt line, job forecasting, per-project
 attribution, the CLI, packaging, and the settings save/restore.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-usage-limits",
-  "version": "1.5.2",
+  "version": "1.5.3",
   "description": "Puts your remaining Claude Code usage limit into Claude's context before every prompt, so it opens with what fits in the budget instead of starting work that gets cut off. Reports headroom as turns rather than percentages, prices a job before you start it, and detects your plan tier.",
   "keywords": [
     "claude",