@warren-dean/code-kit 0.15.0 → 0.15.1

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "name": "code-kit",
       "source": "./",
       "description": "Keeps AI coding agents inside your project's rules, from idea to merged code: spec design, lanes, layer rules, protected paths with an approval log, spec-check and design gates, proof-before-finish checks, dispatch, review, build status and CI verification, configured per project from its docs",
-      "version": "0.15.0",
+      "version": "0.15.1",
       "category": "development",
       "tags": ["guardrails", "architecture", "lanes", "layers", "spec-driven", "ci", "multi-agent"],
       "license": "MIT"

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "code-kit",
-  "version": "0.15.0",
+  "version": "0.15.1",
   "description": "Keeps AI coding agents inside your project's rules, from idea to merged code: spec design, lanes, layer rules, protected paths with an approval log, spec-check and design gates, proof-before-finish checks, dispatch, review, build status and CI verification, configured per project from its docs",
   "author": {
     "name": "Warren Langeveldt"

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 What changed in each release of code-kit, newest first. Versions follow the plugin manifest and the npm package `@warren-dean/code-kit`. Each release is also on [GitHub Releases](https://github.com/warrendeanlangeveldt/code-kit/releases).
 
+## 0.15.1 (2026-10-16)
+
+Lanes stop less often to wait for you.
+
+- A lane reading `.claude/code-kit.json` with an inline script, such as `python3 -c "json.load(open(...))"`, no longer waits for your approval. The bash guard used to count any Python command that named a kit file as a change to the kit, so each lane that read its spec folders this way filed a kit request and stopped: 11 of one project's 16 approval requests. An inline Python or Node script is now judged by its code, and only one that writes the kit, or whose output is redirected into it, is refused. A Python script run from a file still counts as a change, and the check after each shell call still catches any real write. The spec-check skill tells lanes to open the config with the Read tool.
+- A call Claude Code refused that later goes through, the same tool from the same agent (for a shell command, the same command), leaves the band. Before, every refusal stayed in the band until you pressed Done it or Not now, even after a retry had worked, so the band could show calls refused that no longer needed you.
+
 ## 0.15.0 (2026-10-16)
 
 The lane agents can run on a cheaper model than the lead.

package/hooks/guard-bash.mjs

@@ -368,8 +368,21 @@ if (team) {
 const KIT_PATH = /\.claude\/(hooks|agents|skills|settings[^/]*\.json|README\.md|code-kit\.json)/;
 // a real redirect into a file; `2>&1` and `>/dev/null` are not writes
 const WRITES =
-  /((?<![0-9&])>>?\s*(?!&|\/dev\/null)\S|\btee\b|\bsed\s+-i|\bperl\s+-i|\bmv\b|\bcp\b|\brm\b|\bpython3?\b|\bnode\s+-e|\btruncate\b|\bchmod\b|\bln\b)/;
-const kitWrite = commandsOf(cmd).some((c) => KIT_PATH.test(c.text) && WRITES.test(c.text));
+  /((?<![0-9&])>>?\s*(?!&|\/dev\/null)\S|\btee\b|\bsed\s+-i|\bperl\s+-i|\bmv\b|\bcp\b|\brm\b|\btruncate\b|\bchmod\b|\bln\b)/;
+// An inline script (`python3 -c`, `node -e`) is judged by its code: lanes read the config this way,
+// and a read isn't a change to the kit. A Python script run from a file can't be read here, so it counts.
+const SCRIPT = /\bpython3?\b/;
+const INLINE =
+  /(?:^|\s)(?:python3?\s+(?:-\w+\s+)*-c|node\s+(?:-\w+\s+)*(?:-e|--eval|-p|--print))\s/;
+const SCRIPT_WRITES =
+  /\bopen(?:Sync)?\s*\([^)]*['"][rwax]*[wax+][rwax+b]*['"]|\.write_(?:text|bytes)\b|\.(?:unlink|rename|touch|rmdir|chmod|symlink_to)\s*\(|\bos\.(?:remove|unlink|rename|replace|rmdir|chmod|symlink|system|popen)\b|\bshutil\.|\bsubprocess\.|\b(?:writeFile|appendFile|rm|rmdir|unlink|rename|copyFile|cp|chmod|truncate|symlink|createWriteStream)(?:Sync)?\s*\(|\bexecSync\b|\bspawnSync\b|\bchild_process\b/;
+const writesKit = ({ text, code }) => {
+  if (!KIT_PATH.test(text)) return false;
+  // the script's own text is quoted, so a `>` in it isn't a redirect; one outside it still is
+  if (INLINE.test(text)) return WRITES.test(code) || SCRIPT_WRITES.test(text);
+  return WRITES.test(text) || SCRIPT.test(text);
+};
+const kitWrite = commandsOf(cmd).some(writesKit);
 if (kitWrite && actor.kind !== 'lead' && !approval(root, 'kit', actor)) {
   recordRequest(
     root,

package/hooks/mod/register.mjs

@@ -1684,6 +1684,7 @@ export function register(on) {
     const lane = e.agent_id ? activity.get(e.agent_id)?.lane : null;
     denied.set(e.tool_use_id ?? `${e.tool_name}-${denied.size}`, {
       id: e.tool_use_id ?? `${e.tool_name}-${denied.size}`,
+      agentId: e.agent_id ?? null,
       who: lane ? `the ${lane} lane` : (e.agent_type ?? (e.agent_id ? 'an agent' : 'the lead')),
       tool: e.tool_name,
       command,
@@ -1733,6 +1734,19 @@ export function register(on) {
     try {
       const res = await next(e);
       const text = res?.deny ?? (res?.isError ? (res.text ?? String(res.result ?? '')) : null);
+      // PERM-1: a refused call that later goes through (retried, or allowed) no longer waits for the person.
+      if (!text && denied.size) {
+        const command = e.tool === 'Bash' ? (e.command ?? null) : null;
+        const before = denied.size;
+        for (const [id, d] of denied)
+          if (
+            d.tool === e.tool &&
+            d.agentId === (e.agentId ?? null) &&
+            (!d.command || d.command === command)
+          )
+            denied.delete(id);
+        if (denied.size < before) $.ui.invalidate('ui.render');
+      }
       if (text && refusalCard(text)) {
         refusals.set(e.tool_use_id, text);
         if (refusals.size > REFUSALS_KEPT) refusals.delete(refusals.keys().next().value);

package/hooks/mod/register.test.ts

@@ -1707,6 +1707,38 @@ test("PERM-1 a call Claude Code's own permission check refused waits for the per
   await after.unmount();
 });
 
+test('PERM-1 a refused call that later goes through no longer waits for the person', async ($, on) => {
+  const w = project();
+  await start($, on, w);
+  const refused = (id: string, command: string) =>
+    $.classic.PermissionDenied({
+      tool_name: 'Bash',
+      tool_input: { command },
+      tool_use_id: id,
+      reason: 'Permission for this action was denied by the Claude Code auto mode classifier.',
+    });
+  await refused('tu-1', 'pnpm db:generate');
+  await refused('tu-2', 'pnpm db:migrate');
+  // another command going through leaves both waiting
+  await $.tool.call({ tool: 'Bash', tool_use_id: 'tu-3', command: 'pnpm test' } as any);
+  let band = await bandUi($);
+  expect(await band.find({ type: 'Text', text: /^2 calls refused by Claude Code/ })).toBeDefined();
+  await band.unmount();
+  // the lead retries one and it goes through: only the other still waits
+  await $.tool.call({ tool: 'Bash', tool_use_id: 'tu-4', command: 'pnpm db:generate' } as any);
+  band = await bandUi($);
+  expect(
+    await band.find({ type: 'Text', text: "Claude Code refused the lead's `pnpm db:migrate`" }),
+  ).toBeDefined();
+  await band.unmount();
+  await $.tool.call({ tool: 'Bash', tool_use_id: 'tu-5', command: 'pnpm db:migrate' } as any);
+  band = await bandUi($);
+  expect(
+    await band.find({ type: 'Text', text: /Claude Code refused|refused by Claude Code/ }),
+  ).toBeUndefined();
+  await band.unmount();
+});
+
 test('CARD-8 two approvals waiting are two decisions, each approved or dropped on its own', async ($, on) => {
   const w = project();
   w.requests = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@warren-dean/code-kit",
-  "version": "0.15.0",
+  "version": "0.15.1",
   "description": "Keeps AI coding agents inside your project's rules: lanes, layer rules, protected paths and proof before finish, enforced by Claude Code hooks and in CI",
   "license": "MIT",
   "author": "Warren Langeveldt",

package/skills/spec-check/SKILL.md

@@ -5,7 +5,7 @@ description: Check a task against the project's specs before implementing it, an
 
 # Spec check
 
-The project's specs are in the folder named by `docs.specs` in `.claude/code-kit.json`. The engineering principles are in `docs.principles`, and the plan in `docs.plan`.
+The project's specs are in the folder named by `docs.specs` in `.claude/code-kit.json`. The engineering principles are in `docs.principles`, and the plan in `docs.plan`. Open the config with the Read tool. A shell script that reads it works too, but one that could write to it waits for a person's approval.
 
 ## Steps