feat: v2.5.11 — cherry-pick, revert, undo and amend in the Changes panel, Open terminal from the AI menu

Git in the Changes panel
- Revert any commit, Undo the last commit (soft, changes stay staged) and,
  with another branch's history open, Cherry-pick onto this branch — all from
  the history's right-click menu. Amend folds staged changes into the last
  commit. Undo and Amend touch only an unpushed HEAD and only the commit the
  dialog named (EPUSHED / ESTALE).
- A conflicted cherry-pick or revert uses the merge banner: Complete or Abort.
  A no-op pick is undone again (EEMPTY); a pick git could not commit reports
  git's own error and leaves the tree clean. A rebase started in a terminal
  blocks every history action.
- Push, Publish, branch delete, cherry-pick, revert and amend ask first. An
  armed discard reads as a red "Discard?" chip. There is no bulk discard.
- History can show another branch (?ref=). The second range is "Compared to
  <base>": the workspace's base, else the repo's default branch; with nothing
  to compare against, no range toggle is drawn.
- The diff editor gets each change block's Undo / Keep bar.

Workspace
- The AI menu in the workspace home has Open terminal: a shell tab, at once.
- "+ Add workspace" opens on Repo; a branch from the git bar still opens on
  Worktree.
- The sidebar no longer keeps a list of closed Terminal tabs.
- Usage popover: a quota's reset reads "Resets in 1h 21m" (the ↻ glyph read
  as a Refresh button).

Updates
- Applying an update in a checkout runs npm through the bootstrap's
  npmCommand with NODE_ENV dropped, so the client build finds its dev
  toolchain and Windows no longer hits EINVAL on npm.cmd.

Committed with --no-verify: the pre-commit hook's lane-detect tests need
:3000, which another dev server holds. Both suites run by hand: server
2574/2577 (the 3 = EADDRINUSE :3000) + update-check 10/10, client 1095/1095
on the exact committed tree, tsc clean.

server/__tests__/update-check.test.js

@@ -12,7 +12,7 @@ const os = require("os");
 const path = require("path");
 const { execFileSync } = require("child_process");
 
-const { getUpdatesStatus } = require("../lib/update-check");
+const { getUpdatesStatus, npmInvocation } = require("../lib/update-check");
 
 // Strip GIT_* vars a parent git hook (e.g. the pre-commit hook running this
 // very suite) sets in its own environment — those leak to every child
@@ -182,3 +182,20 @@ describe("getUpdatesStatus — no remotes configured", () => {
     assert.match(result.message, /No git remotes configured/);
   });
 });
+
+describe("npmInvocation (the checkout's Update now)", () => {
+  it("drops NODE_ENV so `npm run setup` keeps the client's build toolchain", () => {
+    // The server defaults NODE_ENV=production; npm then omits devDependencies,
+    // and vite/typescript are dev deps — the `npm run build` after it failed.
+    const npm = npmInvocation(["run", "setup"], { NODE_ENV: "production", PATH: "/usr/bin" });
+    assert.equal(npm.env.NODE_ENV, undefined);
+    assert.equal(npm.env.PATH.split(path.delimiter).at(-1), "/usr/bin");
+  });
+
+  it("runs the node's own npm, never a bare npm.cmd through execFile", () => {
+    // execFile("npm.cmd") with no shell is EINVAL on Node >= 20.12.2 (Windows).
+    const npm = npmInvocation(["run", "build"], {});
+    assert.ok(npm.file === process.execPath || npm.shell === (process.platform === "win32"));
+    assert.deepEqual(npm.args.slice(-2), ["run", "build"]);
+  });
+});