transcripto 0.1.2__tar.gz → 0.1.4__tar.gz

{transcripto-0.1.2/transcripto.egg-info → transcripto-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: transcripto
-Version: 0.1.2
+Version: 0.1.4
 Summary: Search everything your coding agents ever did, grade your own prompts, and price your decisions. Local, stdlib-only, your data never leaves the machine.
 Author: Oscar Morke
 License: MIT
@@ -29,19 +29,11 @@ your disk and never opens a socket.
 uvx transcripto coach
 ```
 
-> **check which build you got.** `trace`, `--harness cursor`, and the "run `index`
-> first" errors below all arrive in **0.1.2**. On anything older, `trace` is not a
-> command, cursor is rejected, and the index-gated commands fail with a raw sqlite
-> traceback instead of an instruction. One line settles which one you are holding:
+> **which build you got.** `uvx transcripto --version` should print **0.1.3**. If `--version`
+> is not a recognised flag at all you are on 0.1.1, which predates `trace`, Cursor support and
+> this README. `uvx --refresh transcripto` forces a fresh resolve past uv's cache.
 >
-> ```
-> uvx transcripto --version          # 0.1.2 or newer = this README is accurate
-> ```
->
-> *Read 2026-08-31: PyPI was serving 0.1.1 while this README described 0.1.2, so
-> `uvx transcripto` gave the older build. If `--version` is not even a recognised
-> flag, you have 0.1.1 — it was added in 0.1.2 precisely because there was no way
-> to tell.* The repo always matches this README and needs nothing installed:
+> The repo always matches this README and needs nothing installed:
 >
 > ```
 > git clone https://github.com/Morkeeth/transcripto && cd transcripto
@@ -81,41 +73,48 @@ the same way.
 
 ## what you get back
 
-this is a real run on one machine, pasted unedited, 2026-08-28:
+this is a real run on one machine, 2026-08-31. The numbers are unedited; the two quoted prompts are synthetic stand-ins of the same shape, because your prompts never leave your machine and neither do mine:
 
 ```
 
   YOUR PROMPT HABITS, GRADED   (offline, your machine only)
 
-  harness: claude
-  corpus : 2720 transcript(s), 381,804 records
-  kept   : 3678 prompts you actually typed (0.96% of records)
-  episodes: 1946 ranked, 910 survived (47%)
-  tiers  : commit 373 | write/edit 537 | reverted 2 | nothing durable 1034
+  - your worst looped prompt, with its witness:
+      "hmm ok lets just try again and see if it works this time, same thing as before but…"
+      NO-DURABLE-RECORD: read-only Bash only, no file change  ·  corrections: 15  ·  assistant turns: 221
+
+  + your best landed prompt, with its witness:
+      "TERMINAL 3 — parser · ~/CODE/demo Read hack.md. Fix the counter, run the suite, commit if green…"
+      COMMIT-WITNESSED: git commit  ·  corrections: 0
 
   SURVIVAL IS A PROXY: survival = a durable Write/Edit or an un-reverted git commit in-episode. A PROXY, not proof the work was correct or shipped.
 
   SURVIVES MOST  do more of these:
-     64%  (167/260)  detailed (>40 words)
-     63%  (66/104)  states-a-check-or-done-condition
-     58%  (414/708)  intent:CHANGE
-     58%  (21/36)  no-object (pronoun/vague)
-     57%  (99/175)  cites-a-file-or-path
+     65%  (71/110)  states-a-check-or-done-condition
+     64%  (178/276)  detailed (>40 words)
+     59%  (22/37)  no-object (pronoun/vague)
+     59%  (451/763)  intent:CHANGE
+     57%  (106/187)  cites-a-file-or-path
 
   SURVIVES LEAST  these tend to loop:
-     33%  (4/12)  intent:REVERT
-     39%  (411/1043)  intent:none
-     40%  (4/10)  intent:TEST
-     42%  (298/715)  terse (<8 words)
-     45%  (77/173)  intent:DESCRIBE
-
-  + your best landed prompt, with its witness:
-      "mTERMINAL 8 — Mountain of Helicon · ~/CODE/mountain-of-helicon Read ~/CODE/mountain-of-helicon. Two…"
-      COMMIT-WITNESSED: git commit  ·  corrections: 0
-
-  - your worst looped prompt, with its witness:
-      "ok, and lets see they might solve it in the future so i can go back to my beloeved routine :) Befor…"
-      NO-DURABLE-RECORD: read-only Bash only, no file change  ·  corrections: 15  ·  assistant turns: 221
+     31%  (4/13)  intent:REVERT
+     40%  (451/1129)  intent:none
+     42%  (320/765)  terse (<8 words)
+     42%  (81/192)  intent:DESCRIBE
+     45%  (5/11)  intent:TEST
+
+  harness claude  ·  2957 transcript(s), 431,085 records  ·  3969 typed by you (0.92%)
+  episodes: 2108 ranked, 992 survived (47%)
+  commit 454  ·  write/edit 538  ·  reverted 2  ·  nothing durable 1114
+
+  ─────────────────────────────────────────────────────────
+   compare yours. numbers only, nothing from your prompts:
+
+   transcripto coach · claude · 2108 episodes · 47% survived
+   states-a-check-or-done-condition    65%  (71/110)
+   intent:none                         40%  (451/1129)
+   gap                                 1.6x
+  ─────────────────────────────────────────────────────────
 ```
 
 those are my numbers on that date, and they move every session i run, so treat
@@ -143,6 +142,74 @@ signal, not a verdict. if it ever prints something that flatters you, distrust i
 
 the caveat is printed in the output itself, every run, on purpose.
 
+## correction rate
+
+> in the repo since 2026-09-02, not yet on PyPI. `python3 transcripto.py coach` prints it.
+
+one more line under the coach footer:
+
+```
+  correction rate: 6% measured (227 of 4061 typed turns) · v1 catches ~1 in 6, so the real rate is ~26-37%
+```
+
+**correction rate = typed turns that correct the agent ÷ typed turns.** the denominator
+is the same authorship gate as every other number here (`typed` or `queued`, never
+`isMeta`, `isSidechain` or a tool result), so a tool result that happens to say "wrong"
+cannot move it. a typed turn counts as a correction when a **marker** fires in its head:
+the first 80 words after URLs and file paths are stripped, case-insensitive, whole-word:
+a leading or bare `no`, `again`, `wrong`, `not that`, `I meant`, `revert`, `undo`, `stop`,
+`instead`, plus a few measured additions. whole-word, so "against" is not "again" and
+"now" is not "no". the v0 "nudge" rule (a short turn naming the agent's last file) is gone:
+measured over 100 flagged rows it fired alone five times and was wrong five times.
+`TRANSCRIPTO_CORRECTION=v0` brings the old classifier back for comparison.
+
+it is one pure function, `is_correction(text)`, and it is a **floor**, now measured rather
+than asserted: on a 200-row labelled sample the v1 classifier has precision 0.81 and recall
+0.16 (`docs/CORRECTION-PRECISION-2026-09-03.md`), which is why the printed line carries the
+"~1 in 6" correction and a range. read it as a trend on your own history.
+`test_correction.sh` pins the rule and the gate on `fixtures-correction/`.
+
+## export-run
+
+> in the repo since 2026-09-02, not yet on PyPI.
+
+```
+transcripto export-run latest                 # the newest session on this machine
+transcripto export-run 3f9c1a2b               # a session id, or a prefix of one
+transcripto export-run path/to/session.jsonl  # a transcript file
+transcripto export-run latest --harness codex # --root / --harness as for coach
+```
+
+one run's numbers as JSON, read straight from the transcript file (no index needed).
+this is the contract other tools read (Agent Grinder's card, ZUP's board); the keys are
+frozen under `schema`, and a new key is an addition, never a rename.
+
+| key | meaning |
+|---|---|
+| `schema` | `transcripto.export-run/1` |
+| `session_id` | the harness's session id (Claude Code: the file name; Codex: `session_meta.id`; Cursor: the file name) |
+| `project` | the run's `cwd` |
+| `harness` | `claude` · `codex` · `cursor` |
+| `transcript` | absolute path of the file read |
+| `started` · `ended` | first and last record timestamp, UTC, `…Z`; `null` if the file carries none |
+| `duration_s` | `ended − started`, whole seconds |
+| `records` | every record in the file, before any gate |
+| `typed_turns` | records that pass the authorship gate: `promptSource` typed or queued, never meta, sidechain or tool result. the same count coach prints as "typed by you" |
+| `corrections` | typed turns `is_correction()` flags (see above) |
+| `correction_rate` | `corrections / typed_turns`, 3 decimals; `null` when nothing was typed |
+| `tool_calls` | every `tool_use` block the agent emitted |
+| `files_touched` | sorted set of `file_path` (or `notebook_path`) from Edit / Write / Read / MultiEdit / NotebookEdit calls |
+| `commits_in_window` | commits stamped inside `[started, ended]` in the project's git reflog; `null` when `project` is not inside a git repo |
+| `commits` | those commits as `{sha, ts, subject}`, oldest first; `null` when not a repo |
+| `proxy` | the caveat, in the JSON so it travels with the numbers |
+
+`commits_in_window` reads `.git/logs/HEAD` directly, not `git log`, because this file
+does not shell out (see privacy). the reflog is the record of what **that working tree**
+did: a commit made there in the window is in it, a commit pulled in from elsewhere is not.
+git expires the reflog after 90 days by default, so a run older than that can read 0 here
+while `git log` would still show its commits. `commit (amend)` counts; a rebase's `pick`
+lines do not. a `.git` file (a worktree) is followed to its gitdir.
+
 ## why your own gate matters here
 
 at fleet scale roughly 95% of the `type: user` records in a transcript are not
@@ -200,15 +267,15 @@ claim, so here is the grep that settles it against the single file it ships as:
 $ grep -nE '^[[:space:]]*(import|from) ' transcripto.py
 8:import sys, os, json, glob, re, sqlite3, argparse
 9:from datetime import datetime, timezone
-260:    import time
-1051:            import datetime
-1061:    from the separator), so the result is checked on disk and dropped if it is
+261:    import time
+1160:            import datetime
+1170:    from the separator), so the result is checked on disk and dropped if it is
 ```
 
 five lines, four of which are imports and all four are stdlib. `time` and
 `datetime` sit inside functions, which is why the pattern allows for indentation —
 anchor it at `^import` and you would miss two, so do not take my word for the
-anchor either. line 1061 is the pattern catching a docstring that happens to begin
+anchor either. line 1170 is the pattern catching a docstring that happens to begin
 with the word `from`; it is prose, not an import, and it is left in rather than
 tuned out, because a grep you tuned until it agreed with you proves nothing.
 
@@ -247,6 +314,7 @@ transcripto sessions   recent sessions + the first prompt YOU typed in each
 transcripto stats      what you actually work on
 transcripto cost       what ONE of your decisions costs
 transcripto coach      which of YOUR prompt habits survive (a proxy)
+transcripto export-run one run's numbers as JSON (typed turns, correction rate, commits)
 ```
 
 `ask` is the one that kills "wait, did i lose something?". it answers "what was i
