@nightlab-agent/turn-tally 0.2.3 → 0.2.4

package/.claude-plugin/marketplace.json

@@ -8,7 +8,7 @@
       "name": "turn-tally",
       "source": "./",
       "description": "Steps, tool calls and tool-error streak of the running session, in a file and the status line.",
-      "version": "0.2.3",
+      "version": "0.2.4",
       "category": "productivity"
     }
   ],

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "turn-tally",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Writes the session's model steps, tool calls and tool-error streak to a file and the status line, so a headless or budgeted session can read its own budget.",
   "author": { "name": "Nightlab" },
   "license": "MIT",

package/CHANGELOG.md

@@ -4,6 +4,13 @@ The form is Keep a Changelog; versions follow SemVer.
 
 ## [Unreleased]
 
+## 0.2.4 - 2026-10-28 - says what each hook does, and that nothing leaves the machine
+
+### Changed
+- README: a table of each hook, what it does, what it changes (nothing) and the file it writes each day; it says plainly that no data leaves the machine.
+- The design comment and CLAUDE.md say what the module reads (only the events the engine hands it) instead of listing what it does not read.
+- plugin.json: the `types` field is gone (not part of the plugin manifest; the `types/` folder stays for the module).
+
 ## 0.2.3 - 2026-10-28
 
 ### Added

package/README.md

@@ -63,6 +63,20 @@ rewritten whole each step, so a reader never sees a partial line. Two
 sessions on the same day write the same file; the last step wins, and the
 `updated` line says when.
 
+## What each hook does, what it changes, what it writes
+
+Everything stays on your machine: the mod makes no network request and sends
+nothing anywhere. It only reads the events Claude Code hands it.
+
+| Hook | What it does | Changes |
+|---|---|---|
+| `tool.call` | Counts the call, and whether it came back as an error. | Nothing: the call runs as asked and its result passes through. |
+| `turn.step` (main loop only) | Counts the step; updates the status line; rewrites the day's file. | Nothing: the request and the response pass through untouched. |
+
+It writes one file per day, `~/.turn-tally/<YYYY-MM-DD>.txt` (or under
+`TURN_TALLY_DIR`), holding only counts, the model name and a time. No tool
+input, prompt or reply text is stored.
+
 ## What it does not do
 
 No tokens or dollars: see
@@ -89,7 +103,7 @@ falls back to `$HOME`, and a failed write does not fail the step.
 
 ## Status
 
-Version 0.2.3, 2026-10-28. An earlier private version has run in the
+Version 0.2.4, 2026-10-28. An earlier private version has run in the
 author's own headless sessions since 2026-10-27 (one session read its own
 count: steps 18, tool calls 17, errors 0). Not yet confirmed in an
 interactive session on another machine; if the status line or the file does

package/hooks/register.ts

@@ -9,7 +9,7 @@ import type { Register } from 'claude-code'
 // cap fires silently.
 //
 // DESIGN NOTE, deliberately narrow: it never denies, never rewrites a call,
-// never reads settings or credentials, never touches the network. A failed
+// reads only the events the engine hands it, sends nothing off the machine. A failed
 // write is swallowed: the tally is advisory, and a gauge that stops the
 // engine would be worse than no gauge. Steady state is one status line and
 // one file; nothing is printed to the transcript.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nightlab-agent/turn-tally",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Claude Code mod: writes the session's model steps, tool calls and tool-error streak to a file and the status line, so a headless or budgeted session can read its own budget.",
   "keywords": [
     "claude-code",