agent-kitchen 0.3.0 → 0.3.1

package/README.md

@@ -24,7 +24,7 @@ Al arrancar revisa si npm tiene una versión más nueva de sí mismo. Si la hay,
 |---|---|---|---|---|---|
 | `issue-flow` | Flujo de issues ([`@ramon-sg/issue-flow`](https://github.com/ramon-sg/issue-flow)): rama, worktree y PR en draft por issue, y sus 5 skills | `package.json` | npm | `issue-flow init` | `issue-flow upgrade` en la versión nueva, y sus skills a la misma tag |
 | `claude-cloud` | Sesiones en la nube ([`@ramon-sg/claude-cloud`](https://github.com/ramon-sg/claude-cloud)): herramientas, Docker y el clone completo | `.claude/cloud.json` | npm | `claude-cloud init` | Cambia la versión que fija `.claude/cloud.json` |
-| `claude-repo-guard` | Barandas ([`claude-repo-guard`](https://github.com/ramon-sg/claude-repo-guard)): modo auto con sandbox, escribe solo en su worktree | `.claude/repo-guard.manifest.json` | Tags `vX.Y.Z` de GitHub | `install` en esa tag | `install` en la tag nueva |
+| `claude-repo-guard` | Barandas ([`claude-repo-guard`](https://github.com/ramon-sg/claude-repo-guard)): modo auto con sandbox, escribe solo en su worktree | `.claude/repo-guard.manifest.json` | Tags `vX.Y.Z` de GitHub | `apply` en esa tag (`install` antes de 0.5.0) | `apply` en la tag nueva |
 | `skills` | Skills con [`skills-manager`](https://github.com/ramon-sg/skills-manager): las del flujo y las de [`agent-skills`](https://github.com/ramon-sg/agent-skills) (planes, auditoría de código y de tests) | `.agents/skills.lock.json` | Tags del catálogo | `skills-manager init --select` con las elegidas | `skills-manager update` |
 
 Si npm o GitHub no responden, la pieza se muestra pero no se ofrece actualizarla. Si un paso falla, los demás siguen y el comando dice cómo reintentarlo.

package/dist/pieces/guard.d.ts

@@ -7,6 +7,11 @@
  * macOS `weakerNetworkIsolation` lets `gh` work inside the sandbox (the guard's own default
  * is false, so false counts as missing; the step can be unticked). When the flow is
  * installed in the same run, the guard gets those options in that run too.
+ *
+ * Its command that installs or updates is `apply` since 0.5.0 and `install` before, so the
+ * command follows the version being run. If it fails, its own output is shown; the hint about
+ * Claude's sandbox is added only when that output is a permission error, which is how the
+ * sandbox's block on `.claude/settings.json` shows up.
  */
 import { type Check, type PieceStatus } from "../piece.js";
 /** The piece's name, as `--skip` takes it. */
@@ -24,6 +29,21 @@ export declare const WEAKER_NETWORK = "weakerNetworkIsolation";
  * @example guardSpec("0.2.0") // "github:ramon-sg/claude-repo-guard#v0.2.0"
  */
 export declare function guardSpec(version: string | null): string;
+/**
+ * The guard's command that installs or updates, at a version.
+ * @param version - The version, or null for the default branch.
+ * @returns `apply` from 0.5.0 on and on the default branch, `install` before.
+ * @example guardCommand("0.4.1") // "install"
+ */
+export declare function guardCommand(version: string | null): string;
+/**
+ * What to say when the guard did not install.
+ * @param version - The version it ran.
+ * @param output - What it printed.
+ * @returns One line: the command to run by hand, and the sandbox hint only if the output is a permission error.
+ * @example guardFailure("0.5.1", "Error: EPERM: operation not permitted") // "…sandbox…"
+ */
+export declare function guardFailure(version: string | null, output: string): string;
 /**
  * The guard's options with what the flow needs added; what the repo set stays.
  * @param root - The repo.

package/dist/pieces/guard.js

@@ -7,6 +7,11 @@
  * macOS `weakerNetworkIsolation` lets `gh` work inside the sandbox (the guard's own default
  * is false, so false counts as missing; the step can be unticked). When the flow is
  * installed in the same run, the guard gets those options in that run too.
+ *
+ * Its command that installs or updates is `apply` since 0.5.0 and `install` before, so the
+ * command follows the version being run. If it fails, its own output is shown; the hint about
+ * Claude's sandbox is added only when that output is a permission error, which is how the
+ * sandbox's block on `.claude/settings.json` shows up.
  */
 import { FLOW_CONFIG } from "../piece.js";
 import { readJson, writeJson } from "../repo.js";
@@ -32,6 +37,32 @@ export const WEAKER_NETWORK = "weakerNetworkIsolation";
 export function guardSpec(version) {
     return version === null ? `github:${REPO}` : `github:${REPO}#v${version}`;
 }
+/** The first version whose install command is `apply`. */
+const APPLY_SINCE = "0.5.0";
+/** What a write blocked by a sandbox or by the file's permissions prints. */
+const PERMISSION_ERROR = /\b(EPERM|EACCES|EROFS)\b|operation not permitted|permission denied|read-only file system/i;
+/**
+ * The guard's command that installs or updates, at a version.
+ * @param version - The version, or null for the default branch.
+ * @returns `apply` from 0.5.0 on and on the default branch, `install` before.
+ * @example guardCommand("0.4.1") // "install"
+ */
+export function guardCommand(version) {
+    return version === null || compareVersions(version, APPLY_SINCE) >= 0 ? "apply" : "install";
+}
+/**
+ * What to say when the guard did not install.
+ * @param version - The version it ran.
+ * @param output - What it printed.
+ * @returns One line: the command to run by hand, and the sandbox hint only if the output is a permission error.
+ * @example guardFailure("0.5.1", "Error: EPERM: operation not permitted") // "…sandbox…"
+ */
+export function guardFailure(version, output) {
+    const command = `npx ${guardSpec(version)} ${guardCommand(version)}`;
+    if (PERMISSION_ERROR.test(output))
+        return `claude-repo-guard no se instaló: no tuvo permiso para escribir en el repo. Si corres agent-kitchen dentro de una sesión de Claude, su sandbox bloquea .claude/settings.json; corre '${command}' desde tu terminal.`;
+    return `claude-repo-guard no se instaló; su error está abajo. Para reintentar a mano: '${command}'.`;
+}
 /**
  * The guard's options with what the flow needs added; what the repo set stays.
  * @param root - The repo.
@@ -71,10 +102,10 @@ async function install(context, version) {
         writeJson(context.root, CONFIG, options);
     for (const change of changes)
         context.note(change);
-    const run = await runNpx(context.root, [guardSpec(version), "install", "--yes"]);
+    const run = await runNpx(context.root, [guardSpec(version), guardCommand(version), "--yes"]);
     if (run.ok)
         return true;
-    context.fail(`claude-repo-guard no se instaló; corre 'npx ${guardSpec(version)} install' desde tu terminal (dentro de una sesión de Claude su sandbox bloquea .claude/settings.json).`, run.output);
+    context.fail(guardFailure(version, run.output), run.output);
     return false;
 }
 /**

package/package.json

@@ -1,13 +1,22 @@
 {
   "name": "agent-kitchen",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "One command to install, update and check a repo's agent tooling: the issue flow and its skills, the general skills, Claude cloud sessions and claude-repo-guard.",
   "license": "MIT",
   "type": "module",
-  "bin": { "agent-kitchen": "dist/cli.js" },
-  "files": ["dist"],
-  "engines": { "node": ">=20" },
-  "publishConfig": { "access": "public", "provenance": true },
+  "bin": {
+    "agent-kitchen": "dist/cli.js"
+  },
+  "files": [
+    "dist"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "publishConfig": {
+    "access": "public",
+    "provenance": true
+  },
   "repository": {
     "type": "git",
     "url": "git+https://github.com/ramon-sg/agent-kitchen.git"
@@ -17,6 +26,11 @@
     "test": "tsc && node --test test/*.test.mjs",
     "prepublishOnly": "npm test"
   },
-  "dependencies": { "@clack/prompts": "1.8.1" },
-  "devDependencies": { "@types/node": "^24.0.0", "typescript": "^5.9.3" }
+  "dependencies": {
+    "@clack/prompts": "1.8.1"
+  },
+  "devDependencies": {
+    "@types/node": "^24.0.0",
+    "typescript": "^5.9.3"
+  }
 }