@@ -307,9 +375,12 @@ just gives the file a name on your PATH.
 ./test_cost.sh         12 assertions
 ./test_small_n.sh       7 assertions
 ./test_label_bands.sh  13 assertions
+./test_correction.sh   32 assertions   (correction rate + export-run, 2026-09-02)
+./test_cursor_partial.sh 7 assertions
+./test_version.sh       1 assertion    (VERSION matches in transcripto.py and pyproject.toml)
 ```
 
-61 assertions, all green, re-run 2026-08-31.
+91 assertions, all green, re-run 2026-09-02.
 
 offline, no keys, on fixtures that inherit the real transcript shape including
 all four ways a non-human record disguises itself as `type: user`.

{transcripto-0.1.2 → transcripto-0.1.4}/README.md

@@ -11,19 +11,11 @@ your disk and never opens a socket.
 uvx transcripto coach
 ```
 
-> **check which build you got.** `trace`, `--harness cursor`, and the "run `index`
-> first" errors below all arrive in **0.1.2**. On anything older, `trace` is not a
-> command, cursor is rejected, and the index-gated commands fail with a raw sqlite
-> traceback instead of an instruction. One line settles which one you are holding:
+> **which build you got.** `uvx transcripto --version` should print **0.1.3**. If `--version`
+> is not a recognised flag at all you are on 0.1.1, which predates `trace`, Cursor support and
+> this README. `uvx --refresh transcripto` forces a fresh resolve past uv's cache.
 >
