transcripto 0.1.1__tar.gz → 0.1.3__tar.gz

{transcripto-0.1.1/transcripto.egg-info → transcripto-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: transcripto
-Version: 0.1.1
+Version: 0.1.3
 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,43 +29,92 @@ your disk and never opens a socket.
 uvx transcripto coach
 ```
 
-## what you get back
+> **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.
+>
+> The repo always matches this README and needs nothing installed:
+>
+> ```
+> git clone https://github.com/Morkeeth/transcripto && cd transcripto
+> python3 transcripto.py coach
+> ```
 
-this is a real run on one machine, pasted unedited, 2026-08-28:
+## three harnesses, one instrument
 
+```
+transcripto coach                     # Claude Code, ~/.claude/projects
+transcripto coach --harness codex     # Codex, ~/.codex
+transcripto coach --harness cursor    # Cursor, ~/.cursor/projects/*/agent-transcripts
 ```
 
-  YOUR PROMPT HABITS, GRADED   (offline, your machine only)
+**Authorship is not the same gate in all three, and the tool says so rather than pooling them.**
+Claude Code stamps `promptSource: typed`, which is the measured-reliable signal: about 95% of raw
+`type: user` records are not the operator at all. Cursor has no such field. Its one honest
+equivalent is the `<user_query>` wrapper it puts around a submitted prompt, which injected and
+tool-result records do not carry. That is a weaker signal and it is labelled weaker.
 
-  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
+## `trace` — what actually happened after you asked
 
-  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.
+`ask` shows what you typed. `find` shows what a file went through. Neither answers the
+question that matters after the fact: **you asked for X, did anything durable happen?**
 
-  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
+```
+transcripto trace "the gate"
+```
 
-  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
+It walks each of your matching prompts forward inside its own session and lists the writes
+and edits that followed, stopping at your next prompt so one turn cannot claim the next
+turn's work. Green dot = something durable landed. Red = nothing was touched.
 
-  + 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
+**Honest limit:** a write following a prompt in the same session is CO-OCCURRENCE, not proof
+the write was caused by that prompt or that it was correct. Same proxy `coach` uses, labelled
+the same way.
+
+## what you get back
+
+this is a real run on one machine, pasted unedited, 2026-08-31:
+
+```
+
+  YOUR PROMPT HABITS, GRADED   (offline, your machine only)
 
   - 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
+
+  + 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
+
+  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:
+     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:
+     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
@@ -73,9 +122,13 @@ them as a snapshot rather than a constant. yours will be different, which is the
 whole point. the last two lines are the ones that sting: it hands you back your
 own best and worst prompt, verbatim, with the receipt for why it scored each one.
 
-on that machine, prompts that wrote down what done looks like survived **63% of
-the time (66 of 104)**. prompts with no stated intent survived **39% (411 of
-1043)**. i had spent a year blaming the model.
+on that machine, on that date, prompts that wrote down what done looks like
+survived **63% of the time (66 of 104)**. prompts with no stated intent survived
+**39% (411 of 1043)**. i had spent a year blaming the model.
+
+one day later, 2026-08-29, the same command on the same machine read 63% (67 of
+107) and 40% (424 of 1072) over 2,874 transcripts. the percentages held and the
+denominators moved, which is what a snapshot is supposed to do.
 
 ## the proxy caveat, which travels with every number
 
@@ -127,8 +180,10 @@ read these before you quote a number at anyone.
 - **one operator's corpus.** every figure in this README comes from one machine.
   it is an existence proof that the measurement runs, not a finding about how
   people prompt. run it on yours and you get yours.
-- **two harnesses today: Claude Code and Codex.** nothing else is supported.
-  cursor, aider, and the rest are not read.
+- **three harnesses today: Claude Code, Codex, Cursor.** nothing else is supported.
+  aider and the rest are not read. and the three are not equal: Claude Code has a
+  measured-reliable authorship field, Cursor has only the `<user_query>` wrapper,
+  which is weaker and is labelled weaker wherever it is used.
 - **the habit labels are heuristics.** "states-a-check-or-done-condition" is a
   pattern match over your text, not comprehension. it will misfile some prompts.
 - **correlation, not instruction.** detailed prompts surviving more often does not
@@ -144,25 +199,50 @@ 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
-225:    import time
+260:    import time
+1051:            import datetime
+1061:    from the separator), so the result is checked on disk and dropped if it is
 ```
 
-that is the whole import list, three lines. `time` sits inside the `watch` loop,
-which is why the pattern allows for indentation. anchor it at `^import` and you
-would miss one, so do not take my word for the anchor either.
+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
+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.
+
+what the list does NOT contain is the actual claim: no `socket`, no `urllib`, no
+`requests`, no `http.client`, no `subprocess`. that one is checkable too, and the
+right answer is no output at all:
+
+```
+$ grep -nE '\b(socket|urllib|requests|http\.client|subprocess)\b' transcripto.py
+$
+```
 
-your transcripts stay in `~/.claude` and `~/.codex`. the index it builds stays in
-`~/.trace`.
+your transcripts stay in `~/.claude`, `~/.codex` and `~/.cursor`. the index it
+builds stays in `~/.trace`.
 
 ## the rest of it
 
+`coach` and `cost` read your transcript files directly and need nothing set up.
+**the other six read a local index, so run this once first:**
+
+```
+transcripto index      # a few minutes on a large corpus, incremental after that
+```
+
+on a 2,874-file corpus that was 164 seconds, measured 2026-08-29. if you skip it,
+the six say so and exit 2.
+
 ```
 transcripto index      build / refresh (incremental)
 transcripto watch      live, new sessions get picked up as your agents work
 transcripto ask        YOUR OWN messages about a topic, newest first + a rollup
 transcripto search     full-text across everything (you + agents + tool logs)
 transcripto find       every session that wrote / edited / read a file
