@coderook/cli 0.25.0 → 0.25.1

package/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "coderook",
   "displayName": "CodeRook",
   "description": "Save, browse and restore whole-snapshot versions of a project on CodeRook, from Claude Code.",
-  "version": "0.25.0",
+  "version": "0.25.1",
   "author": {
     "name": "ACCA Gaming Productions",
     "url": "https://coderook.com"

package/README.md

@@ -282,12 +282,14 @@ a half-written tree.
 
 ## Claude Code
 
-```
+Run this **in a terminal**, not inside Claude Code:
+
+```bash
 cbx skill
 ```
 
-That is the whole setup. It writes a short guide into Claude Code's skills
-folder, and from then on you ask for what you want in ordinary words:
+That is the whole setup. It writes `~/.claude/skills/coderook/SKILL.md`, and
+from then on you ask for what you want in ordinary words:
 
 > save this to CodeRook
 
@@ -298,6 +300,12 @@ folder, and from then on you ask for what you want in ordinary words:
 Claude works out which commands to run. You can also call it by name with
 `/coderook`.
 
+**The skill is called `coderook`, not `cbx`.** `cbx` is the command line, run
+in a terminal; the skill is the file that teaches Claude how to use it. Typing
+`cbx skill` *into* Claude Code asks it for a skill by that name and it will
+tell you there is not one — which is correct, and is why the line above says
+where to run it.
+
 `cbx skill --project` writes it into `./.claude` instead of your home
 folder, so it travels with the repository and everybody who clones it has it
 too.

package/dist/cli/src/cli.js

@@ -44,25 +44,13 @@ const api_js_2 = require("./api.js");
 const import_command_js_1 = require("./import_command.js");
 const runner_js_1 = require("./runner.js");
 const config_js_1 = require("./config.js");
-/*
-  Read from the package rather than written twice. A hardcoded copy had
-  already drifted from the published version, which makes `cbx doctor`
-  worse than useless when working out what somebody is actually running.
-*/
-const VERSION = (() => {
-    try {
-        return (require("../../../package.json").version ?? "0.0.0");
-    }
-    catch {
-        return "0.0.0";
-    }
-})();
+const version_js_1 = require("./version.js");
 /*
   Said once, before anything reaches the service. The version comes from the
   package rather than a constant, so it cannot drift from what was published
   and claim a behaviour this build does not have.
 */
-(0, identify_js_1.declareClient)("cli", VERSION);
+(0, identify_js_1.declareClient)("cli", version_js_1.VERSION);
 // ── presentation ────────────────────────────────────────────────────────────
 const colour = node_process_1.default.stdout.isTTY && !node_process_1.default.env.NO_COLOR;
 const dim = (text) => (colour ? `${text}` : text);
@@ -1205,7 +1193,7 @@ async function commandInspect(parsed) {
 }
 async function commandDoctor() {
     const service = await (0, api_js_2.health)().catch(() => null);
-    console.log(`cbx ${VERSION} · Node ${node_process_1.default.versions.node} · ${node_process_1.default.platform}`);
+    console.log(`cbx ${version_js_1.VERSION} · Node ${node_process_1.default.versions.node} · ${node_process_1.default.platform}`);
     console.log(`Config: ${(0, config_js_1.configDirectory)()}`);
     console.log(service
         ? `Service: ${service.status} · schema ${service.schemaVersion}` +
@@ -1417,7 +1405,7 @@ async function commandRunner(parsed) {
     for (;;) {
         let job = null;
         try {
-            job = await (0, runner_js_1.claim)(project.id, name, VERSION, answersTo);
+            job = await (0, runner_js_1.claim)(project.id, name, version_js_1.VERSION, answersTo);
         }
         catch (error) {
             /*
@@ -2040,7 +2028,7 @@ const SPECS = [
             "A project whose owner has turned off machine reading is refused, in\n" +
             "words rather than as a status code.\n",
         examples: ["claude mcp add coderook -- cbx mcp"],
-        run: () => (0, mcp_js_1.commandMcp)(VERSION),
+        run: () => (0, mcp_js_1.commandMcp)(version_js_1.VERSION),
     },
     {
         name: "doctor",
@@ -2054,11 +2042,11 @@ const REGISTRY = (0, registry_js_1.buildRegistry)(SPECS);
 async function main(argv) {
     const [name, ...rest] = argv;
     if (!name || name === "--help" || name === "-h") {
-        console.log((0, help_js_1.renderHelp)(REGISTRY, VERSION));
+        console.log((0, help_js_1.renderHelp)(REGISTRY, version_js_1.VERSION));
         return 0;
     }
     if (name === "--version" || name === "-v" || name === "version") {
-        console.log(VERSION);
+        console.log(version_js_1.VERSION);
         return 0;
     }
     /*
@@ -2069,7 +2057,7 @@ async function main(argv) {
     if (name === "help") {
         const wanted = rest[0];
         if (!wanted) {
-            console.log((0, help_js_1.renderHelp)(REGISTRY, VERSION));
+            console.log((0, help_js_1.renderHelp)(REGISTRY, version_js_1.VERSION));
             return 0;
         }
         const spec = REGISTRY.lookup.get(wanted);

package/dist/cli/src/git_history.js

@@ -10,7 +10,7 @@
  * is why this file exists at all.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.TRAILER = exports.EMPTY_TREE = void 0;
+exports.MESSAGE_LIMIT = exports.TRAILER = exports.EMPTY_TREE = void 0;
 exports.parseRemoteUrl = parseRemoteUrl;
 exports.commitFromMessage = commitFromMessage;
 exports.messageWithCommit = messageWithCommit;
@@ -75,10 +75,47 @@ function commitFromMessage(message) {
     ];
     return all.length ? all[all.length - 1][1] : null;
 }
-/** Attach the marker to a commit message without disturbing what it says. */
+/**
+ * What a version message may hold, matching the service.
+ *
+ * Not a guess and not a safety margin: the publish endpoint trims and then
+ * refuses anything longer, so exceeding it fails the whole push rather than
+ * being quietly shortened somewhere along the way.
+ */
+exports.MESSAGE_LIMIT = 240;
+/**
+ * Attach the marker to a commit message, within what the service will accept.
+ *
+ * The marker is not decoration — it is how a version is tied back to the
+ * commit it came from, and losing it means a later push republishes history
+ * the project already holds. So when the two together are too long, the
+ * message gives way and the marker survives.
+ *
+ * Git's own convention decides how: the first line is the summary and the rest
+ * is detail, so as much as fits is kept and the remainder is cut on a word
+ * boundary. A repository with a two-paragraph commit message would otherwise
+ * fail the push outright — which is what it did, on a real transfer, with an
+ * error naming a limit the person had never heard of.
+ */
 function messageWithCommit(message, sha) {
+    const trailer = `\n\n${exports.TRAILER} ${sha}`;
+    const room = exports.MESSAGE_LIMIT - trailer.length;
     const body = message.replace(/\s+$/, "");
-    return `${body}\n\n${exports.TRAILER} ${sha}`;
+    if (body.length <= room)
+        return `${body}${trailer}`;
+    /*
+      Cut on a word boundary when one is reasonably near the end, so the result
+      reads as a shortened sentence rather than a severed one. The ellipsis is
+      what tells a reader there was more.
+    */
+    const kept = body.slice(0, room - 1);
+    const tidy = kept.replace(/\s+\S*$/, "");
+    const shortened = (tidy.length > room / 2 ? tidy : kept).trimEnd();
+    /*
+      A message of nothing but whitespace would leave an empty string, which the
+      service refuses for its own reason: it requires at least one character.
+    */
+    return `${shortened || sha.slice(0, 8)}…${trailer}`;
 }
 /**
  * The message as a person wrote it, with our bookkeeping taken back out.

package/dist/cli/src/git_remote.js

@@ -106,6 +106,7 @@ const upload_js_1 = require("../../desktop-app/src/main/upload.js");
 const tracks_js_1 = require("../../desktop-app/src/main/tracks.js");
 const identify_js_1 = require("../../desktop-app/src/main/identify.js");
 const config_js_1 = require("./config.js");
+const version_js_1 = require("./version.js");
 const publish_js_1 = require("./publish.js");
 const git_history_js_1 = require("./git_history.js");
 const api_js_1 = require("./api.js");
@@ -1080,7 +1081,14 @@ async function* lines() {
 }
 async function main(argv) {
     const url = argv[1] ?? argv[0] ?? "";
-    (0, identify_js_1.declareClient)("cli", "git-remote");
+    /*
+      The real version, not the word "git-remote". This passed its own name
+      where the version belongs, so the service applied its version floor and
+      refused to serve files — `git clone` failed with a demand to update to a
+      release older than the one running. Push was unaffected, which is why it
+      went unnoticed until a clone.
+    */
+    (0, identify_js_1.declareClient)("cli", version_js_1.VERSION);
     const pending = [];
     const importing = [];
     for await (const line of lines()) {

package/dist/cli/src/version.js

@@ -0,0 +1,59 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.VERSION = void 0;
+/**
+ * What this build calls itself to the service.
+ *
+ * Read from the package rather than written down, because a hardcoded copy had
+ * already drifted from the published version once — and the version is not
+ * cosmetic. The service refuses operations it knows an older client cannot do
+ * safely, so a build that misstates its version is refused as though it were
+ * ancient.
+ *
+ * Which is exactly what happened: the git remote helper announced itself as
+ * `cli/git-remote`, having passed its own name where the version belongs. The
+ * service could make nothing of it, applied the floor, and told people to
+ * update to a version far older than the one they were running. Pushing was
+ * unaffected and cloning was refused, so it surfaced only on the way back.
+ */
+const node_fs_1 = require("node:fs");
+const node_path_1 = __importDefault(require("node:path"));
+/**
+ * Search upwards for this package's own manifest.
+ *
+ * A fixed number of `..` segments only holds for one directory layout. The
+ * compiled file sits three deep under `dist`, the source two deep under `src`,
+ * and a bundler may put it somewhere else again — so a fixed path silently
+ * resolved to a different package's manifest, or to none, and fell back to
+ * `0.0.0`. Walking up and checking the name finds the right file wherever
+ * this ends up.
+ */
+function readVersion() {
+    /*
+      `__dirname` in the build, which compiles to CommonJS and is what ships.
+      Running the source directly for a test loads it as a module where that name
+      does not exist, so the check is on `typeof` — which is safe for a name that
+      was never declared — and the working directory stands in.
+    */
+    let here = typeof __dirname === "string" ? __dirname : process.cwd();
+    for (let up = 0; up < 6; up += 1) {
+        try {
+            const manifest = JSON.parse((0, node_fs_1.readFileSync)(node_path_1.default.join(here, "package.json"), "utf8"));
+            if (manifest.name === "@coderook/cli" && manifest.version) {
+                return manifest.version;
+            }
+        }
+        catch {
+            // Not here, or not readable. Keep walking.
+        }
+        const parent = node_path_1.default.dirname(here);
+        if (parent === here)
+            break;
+        here = parent;
+    }
+    return "0.0.0";
+}
+exports.VERSION = readVersion();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@coderook/cli",
-  "version": "0.25.0",
+  "version": "0.25.1",
   "description": "CodeRook from the command line, on any operating system",
   "license": "SEE LICENSE IN LICENSE.txt",
   "homepage": "https://coderook.com",