-> ```
-> uvx transcripto --version          # 0.1.2 or newer = this README is accurate
-> ```
->
-> *Read 2026-08-31: PyPI was serving 0.1.1 while this README described 0.1.2, so
-> `uvx transcripto` gave the older build. If `--version` is not even a recognised
-> flag, you have 0.1.1 — it was added in 0.1.2 precisely because there was no way
-> to tell.* The repo always matches this README and needs nothing installed:
+> The repo always matches this README and needs nothing installed:
 >
 > ```
 > git clone https://github.com/Morkeeth/transcripto && cd transcripto
@@ -63,41 +55,48 @@ the same way.
 
 ## what you get back
 
-this is a real run on one machine, pasted unedited, 2026-08-28:
+this is a real run on one machine, 2026-08-31. The numbers are unedited; the two quoted prompts are synthetic stand-ins of the same shape, because your prompts never leave your machine and neither do mine:
 
 ```
 
   YOUR PROMPT HABITS, GRADED   (offline, your machine only)
 
-  harness: claude
-  corpus : 2720 transcript(s), 381,804 records
-  kept   : 3678 prompts you actually typed (0.96% of records)
-  episodes: 1946 ranked, 910 survived (47%)
-  tiers  : commit 373 | write/edit 537 | reverted 2 | nothing durable 1034
+  - your worst looped prompt, with its witness:
+      "hmm ok lets just try again and see if it works this time, same thing as before but…"
+      NO-DURABLE-RECORD: read-only Bash only, no file change  ·  corrections: 15  ·  assistant turns: 221
+
+  + your best landed prompt, with its witness:
+      "TERMINAL 3 — parser · ~/CODE/demo Read hack.md. Fix the counter, run the suite, commit if green…"
+      COMMIT-WITNESSED: git commit  ·  corrections: 0
 
   SURVIVAL IS A PROXY: survival = a durable Write/Edit or an un-reverted git commit in-episode. A PROXY, not proof the work was correct or shipped.
 
   SURVIVES MOST  do more of these:
