claude-code-log 1.6.0__tar.gz → 1.7.0__tar.gz

claude_code_log-1.7.0/.github/workflows/release.yml

@@ -0,0 +1,169 @@
+name: Release
+
+# Tag → build + wait for CI → (a maintainer approves) → publish to PyPI →
+# GitHub Release.
+# Adapted from foldyard's release workflow. `just release-prep` makes the
+# commit and tag; `just release-push` pushes them, which starts this.
+#
+# The approval is the `pypi` environment's required reviewers (repo Settings →
+# Environments → pypi): the publish job waits until any one of them approves
+# the run, so a pushed tag on its own publishes nothing. The approval is only
+# requested once CI on the release commit has passed (the `ci` job).
+#
+# Trusted publishing: PyPI trusts THIS workflow in THIS repo (PyPI project
+# settings → Publishing → GitHub publisher: owner daaain, repo claude-code-log,
+# workflow release.yml, environment pypi). No API token is stored anywhere;
+# `uv publish` exchanges the job's OIDC token for a short-lived upload token.
+# Build and publish are separate jobs so the publish job holds the id-token
+# permission and nothing else, and never runs project code.
+on:
+  push:
+    # Tags are bare versions (1.6.0, not v1.6.0), as every release so far.
+    tags: ["[0-9]+.[0-9]+.[0-9]+"]
+
+# Least privilege by default; the two jobs that need more (publish: id-token,
+# github-release: contents write) say so themselves and run no project code.
+permissions:
+  contents: read
+
+jobs:
+  # `just release-push` pushes main and the tag together, so CI (ci.yml) and
+  # this workflow start side by side on the same commit. Rather than re-run the
+  # whole matrix, wait for THAT run: publish needs this job, so reviewers are
+  # only asked to approve once the release commit's CI is green, and a red run
+  # fails the release before anyone is asked.
+  ci:
+    runs-on: ubuntu-latest
+    timeout-minutes: 90
+    permissions:
+      actions: read
+      contents: read
+    steps:
+      # A tag cut on a branch (or a commit squash-merged away) would release
+      # code main never had. CI only runs on pushes to main, so the wait below
+      # would refuse it too — but slowly, and only while ci.yml's trigger stays
+      # main-only. This says so directly. Tag rulesets can't express it: they
+      # govern who may push a tag, not which commit it names.
+      - name: The tagged commit must be on main
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          set -euo pipefail
+          # Comparing main...SHA: `identical` or `behind` means main contains it.
+          status="$(gh api "repos/$GITHUB_REPOSITORY/compare/main...$GITHUB_SHA" --jq .status)"
+          case "$status" in
+            identical|behind) echo "✓ $GITHUB_SHA is on main" ;;
+            *) echo "✗ tag $GITHUB_REF_NAME names $GITHUB_SHA, which is not on main ($status)"
+               exit 1 ;;
+          esac
+      - name: Wait for CI on the tagged commit to pass
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          set -euo pipefail
+          find_run() {
+            gh run list --repo "$GITHUB_REPOSITORY" --workflow ci.yml --commit "$GITHUB_SHA" \
+              --event push --limit 1 --json databaseId --jq '.[0].databaseId // empty'
+          }
+          # The CI run can register a moment after this one does.
+          for _ in $(seq 30); do
+            run_id="$(find_run)"
+            [ -n "$run_id" ] && break
+            sleep 10
+          done
+          if [ -z "${run_id:-}" ]; then
+            echo "✗ no CI run for $GITHUB_SHA — release a commit that was pushed to main"
+            exit 1
+          fi
+          echo "Waiting on CI run $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$run_id"
+          gh run watch "$run_id" --repo "$GITHUB_REPOSITORY" --exit-status --interval 30 > /dev/null \
+            || { echo "✗ CI failed on $GITHUB_SHA — fix it and release the next version"; exit 1; }
+          echo "✓ CI passed"
+
+  build:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@v8.2.0
+      # The same number is written in four places: the tag, pyproject.toml,
+      # uv.lock (it records the project's own version) and CHANGELOG.md.
+      # Failing here costs a re-tag; failing after publish costs the version
+      # number forever, since PyPI never lets one be reused.
+      - name: Tag, pyproject, uv.lock and CHANGELOG must agree
+        run: |
+          set -euo pipefail
+          tag="$GITHUB_REF_NAME"
+          version="$(uv version --short)"
+          if [ "$tag" != "$version" ]; then
+            echo "✗ tag $tag does not match [project].version = $version — bump pyproject first"
+            exit 1
+          fi
+          locked="$(awk '/^name = "claude-code-log"$/{getline; print}' uv.lock | sed -n 's/^version = "\(.*\)"$/\1/p')"
+          if [ "$locked" != "$version" ]; then
+            echo "✗ uv.lock records claude-code-log $locked, pyproject says $version — run \`uv lock\`"
+            exit 1
+          fi
+      - run: uv build
+      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+      # The GitHub Release's notes: this version's CHANGELOG section, extracted
+      # HERE (the job that already runs project code, read-only) so the job
+      # holding contents:write runs none. A missing section fails the run.
+      # Its own artifact, because `uv publish` uploads everything in dist/.
+      - name: Release notes from CHANGELOG.md
+        run: |
+          set -euo pipefail
+          mkdir notes
+          python3 scripts/release_notes.py "$GITHUB_REF_NAME" > notes/notes.md
+      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        with:
+          name: notes
+          path: notes/
+          if-no-files-found: error
+
+  publish:
+    needs: [ci, build]
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: astral-sh/setup-uv@v8.2.0
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
+        with:
+          name: dist
+          path: dist/
+      - run: uv publish
+
+  # After PyPI took it, never before: a GitHub Release for a version PyPI
+  # refused would advertise one nobody can install. The wheel and sdist ride
+  # along, byte-identical to what PyPI has.
+  github-release:
+    needs: publish
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
+        with:
+          name: dist
+          path: dist/
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
+        with:
+          name: notes
+          path: notes/
+      - name: Create the GitHub Release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          set -euo pipefail
+          gh release create "$GITHUB_REF_NAME" --repo "$GITHUB_REPOSITORY" --verify-tag \
+            --title "Release $GITHUB_REF_NAME" --notes-file notes/notes.md dist/*

{claude_code_log-1.6.0 → claude_code_log-1.7.0}/CHANGELOG.md

@@ -6,6 +6,28 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 
+## [1.7.0] - 2026-10-05
+
+### Changed
+
+- **(Claude) Upgrade wenmode to 0.15.2 and bump to 1.7.0 (#340)**
+- **Release to PyPI from a tag-driven, maintainer-approved workflow (#341)**
+- **(Claude) Show the logical-parent arrow on a /compact boundary's uuid line (#338)**
+- **(Claude) Drop the host icon before a tool_result title that has its own (#337)**
+- **Keep a Markdown message's body when its title is empty (#336)**
+- **fix(search): report an unreadable cache as such, not as a missing FTS5 (#334)**
+- **Continue the rewind branch across a /compact boundary (#331)**
+- **Run the fail-fast just ci steps before the test suite**
+- **Switch the Markdown engine from mistune to wenmode (#329)**
+- **Resolve commit SHAs from one rev-list per repository (#330)**
+- **Render peer agent messages as teammate cards instead of steering (#309) (#328)**
+- **Apply the cache's write pragmas to every writing connection (#326)**
+- **Link teammate subagent transcripts spawned by the Agent tool (#316)**
+- **Re-parse cached entries when the shape of what we cache changes (#320) (#322)**
+- **Make watch ticks cheap (#321)**
+- **Update some README bits**
+
+
 ## [1.6.0] - 2026-08-31
 
 ### Changed

{claude_code_log-1.6.0 → claude_code_log-1.7.0}/CLAUDE.md

@@ -16,7 +16,7 @@ This tool processes Claude Code transcript files (stored as JSONL) and generates
 - **Runtime Message Filtering**: JavaScript-powered filtering to show/hide message types
 - **Interactive Timeline**: vis-timeline visualization with click-to-scroll navigation
 - **Date Range Filtering**: Filter messages using natural language (e.g., "today", "yesterday")
-- **Markdown Rendering**: Server-side markdown with syntax highlighting using mistune
+- **Markdown Rendering**: Server-side markdown with syntax highlighting using wenmode
 
 ## Usage
 

{claude_code_log-1.6.0 → claude_code_log-1.7.0}/CONTRIBUTING.md

@@ -64,7 +64,7 @@ The project uses:
 - Textual for Terminal User Interface
 - Pydantic for data modeling and validation
 - Jinja2 for HTML template rendering
-- mistune for Markdown rendering
+- wenmode for Markdown rendering
 - dateparser for natural language date parsing
 
 ### Dependency Management
@@ -171,14 +171,20 @@ uv run pytest test/test_snapshot_html.py -n0
 # all pass → the committed .ambr matches the render (not a raced file)
 ```
 
-When you do intend to regenerate, run `--snapshot-update` serially; a purely
-additive result (`+N/-0`, e.g. "8 snapshots passed. 1 snapshot generated.")
-is the healthy signature:
+When you do intend to regenerate, use the recipe — it purges stale
+bytecode, regenerates serially, and then re-runs read-only to prove the
+file it just wrote is what the code renders:
 
 ```bash
-uv run pytest test/test_snapshot_html.py -n0 --snapshot-update
+just update-snapshot
 ```
 
+A purely additive result (`+N/-0`, e.g. "8 snapshots passed. 1 snapshot
+generated.") is the healthy signature. The recipe exists because doing
+only part of this by hand is what produced both incidents above; reach
+for a bare `pytest --snapshot-update` only if you have a reason to, and
+keep the `-n0`.
+
 When snapshot tests fail:
 1. Review the diff to verify changes are intentional
 2. If intentional, run `--snapshot-update` (serially) to accept new output
@@ -477,29 +483,67 @@ The cache automatically rebuilds when source files change or cache schema versio
 
 ## Release Process
 
-The project uses automated releases with semantic versioning.
+Releases are tag-driven: pushing a version tag runs
+[`.github/workflows/release.yml`](.github/workflows/release.yml), which
+publishes to PyPI only after a maintainer approves it.
 
-### Quick Release
+### Cutting a release
 
 ```bash
-# Bump version and create release (patch/minor/major)
-just release-prep patch    # Bug fixes
-just release-prep minor    # New features
-just release-prep major    # Breaking changes
-
-# Or specify exact version
-just release-prep 0.4.3
+# On main, with a clean tree: bump version, update uv.lock and CHANGELOG.md,
+# commit and tag — all local (patch/minor/major, or an exact version)
+just release-prep minor
 
-# Preview what would be released
+# Check the notes the GitHub Release will carry, and the commit
 just release-preview
+git show --stat HEAD
 
-# Push to PyPI and create GitHub release
+# Push main and the tag together (--atomic), which starts the workflow
 just release-push
 ```
 
-### GitHub Release Only
-
-```bash
-just github-release          # For latest tag
-just github-release 0.4.2    # For specific version
-```
+Until the push, `git tag -d X.Y.Z && git reset --hard HEAD~1` undoes it.
+
+### What the workflow does
+
+1. **ci** — refuses a tag whose commit isn't on `main`, then waits for the CI
+   run (`ci.yml`) that the same push started on the release commit, and fails
+   the release if it fails. Nothing is re-run.
+2. **build** — in parallel, checks that the tag, `[project].version`,
+   `uv.lock`'s own `claude-code-log` entry and a `## [X.Y.Z]` CHANGELOG
+   section all agree, then runs `uv build` and extracts the release notes
+   (`scripts/release_notes.py`).
+3. **publish** — once both pass, waits in the `pypi` environment for a
+   required reviewer to **approve the deployment** in the run's page on
+   GitHub, then `uv publish`es.
+4. **github-release** — once PyPI has it, creates the GitHub Release from the
+   notes, with the same wheel and sdist attached.
+
+Publishing uses PyPI **trusted publishing**: PyPI trusts this workflow and the
+`pypi` environment, so no API token exists anywhere. A version, once
+published, is burned — PyPI refuses re-uploads even after a delete, so a
+botched release is fixed by releasing the next number.
+
+`just publish` is the manual escape hatch for when GitHub is down; it needs
+PyPI credentials (e.g. `UV_PUBLISH_TOKEN`) locally.
+
+### Who can release
+
+Pushing a tag needs write access, and on this personally-owned repo every
+collaborator has it — so collaborators *are* the maintainers who can start a
+release. Publishing additionally needs one of the `pypi` environment's
+required reviewers to approve. Before adding a collaborator who shouldn't
+release, note that write access is all-or-nothing here: per-role tag
+restrictions need an organisation-owned repo.
+
+### One-time setup
+
+- **PyPI** → project settings → Publishing → add a GitHub publisher: owner
+  `daaain`, repo `claude-code-log`, workflow `release.yml`, environment `pypi`.
+- **GitHub** → Settings → Environments → `pypi`: add the maintainers as
+  required reviewers (any one approval releases), and limit deployments to
+  tags matching `[0-9]*.[0-9]*.[0-9]*`.
+- **GitHub** → Settings → Rules → Rulesets: the "release tags are immutable"
+  tag ruleset blocks deleting, moving or force-pushing `refs/tags/[0-9]*`, so
+  a published version's tag always names what was released. Releasing a
+  botched version again means the next number, which PyPI requires anyway.

{claude_code_log-1.6.0 → claude_code_log-1.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: claude-code-log
-Version: 1.6.0
+Version: 1.7.0
 Summary: Convert Claude Code transcript JSONL files to HTML
 Project-URL: Homepage, https://github.com/daaain/claude-code-log
 Project-URL: Issues, https://github.com/daaain/claude-code-log/issues
@@ -14,13 +14,13 @@ Requires-Dist: click>=8.3.0
 Requires-Dist: dateparser>=1.2.2
 Requires-Dist: gitpython>=3.1.52
 Requires-Dist: jinja2>=3.1.6
-Requires-Dist: mistune>=3.1.4
 Requires-Dist: packaging>=25.0
 Requires-Dist: pydantic>=2.12.0
 Requires-Dist: pygments>=2.19.2
 Requires-Dist: quickjs-ng<0.16,>=0.15.1.1
 Requires-Dist: textual>=6.5.0
 Requires-Dist: toml>=0.10.2
+Requires-Dist: wenmode<0.16,>=0.15.2
 Description-Content-Type: text/markdown
 
 # Claude Code Log
@@ -73,7 +73,7 @@ uvx claude-code-log@latest --open-browser
 - **Date Range Filtering**: Filter messages by date range using natural language (e.g., "today", "yesterday", "last week")
 - **Rich Message Types**: Support for user/assistant messages, tool use/results, thinking content, images
 - **System Command Visibility**: Show system commands (like `init`) in expandable details with structured parsing
-- **Markdown Rendering**: Server-side markdown rendering with syntax highlighting using mistune
+- **Markdown Rendering**: Server-side markdown rendering with syntax highlighting using wenmode
 - **Detail Levels & Compact Mode**: `--detail full|high|low|minimal|user-only` filters by verbosity and `--compact` merges repeated section headings — pairs well with `--format md` to feed past conversations back to an LLM for analysis or experience building
 - **Floating Navigation**: Always-available back-to-top button and filter controls
 - **CLI Interface**: Simple command-line tool using Click
@@ -256,7 +256,7 @@ When processing all projects, the tool generates:
 - **Session Navigation**: Interactive table of contents with session summaries and timestamp ranges
 - **Token Usage Display**: Individual message and session-level token consumption tracking
 - **Syntax Highlighting**: Code blocks properly formatted with markdown rendering
-- **Markdown Support**: Server-side rendering with mistune including:
+- **Markdown Support**: Server-side rendering with wenmode including:
   - Headers, lists, emphasis, strikethrough
   - Code blocks and inline code
   - Links, images, and tables
@@ -279,18 +279,26 @@ Markdown export provides a lightweight, portable alternative to HTML:
 
 ## Installation
 
-Install using pip:
+The recommended way is installing as a `uv` tool:
 
 ```bash
-pip install claude-code-log
+uv tool install claude-code-log
 ```
 
-Or run directly with uvx (no separate installation step required):
+This will create a `claude-code-log` binary that you can call directly.
+
+Or run directly with `uvx` (no separate installation step required):
 
 ```bash
 uvx claude-code-log@latest
 ```
 
+Alternatively, if you prefer, install using `pip`:
+
+```bash
+pip install claude-code-log
+```
+
 Or install from source:
 
 ```bash
@@ -298,6 +306,8 @@ git clone https://github.com/daaain/claude-code-log.git
 cd claude-code-log
 uv sync
 uv run claude-code-log
+# or if you want `claude-code-log` binary that works everywhere:
+uv tool install --editable .
 ```
 
 ## Contributing
@@ -328,6 +338,4 @@ Cross-platform (macOS and Windows/MSYS).
 - feed the filtered user messages to headless claude CLI to distill the user intent from the session
 - filter message type on Python (CLI) side too, not just UI
 - add minimalist theme and make it light + dark; animate gradient background in fancy theme
-- do we need special handling for hooks?
-- make processing parallel, currently we only use 1 CPU (core) and it's slow
 - merge git worktree directories

{claude_code_log-1.6.0 → claude_code_log-1.7.0}/README.md

@@ -48,7 +48,7 @@ uvx claude-code-log@latest --open-browser
 - **Date Range Filtering**: Filter messages by date range using natural language (e.g., "today", "yesterday", "last week")
 - **Rich Message Types**: Support for user/assistant messages, tool use/results, thinking content, images
 - **System Command Visibility**: Show system commands (like `init`) in expandable details with structured parsing
-- **Markdown Rendering**: Server-side markdown rendering with syntax highlighting using mistune
+- **Markdown Rendering**: Server-side markdown rendering with syntax highlighting using wenmode
 - **Detail Levels & Compact Mode**: `--detail full|high|low|minimal|user-only` filters by verbosity and `--compact` merges repeated section headings — pairs well with `--format md` to feed past conversations back to an LLM for analysis or experience building
 - **Floating Navigation**: Always-available back-to-top button and filter controls
 - **CLI Interface**: Simple command-line tool using Click
@@ -231,7 +231,7 @@ When processing all projects, the tool generates:
 - **Session Navigation**: Interactive table of contents with session summaries and timestamp ranges
 - **Token Usage Display**: Individual message and session-level token consumption tracking
 - **Syntax Highlighting**: Code blocks properly formatted with markdown rendering
-- **Markdown Support**: Server-side rendering with mistune including:
+- **Markdown Support**: Server-side rendering with wenmode including:
   - Headers, lists, emphasis, strikethrough
   - Code blocks and inline code
   - Links, images, and tables
@@ -254,18 +254,26 @@ Markdown export provides a lightweight, portable alternative to HTML:
 
 ## Installation
 
-Install using pip:
+The recommended way is installing as a `uv` tool:
 
 ```bash
-pip install claude-code-log
+uv tool install claude-code-log
 ```
 
-Or run directly with uvx (no separate installation step required):
+This will create a `claude-code-log` binary that you can call directly.
+
+Or run directly with `uvx` (no separate installation step required):
 
 ```bash
 uvx claude-code-log@latest
 ```
 
+Alternatively, if you prefer, install using `pip`:
+
+```bash
+pip install claude-code-log
+```
+
 Or install from source:
 
 ```bash
@@ -273,6 +281,8 @@ git clone https://github.com/daaain/claude-code-log.git
 cd claude-code-log
 uv sync
 uv run claude-code-log
+# or if you want `claude-code-log` binary that works everywhere:
+uv tool install --editable .
 ```
 
 ## Contributing
@@ -303,6 +313,4 @@ Cross-platform (macOS and Windows/MSYS).
 - feed the filtered user messages to headless claude CLI to distill the user intent from the session
 - filter message type on Python (CLI) side too, not just UI
 - add minimalist theme and make it light + dark; animate gradient background in fancy theme
-- do we need special handling for hooks?
-- make processing parallel, currently we only use 1 CPU (core) and it's slow
 - merge git worktree directories