-transcripto sessions   recent sessions + their opening ask
+transcripto trace      what durably happened after each prompt you typed (0.1.2+)
+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)
@@ -172,11 +252,17 @@ transcripto coach      which of YOUR prompt habits survive (a proxy)
 thinking about X across ALL my sessions", in your own words only.
 
 ```
-$ transcripto find USER-JOURNEY.md
-2026-08-20  WROTE  ~/CODE/mountain-of-helicon-main/USER-JOURNEY.md
+$ transcripto find USER-JOURNEY.md          # run 2026-08-29
+USER-JOURNEY.md  4 touches across sessions (3 were writes/edits)
+
+2026-08-20  WROTE  ~/CODE/mountain-of-helicon-main/USER-JOURNEY.md            abd9e871
+2026-08-21  WROTE  ~/…/Obsidian LIFE/00 Dashboard/suite-user-journey.md       0f845ede
+2026-08-27  read   ~/CODE/hack-fleet-ata/docs/USER-JOURNEY.md                 cddfde29
+2026-08-27  WROTE  ~/CODE/hack-fleet-ata/docs/USER-JOURNEY.md                 cddfde29
 ```
 
-the file you lost, found across every session you ever ran, one line.
+the file you lost, found across every session you ever ran, with the session id
+that touched it. `find` needs `transcripto index` first.
 
 ## Codex
 
@@ -215,11 +301,15 @@ just gives the file a name on your PATH.
 ## tests
 
 ```
-./test_coach.sh    14 assertions
-./test_codex.sh    14 assertions
-./test_cost.sh     12 assertions
+./test_coach.sh        15 assertions
+./test_codex.sh        14 assertions
+./test_cost.sh         12 assertions
+./test_small_n.sh       7 assertions
+./test_label_bands.sh  13 assertions
 ```
 
+61 assertions, all green, re-run 2026-08-31.
+
 offline, no keys, on fixtures that inherit the real transcript shape including
 all four ways a non-human record disguises itself as `type: user`.
 
@@ -227,6 +317,15 @@ the load-bearing one in `test_coach.sh` is `REVERTED IS NOT SURVIVED`: a commit
 that got `reset --hard` in the same session left no durable record. flip that one
 line and the suite goes red, which is the point. a generous proxy is a broken one.
 
+`test_label_bands.sh` is the other one, and it exists because 0.1.1 shipped the
+defect it pins. `SURVIVES MOST` took the top five habits and `SURVIVES LEAST` took
+the bottom five, which overlap whenever you have fewer than ten rankable habits —
+so a new user, who necessarily has few, read the same habit at the same percentage
+under both "do more of these" and "these tend to loop". on a 3-habit corpus 0.1.1
+reprinted all three, all at 65% (22/34). the suite is red on the published 0.1.1
+file and green on this one, and its `wide` band asserts the fix leaves a large
+corpus byte-identical.
+
 ## why though
 
 your agent history is proof. every "yeah it's done" has a real trace sitting