-     64%  (167/260)  detailed (>40 words)
-     63%  (66/104)  states-a-check-or-done-condition
-     58%  (414/708)  intent:CHANGE
-     58%  (21/36)  no-object (pronoun/vague)
-     57%  (99/175)  cites-a-file-or-path
+     65%  (71/110)  states-a-check-or-done-condition
+     64%  (178/276)  detailed (>40 words)
+     59%  (22/37)  no-object (pronoun/vague)
+     59%  (451/763)  intent:CHANGE
+     57%  (106/187)  cites-a-file-or-path
 
   SURVIVES LEAST  these tend to loop:
-     33%  (4/12)  intent:REVERT
-     39%  (411/1043)  intent:none
-     40%  (4/10)  intent:TEST
-     42%  (298/715)  terse (<8 words)
-     45%  (77/173)  intent:DESCRIBE
-
-  + your best landed prompt, with its witness:
-      "mTERMINAL 8 — Mountain of Helicon · ~/CODE/mountain-of-helicon Read ~/CODE/mountain-of-helicon. Two…"
-      COMMIT-WITNESSED: git commit  ·  corrections: 0
-
-  - your worst looped prompt, with its witness:
-      "ok, and lets see they might solve it in the future so i can go back to my beloeved routine :) Befor…"
-      NO-DURABLE-RECORD: read-only Bash only, no file change  ·  corrections: 15  ·  assistant turns: 221
+     31%  (4/13)  intent:REVERT
+     40%  (451/1129)  intent:none
+     42%  (320/765)  terse (<8 words)
+     42%  (81/192)  intent:DESCRIBE
+     45%  (5/11)  intent:TEST
+
+  harness claude  ·  2957 transcript(s), 431,085 records  ·  3969 typed by you (0.92%)
+  episodes: 2108 ranked, 992 survived (47%)
+  commit 454  ·  write/edit 538  ·  reverted 2  ·  nothing durable 1114
+
+  ─────────────────────────────────────────────────────────
+   compare yours. numbers only, nothing from your prompts:
+
+   transcripto coach · claude · 2108 episodes · 47% survived
+   states-a-check-or-done-condition    65%  (71/110)
+   intent:none                         40%  (451/1129)
+   gap                                 1.6x
+  ─────────────────────────────────────────────────────────
 ```
 
 those are my numbers on that date, and they move every session i run, so treat
@@ -125,6 +124,74 @@ signal, not a verdict. if it ever prints something that flatters you, distrust i
 
 the caveat is printed in the output itself, every run, on purpose.
 
+## correction rate
+
+> in the repo since 2026-09-02, not yet on PyPI. `python3 transcripto.py coach` prints it.
+
+one more line under the coach footer:
+
+```
+  correction rate: 6% measured (227 of 4061 typed turns) · v1 catches ~1 in 6, so the real rate is ~26-37%
+```
+
+**correction rate = typed turns that correct the agent ÷ typed turns.** the denominator
+is the same authorship gate as every other number here (`typed` or `queued`, never
+`isMeta`, `isSidechain` or a tool result), so a tool result that happens to say "wrong"
+cannot move it. a typed turn counts as a correction when a **marker** fires in its head:
+the first 80 words after URLs and file paths are stripped, case-insensitive, whole-word:
+a leading or bare `no`, `again`, `wrong`, `not that`, `I meant`, `revert`, `undo`, `stop`,
+`instead`, plus a few measured additions. whole-word, so "against" is not "again" and
+"now" is not "no". the v0 "nudge" rule (a short turn naming the agent's last file) is gone:
+measured over 100 flagged rows it fired alone five times and was wrong five times.
+`TRANSCRIPTO_CORRECTION=v0` brings the old classifier back for comparison.
+
+it is one pure function, `is_correction(text)`, and it is a **floor**, now measured rather
+than asserted: on a 200-row labelled sample the v1 classifier has precision 0.81 and recall
+0.16 (`docs/CORRECTION-PRECISION-2026-09-03.md`), which is why the printed line carries the
+"~1 in 6" correction and a range. read it as a trend on your own history.
+`test_correction.sh` pins the rule and the gate on `fixtures-correction/`.
+
+## export-run
+
+> in the repo since 2026-09-02, not yet on PyPI.
+
+```
+transcripto export-run latest                 # the newest session on this machine
+transcripto export-run 3f9c1a2b               # a session id, or a prefix of one
+transcripto export-run path/to/session.jsonl  # a transcript file
+transcripto export-run latest --harness codex # --root / --harness as for coach
+```
+
+one run's numbers as JSON, read straight from the transcript file (no index needed).
+this is the contract other tools read (Agent Grinder's card, ZUP's board); the keys are
+frozen under `schema`, and a new key is an addition, never a rename.
+
+| key | meaning |
+|---|---|
+| `schema` | `transcripto.export-run/1` |
+| `session_id` | the harness's session id (Claude Code: the file name; Codex: `session_meta.id`; Cursor: the file name) |
+| `project` | the run's `cwd` |
+| `harness` | `claude` · `codex` · `cursor` |
+| `transcript` | absolute path of the file read |
+| `started` · `ended` | first and last record timestamp, UTC, `…Z`; `null` if the file carries none |
+| `duration_s` | `ended − started`, whole seconds |
+| `records` | every record in the file, before any gate |
+| `typed_turns` | records that pass the authorship gate: `promptSource` typed or queued, never meta, sidechain or tool result. the same count coach prints as "typed by you" |
+| `corrections` | typed turns `is_correction()` flags (see above) |
+| `correction_rate` | `corrections / typed_turns`, 3 decimals; `null` when nothing was typed |
+| `tool_calls` | every `tool_use` block the agent emitted |
+| `files_touched` | sorted set of `file_path` (or `notebook_path`) from Edit / Write / Read / MultiEdit / NotebookEdit calls |
+| `commits_in_window` | commits stamped inside `[started, ended]` in the project's git reflog; `null` when `project` is not inside a git repo |
+| `commits` | those commits as `{sha, ts, subject}`, oldest first; `null` when not a repo |
+| `proxy` | the caveat, in the JSON so it travels with the numbers |
+
+`commits_in_window` reads `.git/logs/HEAD` directly, not `git log`, because this file
+does not shell out (see privacy). the reflog is the record of what **that working tree**
+did: a commit made there in the window is in it, a commit pulled in from elsewhere is not.
+git expires the reflog after 90 days by default, so a run older than that can read 0 here
+while `git log` would still show its commits. `commit (amend)` counts; a rebase's `pick`
+lines do not. a `.git` file (a worktree) is followed to its gitdir.
+
 ## why your own gate matters here
 
 at fleet scale roughly 95% of the `type: user` records in a transcript are not
@@ -182,15 +249,15 @@ claim, so here is the grep that settles it against the single file it ships as:
 $ grep -nE '^[[:space:]]*(import|from) ' transcripto.py
 8:import sys, os, json, glob, re, sqlite3, argparse
 9:from datetime import datetime, timezone
-260:    import time
-1051:            import datetime
-1061:    from the separator), so the result is checked on disk and dropped if it is
+261:    import time
+1160:            import datetime
+1170:    from the separator), so the result is checked on disk and dropped if it is
 ```
 
 five lines, four of which are imports and all four are stdlib. `time` and
 `datetime` sit inside functions, which is why the pattern allows for indentation —
 anchor it at `^import` and you would miss two, so do not take my word for the
