@coderook/cli 0.33.1 → 0.34.1

package/.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "name": "coderook",
   "displayName": "CodeRook",
-  "description": "Save, browse and restore whole-snapshot versions of a project on CodeRook, from Claude Code.",
-  "version": "0.33.1",
+  "description": "Save, browse and restore whole-snapshot versions of a project on CodeRook, with cbx or plain git, from Claude Code.",
+  "version": "0.34.1",
   "author": {
     "name": "ACCA Gaming Productions",
     "url": "https://coderook.com"
@@ -13,6 +13,7 @@
     "coderook",
     "versioning",
     "snapshots",
-    "backup"
+    "backup",
+    "git"
   ]
 }

package/README.md

@@ -32,7 +32,7 @@ project moved by one is understood by the other.
 
 ## Install
 
-Requires Node 20.11 or later, and nothing else.
+Requires Node 22.15 or later (Node 24 is the safe choice), and nothing else. Older Node lacks the zstd support bundles use, and the CLI says so rather than failing later.
 
 ```
 npm install --global @coderook/cli
@@ -80,9 +80,20 @@ cbx clone my-project          fetch a project into a new folder
 ```
 
 `status` and `submit` act on the current directory unless you name another.
-The first time either runs in a folder, it looks for a project on your account
-whose name matches and links the two, so a folder you already uploaded from
-the desktop is recognised rather than treated as new.
+
+A folder is linked to its project by its first save, by `cbx clone`, or by
+`cbx link <project>`, and the link travels with the folder (in
+`.coderook/link.json`), so the same disk seen from another operating system is
+still recognised. A folder that is not linked is never matched to a project by
+name. Its first `submit` starts a new project, unless your account already has
+one with a name like it; then you are asked which you mean. A script or an
+assistant has to say:
+
+```
+cbx submit --into my-project -m "…"    this folder is that project
+cbx submit --new -m "…"                a separate project
+cbx link my-project                    link it now, send nothing
+```
 
 `submit` sends only what changed. Files the service already holds are not
 uploaded again, and the version it records still names every file in the
@@ -302,14 +313,31 @@ Installing the CLI also installs `git-remote-coderook`, so git talks to
 CodeRook directly — both ways:
 
 ```
-git clone coderook://my-project
+git clone coderook://my-project                       # the remote is called origin
+git remote add coderook coderook://my-project         # or add it to a repository you have
 git push coderook main
-git fetch
+git fetch coderook
+```
+
+If your folder is a git repository, use this rather than `cbx submit`: each
+commit arrives with its own message, and every editor's built-in git panel
+works with CodeRook without a plugin. `cbx submit` is the tool for folders
+that are not git repositories. The helper is installed by
+`npm install --global @coderook/cli`; the Claude Code plugin and `npx` do not
+put it on your `PATH`.
+
+**A project you started with `cbx submit`.** Its saves did not come from git,
+so the first push from your repository is refused rather than replaying your
+history on top of them. If the repository holds that project, adopt it once:
+
+```
+git push -o adopt coderook main
 ```
 
-It exists so that every editor's built-in git panel works with CodeRook
-without a plugin. If you are not already living in git, `cbx submit` is
-the simpler tool and this is not an upgrade on it.
+The project's saves stay as they are, your current commit is saved on top as
+one save, and from then on every push sends one save per commit. Or start
+from the project instead: `git clone coderook://my-project` and carry on in
+the clone.
 
 **Pushing.** Each commit becomes a version, oldest first, with its message
 kept. Later pushes send only what is new, so the usual case — a few commits —
@@ -348,7 +376,7 @@ has two parents is rebuilt as a real git merge.
 Each version records the commit it came from, so a colleague pushing the same
 project does not republish history the project already holds. Pushing a git
 history into a project whose versions came from somewhere else is refused
-rather than interleaved.
+rather than interleaved, unless you adopt it with `-o adopt` as above.
 
 ### The names are the same
 
@@ -408,6 +436,34 @@ artifacts or with `cbx attach <file>`, so a release made by pushing a tag
 simply has none until something adds them — which is what a release without a
 build has always looked like.
 
+## Building for every platform
+
+```
+cbx build --plan                  how each target would be built on this machine
+cbx build --target win,linux,mac  build them
+cbx build --target all --ship     and attach them to the newest save
+cbx build init                    describe the build in coderook.build.json
+```
+
+`cbx build` makes the project's executables for Windows, Linux and macOS on
+the machine you are using. Each target is built natively or cross-compiled,
+chosen from what is installed; Docker and WSL are used when present and never
+required for Linux. A target that cannot be built here is named, with what
+would build it.
+
+| Toolchain | From any machine | Needs its own system |
+| --- | --- | --- |
+| Go, Bun, Deno, .NET | Windows, Linux, macOS | — |
+| Rust | all three, with cargo-zigbuild | macOS apps using system frameworks |
+| Electron | Linux (tar.gz) straight from Windows; Windows and Linux elsewhere with Docker or wine | macOS; AppImage and deb need Linux |
+| Python | Windows, Linux, macOS: the target's own CPython with its wheels, as a tar.gz with a launcher (PyInstaller where it runs) | a dependency with no wheel for that system |
+
+The toolchain is recognised from the files present. `coderook.build.json`
+settles it, and takes a command of your own (`{target}`, `{os}`, `{arch}` and
+`{out}` are filled in, and a target can name a Docker image to run it in).
+Output lands in `.coderook/build/<target>/`, which is never uploaded and which
+git ignores — not `dist/`, which Electron apps commonly package.
+
 ## Bundles
 
 ```

package/dist/cbx/src/core/cbx.js

@@ -31,6 +31,7 @@ const node_crypto_1 = require("node:crypto");
 const node_fs_1 = require("node:fs");
 const promises_1 = require("node:fs/promises");
 const node_path_1 = __importDefault(require("node:path"));
+const node_process_1 = __importDefault(require("node:process"));
 const safe_path_js_1 = require("../shared/safe_path.js");
 const node_zlib_1 = require("node:zlib");
 const download_js_1 = require("./download.js");
@@ -411,6 +412,14 @@ async function unpackBundle(source, destination, report) {
                 throw new Error(`${record.path} did not survive the bundle intact`);
             }
             await (0, promises_1.writeFile)(full, contents);
+            /*
+              The mode was recorded when the bundle was made and never put back, so
+              a script that went in executable came out needing chmod. Only the
+              permission bits, and only where the system has them.
+            */
+            if (node_process_1.default.platform !== "win32" && record.mode & 0o111) {
+                await (0, promises_1.chmod)(full, (record.mode & 0o777) | 0o400);
+            }
             written += 1;
             bytes += contents.length;
         }

package/dist/cbx/src/core/upload.js

@@ -730,6 +730,10 @@ class Uploader {
             const existing = await this.findBySlug(slug);
             if (!existing)
                 throw error;
+            if (request.joinExisting === false) {
+                throw new Error(`Your account already has a project called ${slug}. Save into it on purpose, ` +
+                    `or give this one another name.`);
+            }
             return existing;
         }
     }

package/dist/cbx/src/local/remote.js

@@ -217,6 +217,7 @@ async function push(repository, options) {
                     message: shortMessage(save.message),
                     projectName: options.projectName,
                     repositoryId,
+                    ...(options.joinExisting === false ? { joinExisting: false } : {}),
                     baseVersionId,
                     ...(baseVersionId ? { expectedHeadVersionId: baseVersionId } : {}),
                     track: line,