{transcripto-0.1.1 → transcripto-0.1.3}/README.md

@@ -11,43 +11,92 @@ your disk and never opens a socket.
 uvx transcripto coach
 ```
 
-## what you get back
+> **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.
+>
+> The repo always matches this README and needs nothing installed:
+>
+> ```
+> git clone https://github.com/Morkeeth/transcripto && cd transcripto
+> python3 transcripto.py coach
+> ```
+
+## three harnesses, one instrument
+
+```
+transcripto coach                     # Claude Code, ~/.claude/projects
+transcripto coach --harness codex     # Codex, ~/.codex
+transcripto coach --harness cursor    # Cursor, ~/.cursor/projects/*/agent-transcripts
+```
+
+**Authorship is not the same gate in all three, and the tool says so rather than pooling them.**
+Claude Code stamps `promptSource: typed`, which is the measured-reliable signal: about 95% of raw
+`type: user` records are not the operator at all. Cursor has no such field. Its one honest
+equivalent is the `<user_query>` wrapper it puts around a submitted prompt, which injected and
+tool-result records do not carry. That is a weaker signal and it is labelled weaker.
 
-this is a real run on one machine, pasted unedited, 2026-08-28:
+## `trace` — what actually happened after you asked
 
+`ask` shows what you typed. `find` shows what a file went through. Neither answers the
+question that matters after the fact: **you asked for X, did anything durable happen?**
+
+```
+transcripto trace "the gate"
 ```
 
-  YOUR PROMPT HABITS, GRADED   (offline, your machine only)
+It walks each of your matching prompts forward inside its own session and lists the writes
+and edits that followed, stopping at your next prompt so one turn cannot claim the next
+turn's work. Green dot = something durable landed. Red = nothing was touched.
 
-  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
+**Honest limit:** a write following a prompt in the same session is CO-OCCURRENCE, not proof
+the write was caused by that prompt or that it was correct. Same proxy `coach` uses, labelled
+the same way.
 
-  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.
+## what you get back
 
-  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
+this is a real run on one machine, pasted unedited, 2026-08-31:
 
-  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 PROMPT HABITS, GRADED   (offline, your machine only)
 
   - 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
+
+  + 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
+
+  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:
+     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:
+     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
@@ -55,9 +104,13 @@ them as a snapshot rather than a constant. yours will be different, which is the
 whole point. the last two lines are the ones that sting: it hands you back your
 own best and worst prompt, verbatim, with the receipt for why it scored each one.
 
-on that machine, prompts that wrote down what done looks like survived **63% of
-the time (66 of 104)**. prompts with no stated intent survived **39% (411 of
-1043)**. i had spent a year blaming the model.
+on that machine, on that date, prompts that wrote down what done looks like
+survived **63% of the time (66 of 104)**. prompts with no stated intent survived
+**39% (411 of 1043)**. i had spent a year blaming the model.
+
+one day later, 2026-08-29, the same command on the same machine read 63% (67 of
+107) and 40% (424 of 1072) over 2,874 transcripts. the percentages held and the
+denominators moved, which is what a snapshot is supposed to do.
 
 ## the proxy caveat, which travels with every number
 
@@ -109,8 +162,10 @@ read these before you quote a number at anyone.
 - **one operator's corpus.** every figure in this README comes from one machine.
   it is an existence proof that the measurement runs, not a finding about how
   people prompt. run it on yours and you get yours.
-- **two harnesses today: Claude Code and Codex.** nothing else is supported.
-  cursor, aider, and the rest are not read.
+- **three harnesses today: Claude Code, Codex, Cursor.** nothing else is supported.
+  aider and the rest are not read. and the three are not equal: Claude Code has a
+  measured-reliable authorship field, Cursor has only the `<user_query>` wrapper,
+  which is weaker and is labelled weaker wherever it is used.
 - **the habit labels are heuristics.** "states-a-check-or-done-condition" is a
   pattern match over your text, not comprehension. it will misfile some prompts.
 - **correlation, not instruction.** detailed prompts surviving more often does not
@@ -126,25 +181,50 @@ 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
-225:    import time
+260:    import time
+1051:            import datetime
+1061:    from the separator), so the result is checked on disk and dropped if it is
 ```
 
