@yeison.restrepo.r/code-conductor 1.39.2 → 1.39.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -457,7 +457,6 @@ The backup and temp rules keep the installer's own backups and crash-stranded te
457
457
  - **`[BUG-057]`, open:** `.claude/memory/project.md` is append-only and the phase commands instruct a full read of it, which collides with Guard 1's 150-line read limit once the file grows; on a long-lived project the read cost rises with project age. Until it is fixed, prune or archive old checkpoint sections by hand when the file gets large.
458
458
  - **`[BUG-058]`, open:** the test suite does not pass on a Windows checkout (CRLF checkout of `.mjs` files, `--import` given a bare path, symlink and `chmod` fixtures, `spawnSync('npm')` without a shell), and CI has no Windows leg to show it. Until it is fixed, develop against the suite on Linux/macOS or WSL; the shipped product itself is unaffected.
459
459
  - **`[BUG-059]`, open:** the test helper that fakes the `gh` CLI is POSIX-only, so on a Windows machine where the suites load, tests can reach a real, logged-in `gh` and perform live GitHub writes. Until it is fixed, do not run `npm test` on Windows while authenticated to `gh`, or log out (`gh auth logout`) first.
460
- - **`[BUG-061]`, open:** the PreToolUse hook command is a cwd-relative `node .claude/hooks/pre-tool-use.mjs`, so on Windows nearly every tool call can report a non-blocking `node:internal/modules/cjs/loader` error, and the guards are skipped for that call. Until it is fixed, keep the session's working directory at the project root.
461
460
  - **The `P7` false positive** described under [Guard 3, and what it learned](#guard-3-and-what-it-learned), still live.
462
461
  - **A re-run against an untouched `project.md` prints a recovery hint it cannot prove is needed.** If you install, never write anything into `.claude/memory/project.md`, and install again, you get a line suggesting the file may have been overwritten by a pre-`1.30.0` re-run. It was not; it equals the stub because it was seeded and never edited. The check compares content and **cannot distinguish "seeded and untouched" from "clobbered"**, which is why the wording is hedged to "may have been" rather than "was". This residual is named and accepted in [`BUG-039`'s spec at `:129`](docs/superpowers/specs/2026-09-27-bug039-installer-host-owned-state-design.md), where the alternative (restoring from the host's own git history) was rejected as writing host files out of the host's history with new failure modes. A **fresh** install is silent, which the Quickstart shows.
463
462
  - **Three open dossiers**, which are the evidence-collection pipeline working rather than a backlog: a session denial tally, one for interleaved-artifact reports, and an intermittent commit-hook hang in the `snap-build` suite. A dossier holds specimens until a mechanism is characterized by probe; an id is minted only when the written condition is met. `[BUG-047]` is what that pipeline produces when it completes: an out-of-scope note, then a dossier, then four specimens across four sessions, then a mint, then a release.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yeison.restrepo.r/code-conductor",
3
- "version": "1.39.2",
3
+ "version": "1.39.3",
4
4
  "description": "A governance layer for Claude Code sessions: hooks that check an agent's commands before they run, a spec-first workflow, and project memory the next session reads.",
5
5
  "keywords": [
6
6
  "agentic-development",
@@ -86,7 +86,7 @@ Run `/cc-checkpoint`. Persist current architectural state to `.claude/memory/pro
86
86
 
87
87
  ## Step 5 — Hook integrity check
88
88
 
89
- Verify `.claude/hooks/pre-tool-use.mjs` exists. It is launched as `node <path>`, so it needs no execute bit:
89
+ Verify `.claude/hooks/pre-tool-use.mjs` exists. It is loaded by `node` through the PreToolUse command in `.claude/settings.json`, so it needs no execute bit:
90
90
 
91
91
  ```bash
92
92
  HOOK=".claude/hooks/pre-tool-use.mjs"
@@ -622,10 +622,12 @@ const G3_CHECKS = [
622
622
  // Present-but-unreadable means an empty list PLUS a debug line, because that is a
623
623
  // fault worth seeing, and neither condition may throw: a permissions problem on a
624
624
  // policy file must never escalate into denying every tool call in the session.
625
+ // The root is CLAUDE_PROJECT_DIR because the session's cwd drifts; cwd is only the
626
+ // fallback for a launcher that does not set it (BUG-061).
625
627
  function g3ReadAllowlist() {
626
628
  let raw;
627
629
  try {
628
- raw = readFileSync(join(process.cwd(), ...G3_ALLOWLIST_REL), 'utf8');
630
+ raw = readFileSync(join(process.env.CLAUDE_PROJECT_DIR || process.cwd(), ...G3_ALLOWLIST_REL), 'utf8');
629
631
  } catch (e) {
630
632
  if (e.code !== 'ENOENT') debug(`guard 3 allowlist unreadable: ${e.message}`);
631
633
  return [];
@@ -6,7 +6,7 @@
6
6
  "hooks": [
7
7
  {
8
8
  "type": "command",
9
- "command": "node .claude/hooks/pre-tool-use.mjs"
9
+ "command": "node --input-type=commonjs -e \"import(require('url').pathToFileURL(require('path').resolve(process.env.CLAUDE_PROJECT_DIR||'.','.claude/hooks/pre-tool-use.mjs')).href)\""
10
10
  }
11
11
  ]
12
12
  }