-anchor either. line 1061 is the pattern catching a docstring that happens to begin
+anchor either. line 1170 is the pattern catching a docstring that happens to begin
 with the word `from`; it is prose, not an import, and it is left in rather than
 tuned out, because a grep you tuned until it agreed with you proves nothing.
 
@@ -229,6 +296,7 @@ transcripto sessions   recent sessions + the first prompt YOU typed in each
 transcripto stats      what you actually work on
 transcripto cost       what ONE of your decisions costs
 transcripto coach      which of YOUR prompt habits survive (a proxy)
+transcripto export-run one run's numbers as JSON (typed turns, correction rate, commits)
 ```
 
 `ask` is the one that kills "wait, did i lose something?". it answers "what was i
@@ -289,9 +357,12 @@ just gives the file a name on your PATH.
 ./test_cost.sh         12 assertions
 ./test_small_n.sh       7 assertions
 ./test_label_bands.sh  13 assertions
+./test_correction.sh   32 assertions   (correction rate + export-run, 2026-09-02)
+./test_cursor_partial.sh 7 assertions
+./test_version.sh       1 assertion    (VERSION matches in transcripto.py and pyproject.toml)
 ```
 
-61 assertions, all green, re-run 2026-08-31.
+91 assertions, all green, re-run 2026-09-02.
 
 offline, no keys, on fixtures that inherit the real transcript shape including
 all four ways a non-human record disguises itself as `type: user`.

{transcripto-0.1.2 → transcripto-0.1.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "transcripto"
-version = "0.1.2"
+version = "0.1.4"
 description = "Search everything your coding agents ever did, grade your own prompts, and price your decisions. Local, stdlib-only, your data never leaves the machine."
 readme = "README.md"
 requires-python = ">=3.9"