@youtyan/code-viewer 0.11.2 → 0.13.0

package/README.md

@@ -20,6 +20,20 @@ Requires Node.js 20 or newer. Development uses
   same commit list and diff renderer used by `/history` inside the file's
   tab shell, filtered to that path. Both tabs keep the Repository sidebar
   visible.
+- Browse every worktree of the repository from the `Worktrees` item in the
+  header menu, in the same three-pane shape as History: worktrees on the left,
+  the picked one's changed files in the middle, the diff on the right. Each row
+  shows how far its branch has drifted from the base branch (ahead / behind) and
+  whether it still merges cleanly — checked with `git merge-tree`, so no working
+  tree is touched — or which files would conflict. Files are split into
+  uncommitted work and commits made since the branch point, and a banner lists
+  every file that more than one worktree is changing, which is the conflict you
+  would otherwise only find at merge time. Each row carries the folder it lives
+  in, when its files were last touched, and a "…" holding every action for that
+  worktree — open the folder, copy its path, view it in a new tab, stop the
+  server it started, copy the command that merges it back, or delete it. Create
+  a worktree under `.worktrees/` (the dialog shows the exact path before you
+  commit to it); deleting one removes its folder from disk and keeps the branch.
 - Open files directly from the repository or diff view, including text-like
   config/prompt files and large generated files (virtualized source viewer
   with copy/open-full-view).
@@ -68,6 +82,18 @@ Requires Node.js 20 or newer. Development uses
   bottom tier is the tmux sessions no shell has opened yet. Each pane is
   labelled with the title tmux shows for it — a coding agent usually puts what
   it is doing there, so the tree alone tells you which pane is busy.
+- Terminal status combines lifecycle reports with priority-based matching of
+  the live terminal title and recent visible lines. Matching rules can report
+  working, waiting, idle, or keep the previous state. A target is tracked only
+  after a lifecycle report or a visible rule identifies it; screen motion is
+  then used as a fallback. A working match expires when its title and screen
+  stop changing, so a stale status line does not stay active. Edit the complete
+  JSON rule set under Settings & Help → Settings. Its regular expressions use a
+  bounded safe subset; combine conditions with `all` / `any`. Invalid changes
+  list every validation error and do not replace the active rules; restoring
+  the built-in set removes the saved override so later releases can supply
+  updated defaults. The editor includes an expandable field guide, a valid
+  example, and live JSON syntax highlighting.
 - Click a pane and the panel takes you to it. If a shell already has that
   session open, it switches to that shell and makes the pane current; otherwise
   a shell is opened and attached for you. A session moves up to the top tier the
@@ -264,7 +290,8 @@ palette, Ctrl+G grep palette, the Datastores browser, and the file change
 watcher — the same list applies to all five. Both the skip list and the hide
 list accept gitignore-style wildcards (`*`, `?`, `[abc]`, `[!abc]`) in
 addition to exact names. Everything you change in Viewer
-Settings is saved on the server under `.code-viewer/settings.json` (no
+Settings remains a local draft until you select **Save changes**, then it is
+saved on the server under `.code-viewer/settings.json` (no
 separate project-level config file). `.DS_Store` and a broad set of
 build/cache directories (`node_modules`, `dist`, `build`, `.next`, `.turbo`,
 `.parcel-cache`, `.vite`, `.angular`, `.dart_tool`, `.venv`, …) are hidden by