Merge remote-tracking branch 'origin/main' into claude/message-summarization-feedback-4lpb90

# Conflicts:
#	CHANGELOG.md
#	src/tui/route.tsx
#	test/e2e/tui.test.ts

Author: claude

.github/workflows/publish.yml

@@ -35,13 +35,16 @@ jobs:
       - run: bun run typecheck
       - run: bun test
 
-      # The tag is the version: stamp it into package.json in this checkout only.
+      # The tag is the version: stamp it into package.json in this checkout only. A prerelease
+      # (0.3.0-beta.1) goes under the `beta` dist-tag so `latest` keeps pointing at the last stable.
       - name: Version from the release tag
+        id: version
         run: |
           tag="${GITHUB_REF_NAME#v}"
           echo "$tag" | grep -Eq '^[0-9]+\.[0-9]+\.[0-9]+([-.][0-9A-Za-z.-]+)?$' || { echo "ref '$GITHUB_REF_NAME' is not a version tag" >&2; exit 1; }
           npm version "$tag" --no-git-tag-version --allow-same-version
+          case "$tag" in *-*) echo "dist_tag=beta" ;; *) echo "dist_tag=latest" ;; esac >> "$GITHUB_OUTPUT"
 
       # OIDC trusted publishing needs the package to already exist on npm: the very first
       # version of a new package is published once by hand, every later one lands here.
-      - run: npm publish --provenance --access public
+      - run: npm publish --provenance --access public --tag "${{ steps.version.outputs.dist_tag }}"

.github/workflows/release.yml

@@ -81,7 +81,8 @@ jobs:
           git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
           git tag -a "v$v" -m "v$v"
           git push origin "v$v"
-          gh release create "v$v" --title "v$v" --generate-notes
+          prerelease=""; case "$v" in *-*) prerelease="--prerelease" ;; esac
+          gh release create "v$v" --title "v$v" --generate-notes $prerelease
           gh workflow run publish.yml --ref "v$v"
           echo "Released v$v; publish workflow dispatched on the tag."
 

CHANGELOG.md

@@ -1,26 +1,31 @@
 # Changelog
 
-## Unreleased
+## 0.3.0-beta.2 — 2026-09-09
 
 - **The status line now asks OpenCode for a frame when it changes.** OpenCode's renderer draws
-  on demand, so a signal changed from inside an `await` — every progress update, and every
-  notice raised by a slow action — reached the buffer and then waited there for something else
-  to trigger a repaint. While a draft is running the route also holds the renderer's own
-  refcounted `requestLive()`, the same thing an animation asks for, and drops it when the draft
-  ends. On the two OpenCode versions the e2e suite can drive (1.18.26 and 1.18.29) the line was
-  already being painted promptly without this, so it is a robustness fix rather than a
-  confirmed cure for a report of no feedback at all — but nothing should depend on someone
-  else's render loop to be visible.
+  on demand, and nothing here ever called `requestRender()`: a signal changed from inside an
+  `await` — every progress update, and every notice raised by a slow action — reached the
+  render buffer and then waited there for something else to trigger a repaint. While a draft
+  runs the route also holds the renderer's own refcounted `requestLive()`, the same thing an
+  animation asks for, and drops it when the draft ends.
+
+  This is the one difference between 0.3.0-beta.1 and the branch summary reading as "no
+  feedback at all": beta.1 carries the progress line but never asks to be drawn. On the two
+  OpenCode versions the e2e suite can drive (1.18.26 and 1.18.29) the line was already being
+  painted promptly without it, so the fix is unconfirmed against a report rather than proven —
+  but nothing should depend on another component's render loop to be visible.
 
 - **The e2e suite can now watch a draft while it runs.** `startMock({ slowSummaryMs })` holds
   back the branch-summary request only (the setup turns stay fast), and a new test samples the
   tree 0.3s after you choose *Summarize* and three more times half a second apart: the line
   must be up on all four, and the spinner must have turned between them. Every earlier test
-  used a mock that answered instantly, so nothing ever looked at the screen mid-draft.
+  used a mock that answered instantly, so nothing had ever looked at the screen mid-draft.
 
 - `CTREE_OPENCODE_VERSION` picks the OpenCode the e2e suite installs and drives (default
   1.18.26), so a report against a newer release can be reproduced without editing the harness.
 
+## 0.3.0-beta.1 — 2026-09-08
+
 ### Breaking: the keymap is now vim-aligned
 
 A key inside `/tree` should mean what it means in vim. Seven bindings did not, and they have