-that is the whole import list, three lines. `time` sits inside the `watch` loop,
-which is why the pattern allows for indentation. anchor it at `^import` and you
-would miss one, so do not take my word for the anchor either.
+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
+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.
+
+what the list does NOT contain is the actual claim: no `socket`, no `urllib`, no
+`requests`, no `http.client`, no `subprocess`. that one is checkable too, and the
+right answer is no output at all:
+
+```
+$ grep -nE '\b(socket|urllib|requests|http\.client|subprocess)\b' transcripto.py
+$
+```
 
-your transcripts stay in `~/.claude` and `~/.codex`. the index it builds stays in
-`~/.trace`.
+your transcripts stay in `~/.claude`, `~/.codex` and `~/.cursor`. the index it
+builds stays in `~/.trace`.
 
 ## the rest of it
 
+`coach` and `cost` read your transcript files directly and need nothing set up.
+**the other six read a local index, so run this once first:**
+
+```
+transcripto index      # a few minutes on a large corpus, incremental after that
+```
+
+on a 2,874-file corpus that was 164 seconds, measured 2026-08-29. if you skip it,
+the six say so and exit 2.
+
 ```
 transcripto index      build / refresh (incremental)
 transcripto watch      live, new sessions get picked up as your agents work
 transcripto ask        YOUR OWN messages about a topic, newest first + a rollup
 transcripto search     full-text across everything (you + agents + tool logs)
 transcripto find       every session that wrote / edited / read a file
-transcripto sessions   recent sessions + their opening ask
+transcripto trace      what durably happened after each prompt you typed (0.1.2+)
+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)
@@ -154,11 +234,17 @@ transcripto coach      which of YOUR prompt habits survive (a proxy)
 thinking about X across ALL my sessions", in your own words only.
 
 ```
-$ transcripto find USER-JOURNEY.md
-2026-08-20  WROTE  ~/CODE/mountain-of-helicon-main/USER-JOURNEY.md
+$ transcripto find USER-JOURNEY.md          # run 2026-08-29
+USER-JOURNEY.md  4 touches across sessions (3 were writes/edits)
+
+2026-08-20  WROTE  ~/CODE/mountain-of-helicon-main/USER-JOURNEY.md            abd9e871
+2026-08-21  WROTE  ~/…/Obsidian LIFE/00 Dashboard/suite-user-journey.md       0f845ede
+2026-08-27  read   ~/CODE/hack-fleet-ata/docs/USER-JOURNEY.md                 cddfde29
+2026-08-27  WROTE  ~/CODE/hack-fleet-ata/docs/USER-JOURNEY.md                 cddfde29
 ```
 
-the file you lost, found across every session you ever ran, one line.
+the file you lost, found across every session you ever ran, with the session id
+that touched it. `find` needs `transcripto index` first.
 
 ## Codex
 
@@ -197,11 +283,15 @@ just gives the file a name on your PATH.
 ## tests
 
 ```
-./test_coach.sh    14 assertions
-./test_codex.sh    14 assertions
-./test_cost.sh     12 assertions
+./test_coach.sh        15 assertions
+./test_codex.sh        14 assertions
+./test_cost.sh         12 assertions
+./test_small_n.sh       7 assertions
+./test_label_bands.sh  13 assertions
 ```
 
+61 assertions, all green, re-run 2026-08-31.
+
 offline, no keys, on fixtures that inherit the real transcript shape including
 all four ways a non-human record disguises itself as `type: user`.
 
@@ -209,6 +299,15 @@ the load-bearing one in `test_coach.sh` is `REVERTED IS NOT SURVIVED`: a commit
 that got `reset --hard` in the same session left no durable record. flip that one
 line and the suite goes red, which is the point. a generous proxy is a broken one.
 
+`test_label_bands.sh` is the other one, and it exists because 0.1.1 shipped the
+defect it pins. `SURVIVES MOST` took the top five habits and `SURVIVES LEAST` took
+the bottom five, which overlap whenever you have fewer than ten rankable habits —
+so a new user, who necessarily has few, read the same habit at the same percentage
+under both "do more of these" and "these tend to loop". on a 3-habit corpus 0.1.1
+reprinted all three, all at 65% (22/34). the suite is red on the published 0.1.1
+file and green on this one, and its `wide` band asserts the fix leaves a large
+corpus byte-identical.
+
 ## why though
 
 your agent history is proof. every "yeah it's done" has a real trace sitting

{transcripto-0.1.1 → transcripto-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "transcripto"
-version = "0.1.1"
+version = "0.1.3"
 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"