@xbghc/warden 0.5.0 → 0.6.0

package/README.md

@@ -14,7 +14,7 @@ with line comments you can copy back to the agent as a prompt.
 - Comments follow the code: they move with a hunk that gets staged, re-attach after the agent edits the file, and are cleaned up once the change is committed.
 - Auto-refresh — warden watches the repository and reloads itself when you edit, stage, commit or switch branches.
 - Local issues (title, Markdown body, open/closed) that link comments.
-- Branch-scoped todos, exportable as a numbered checklist.
+- Branch-scoped todos, each copied to the clipboard on its own — one task at a time for the agent.
 - Commit history browser: grouped by day, branch / tag labels, search by message, sha, author or
   path (each a `git log` on the server, not a filter over the rows already loaded), and a
   first-parent view that folds merged branches into their merge commits.
@@ -58,18 +58,25 @@ Several instances on the same repository can run at the same time.
 Refs accept anything git can resolve (`main`, `v1.2`, `HEAD~3`, a sha). `@` is `HEAD`.
 Worktrees are discovered with `git worktree list` and share the review state of the main repository.
 
+There is no target switcher in the UI: the sidebar's two blocks *are* the working tree, a commit is
+picked from the *Commits* panel, and the *Branch vs* and *Range* fields at the top of that panel open
+the other two. The sidebar names whatever is under review in its block header and puts a
+*返回工作区* link above it.
+
 `working`, `staged` and `all` are the three **local views** of one worktree. While any of them is
 selected the sidebar shows two blocks — Unstaged (`working`) and Staged (`staged`) — instead of a
 single tree, and clicking a file switches to the view it belongs to. A file that is only partly
 staged appears in both. Switching between the three keeps your comments, the draft you are typing
-and the current selection; only the diff is reloaded. Commit, range and `base` targets keep the single tree.
+and the current selection; only the diff is reloaded. `all` has no control of its own (a saved
+`lastTarget` can still restore it; *Branch vs* `@` shows the same diff). Commit, range and `base`
+targets keep the single tree.
 
 `base:<ref>` is for a branch a coding agent has been working on, committing as it goes: one tree with
 everything since the branch forked off `<ref>` — the commits plus whatever is still uncommitted or
 untracked. The diff runs against the merge base, so commits that landed on `<ref>` after the fork are
-not listed as reverted (which is what a plain `git diff <ref>` would do). The *Branch* button picks the
-base for you — the main worktree's branch when a sibling worktree is under review, otherwise `main` or
-`master` — and the field next to it takes any ref. Unlike the three local views, `base` keeps its own
+not listed as reverted (which is what a plain `git diff <ref>` would do). The *Branch vs* field in the
+Commits panel suggests the base for you — the main worktree's branch when a sibling worktree is under
+review, otherwise `main` or `master` — and takes any ref. Unlike the three local views, `base` keeps its own
 pool of comments and a commit never deletes them: the round under review is not over when the agent
 commits, so a comment whose lines changed stays *orphaned*, snippet and all, until you have checked
 the fix and delete or re-attach it.
@@ -161,19 +168,16 @@ Notes attached to a branch rather than to a line of code, for the things you not
 that do not belong in a comment. They are not deleted when you commit. They sit in the right-hand
 rail next to the comments, under the *Todo* tab: type a title and press Enter to add one, expand a
 card to read or edit its Markdown body, filter by status, and switch between the current branch
-and all branches; *复制 Todo* copies the open ones
-(optionally including the done ones, marked ` (done)`) as:
+and all branches.
+
+Each card has its own *复制* button, and there is deliberately no "copy all": a todo is one task to
+hand to an agent, and the agent it goes to is already working in that branch. So the clipboard gets
+the title and the body — no branch, repo, count or numbering:
 
 ```markdown
-# TODO
-Branch: feature/x
-Repo: /home/user/project
-Count: 2
+补充 OrderList 的空状态
 
-## 1. 补充 OrderList 的空状态
 描述正文（Markdown）…
-
-## 2. useOrder 的依赖数组缺少 id
 ```
 
 ## nvim integration

package/dist/cli.js

@@ -3960,16 +3960,6 @@ function formatIssueExport({ repoRoot, issue, comments }) {
   parts.push(...comments.map(formatCommentSection));
   return parts.join("\n\n") + "\n";
 }
-function formatTodosExport({ repoRoot, branch, todos }) {
-  const head = ["# TODO", `Branch: ${branch}`, `Repo: ${repoRoot}`, `Count: ${todos.length}`];
-  const sections = todos.map((t, i) => {
-    const title = `## ${i + 1}. ${t.title}${t.status === "done" ? " (done)" : ""}`;
-    const body = t.body.replace(/\r\n/g, "\n").trim();
-    return body ? `${title}
-${body}` : title;
-  });
-  return [head.join("\n"), ...sections].join("\n\n") + "\n";
-}
 
 // packages/server/src/nvim.ts
 import os2 from "os";
@@ -4721,15 +4711,6 @@ function createApp(opts) {
     });
     return c.json(todo, 201);
   });
-  api.post("/todos/export", async (c) => {
-    const body = await c.req.json();
-    const branch = typeof body.branch === "string" ? body.branch.trim() : "";
-    if (!branch) throw badRequest("branch is required");
-    const s = await store.load();
-    const todos = s.todos.filter((t) => t.branch === branch && (body.includeDone === true || t.status === "open"));
-    const res = { text: formatTodosExport({ repoRoot: repo.root, branch, todos }), count: todos.length };
-    return c.json(res);
-  });
   api.patch("/todos/:id", async (c) => {
     const id = c.req.param("id");
     const body = await c.req.json();
@@ -4978,7 +4959,7 @@ async function startServer(opts) {
 }
 
 // bin/cli.ts
-var VERSION = true ? "0.5.0" : "dev";
+var VERSION = true ? "0.6.0" : "dev";
 function parseArgs(argv) {
   const args = { repoPath: process.cwd(), open: true, help: false, version: false };
   for (let i = 0; i < argv.length; i++) {