transcript-viewer 0.14.0__tar.gz → 0.14.1__tar.gz

{transcript_viewer-0.14.0 → transcript_viewer-0.14.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: transcript-viewer
-Version: 0.14.0
+Version: 0.14.1
 Summary: Browse agent transcripts in a local, dependency-free web viewer.
 License: MIT
 Requires-Python: >=3.12
@@ -179,17 +179,16 @@ If that directory is still there, the first run moves it to
 `~/.transcript-viewer` — index, annotations and stored keys together — and says
 so. Nothing is left behind and nothing is copied twice.
 
-A run that delegated shows what it farmed out, above its steps, as a **list**
-or a **timeline**. The list leads because the common question is what was asked
-and what came back, and the median subagent here is two steps — a bar for which
-says almost nothing. It carries the task, the kind, the steps, how long it took
-and the tools it reached for, sorted however you ask.
-
-The timeline is for when the question is *when*, and alongside what. A row is
-shared by everything that did not overlap, so a second row exists only because
-two things ran at once: thirty subagents in one session pack into eight rows,
-and a session of fifteen packs into one, which is the honest picture of a run
-that never did two things at a time. Either way a subagent is called what it was asked to
+A run that delegated shows what it farmed out, above its steps, as a
+**timeline** or a **list**. The timeline leads: a row is shared by everything
+that did not overlap, so a second row exists only because two things ran at
+once. Thirty subagents in one session pack into eight rows, and a session of
+fifteen packs into one, which is the honest picture of a run that never did two
+things at a time.
+
+The list is one chip away, and carries what a chart cannot: the task, the kind,
+the steps, how long it took and the tools it reached for, sorted however you
+ask. Whichever you pick is remembered. Either way a subagent is called what it was asked to
 do — "Review backend for bugs and DRY" rather than "general-purpose" — wherever
 that was written down, which is 50 of the 53 Claude Code subagents here; the
 kind is the fallback, and reads as a handle rather than as prose so the

{transcript_viewer-0.14.0 → transcript_viewer-0.14.1}/README.md

@@ -166,17 +166,16 @@ If that directory is still there, the first run moves it to
 `~/.transcript-viewer` — index, annotations and stored keys together — and says
 so. Nothing is left behind and nothing is copied twice.
 
-A run that delegated shows what it farmed out, above its steps, as a **list**
-or a **timeline**. The list leads because the common question is what was asked
-and what came back, and the median subagent here is two steps — a bar for which
-says almost nothing. It carries the task, the kind, the steps, how long it took
-and the tools it reached for, sorted however you ask.
-
-The timeline is for when the question is *when*, and alongside what. A row is
-shared by everything that did not overlap, so a second row exists only because
-two things ran at once: thirty subagents in one session pack into eight rows,
-and a session of fifteen packs into one, which is the honest picture of a run
-that never did two things at a time. Either way a subagent is called what it was asked to
+A run that delegated shows what it farmed out, above its steps, as a
+**timeline** or a **list**. The timeline leads: a row is shared by everything
+that did not overlap, so a second row exists only because two things ran at
+once. Thirty subagents in one session pack into eight rows, and a session of
+fifteen packs into one, which is the honest picture of a run that never did two
+things at a time.
+
+The list is one chip away, and carries what a chart cannot: the task, the kind,
+the steps, how long it took and the tools it reached for, sorted however you
+ask. Whichever you pick is remembered. Either way a subagent is called what it was asked to
 do — "Review backend for bugs and DRY" rather than "general-purpose" — wherever
 that was written down, which is 50 of the 53 Claude Code subagents here; the
 kind is the fallback, and reads as a handle rather than as prose so the

{transcript_viewer-0.14.0 → transcript_viewer-0.14.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "transcript-viewer"
-version = "0.14.0"
+version = "0.14.1"
 description = "Browse agent transcripts in a local, dependency-free web viewer."
 readme = "README.md"
 requires-python = ">=3.12"

{transcript_viewer-0.14.0 → transcript_viewer-0.14.1}/src/transcript_viewer/page.html

@@ -2686,13 +2686,13 @@ function axisMarks(lo, hi) {
 
 let LANES = [];
 
-/* Which of the two views the box is showing. A list by default: the common
-   question is what was farmed out and what came back, and the median subagent
-   here is two steps — a bar for which says almost nothing. The timeline is for
-   when the question is when, and alongside what. */
+/* Which of the two views the box is showing, remembered between runs. The
+   timeline by default: packed, its rows carry the shape of the run and the
+   parallelism in it at a glance, which is what the box is above the transcript
+   for. The list is where the names and numbers are, one chip away. */
 let LANEVIEW = (() => {
-  try { return localStorage.getItem("transcript-viewer.delegation") || "list"; }
-  catch (e) { return "list"; }
+  try { return localStorage.getItem("transcript-viewer.delegation") || "time"; }
+  catch (e) { return "time"; }
 })();
 
 function setLaneView(v) {

{transcript_viewer-0.14.0 → transcript_viewer-0.14.1}/tests/page.test.js

@@ -2338,13 +2338,32 @@ test("a second row exists only because two things ran at once", () => {
   assert.deepStrictEqual(out.on, [0, 1], "the overlap is what made the row");
 });
 
-test("the list is what the box shows first", () => {
+test("the timeline is what the box shows first", () => {
+  // Nothing stored: the timeline, whose packed rows carry the shape of the run.
+  const html = run(`
+    localStorage.getItem = () => null;
+    LANEVIEW = localStorage.getItem("transcript-viewer.delegation") || "time";
+    return drawLanes(${JSON.stringify(TWO_AT_ONCE)});
+  `);
+  assert.match(html, /class="track"/, "the chart is drawn");
+  assert.ok(!/class="lanelist"/.test(html));
+});
+
+test("the list is one chip away, and shows what a chart cannot", () => {
   const html = run(`LANEVIEW="list"; return drawLanes(${JSON.stringify(TWO_AT_ONCE)})`);
   assert.match(html, /class="lanelist"/);
   assert.match(html, /what it was asked to do/, "the task leads");
   assert.ok(!/class="track"/.test(html), "and no chart is drawn");
 });
 
+test("what was stored is what is shown", () => {
+  const stored = run(`
+    localStorage.getItem = (k) => (k === "transcript-viewer.delegation" ? "list" : null);
+    return localStorage.getItem("transcript-viewer.delegation") || "time";
+  `);
+  assert.strictEqual(stored, "list", "a choice made once is kept");
+});
+
 test("the list names each one and says what it cost", () => {
   const html = run(`LANEVIEW="list"; return drawLanes(${JSON.stringify(TWO_AT_ONCE)})`);
   assert.match(html, /find the theme/, "the task, where there was one");

{transcript_viewer-0.14.0 → transcript_viewer-0.14.1}/uv.lock

@@ -388,7 +388,7 @@ wheels = [
 
 [[package]]
 name = "transcript-viewer"
-version = "0.14.0"
+version = "0.14.1"
 source = { editable = "." }
 dependencies = [
     { name = "atif-make" },