@yeison.restrepo.r/code-conductor 1.52.7 → 1.52.9

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
@@ -498,7 +498,6 @@ The backup and temp rules keep the installer's own backups and crash-stranded te
498
498
  - **`[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.
499
499
  - **`[BUG-070]`, open:** the GitHub Actions workflows pin `actions/checkout` and `actions/setup-node` by tag rather than by commit SHA, so a moved tag would change what runs; the risk is low, since both actions are first-party and the records guard runs with a read-only token and no secrets. Until it is fixed, a fork can pin both actions to full commit SHAs in its own workflows.
500
500
  - **`[BUG-071]`, open:** the OpenCode guard plugin forwards only `command` from OpenCode's `bash` call, so if that tool runs a command in another working directory, Guard 3 evaluates it as if it ran in the project root. Until it is fixed, treat Guard 3 under OpenCode as best-effort for commands that set their own working directory.
501
- - **`[BUG-072]`, open:** the reserved list for recorded spec and plan folders misses root dot-directories outside `.claude` (such as `.husky`, `.vscode`, `.devcontainer`) and `bin`, `lib`, `tools`, so a `- Specs:` or `- Plans:` line in the project `CLAUDE.md` can make one of them the spec or plan agent's Guard 5 write scope. Until it is fixed, review any `- Specs:` or `- Plans:` line in the project `CLAUDE.md` and keep it pointing at a documentation folder.
502
501
  - **`[BUG-074]`, open:** the `/cc-orchestrate` role definitions disagree on when a task's tests are done: `code` may hand back `build_executed` on a red suite, `plan` requires each task to end green, and `qa` passes only on exit 0, so one suite result gates differently depending on the role. Until it is fixed, read a `build_executed` hand-back's reported suite exit code yourself and treat a non-zero one as not done.
503
502
  - **`[BUG-078]`, open:** `scripts/orchestrate.mjs` builds a fix round's write scope with the approved plan included, so Guard 5 lets the fix-round `code` agent write to the plan and only the brief's instruction stops it; any change other than checkbox ticks still halts the run with `ORCH_APPROVED_DOC_CHANGED` on the next `install audit` or fix round, and ticks do not affect `tasks.done`. Until it is fixed, check after a fix round that the approved plan's checkboxes are unchanged.
504
503
  - **`[BUG-079]`, open:** `scripts/orchestrate.mjs` stores every non-security hand-back's full SNAP in `.claude/memory/orchestrator-run.json` with a 64 KiB cap per SNAP but no cap on the total, so a plan of roughly 80 or more tasks with maximally sized hand-backs can push the run file past the hook's 10 MiB read cap, after which `readRunFile` returns null and Guard 6 downgrades from deny to warn for the rest of the run. Until it is fixed, keep orchestrated plans well under 80 tasks, or split a larger item into several runs.
@@ -242,6 +242,11 @@ const PLUGIN_IN_PLACE = new Set(['created', 'merged', 'unchanged']);
242
242
  // still backs up a copy the host edited before replacing it (BUG-069).
243
243
  const replaceWithTemplate = (templateText, hostText) => ({ text: templateText, changed: hostText !== templateText });
244
244
 
245
+ // The link text comes from the checkout, so a raw control character in it could erase or
246
+ // forge installer output; C1 is included because U+009B acts as CSI on some terminals (BUG-088).
247
+ const escapeControlChars = (text) =>
248
+ text.replace(/[\x00-\x1f\x7f-\x9f]/g, (c) => `\\x${c.charCodeAt(0).toString(16).padStart(2, '0')}`);
249
+
245
250
  // The plugin is a managed asset, so a link at its path is removed, never followed:
246
251
  // writing through it would overwrite whatever file the checkout points it at (BUG-087).
247
252
  // Returns false when the link is still there, so nothing may be written.
@@ -257,7 +262,7 @@ function removePluginSymlink(pluginPath, warn) {
257
262
  warn(`code-conductor: skipping ${OPENCODE_PLUGIN} — it is a symlink and could not be removed (${err.code}); nothing was written`);
258
263
  return false;
259
264
  }
260
- warn(`code-conductor: replaced the symlink at ${OPENCODE_PLUGIN} (it pointed to ${linkText}) with the shipped plugin; the file it pointed to was not touched`);
265
+ warn(`code-conductor: replaced the symlink at ${OPENCODE_PLUGIN} (it pointed to ${escapeControlChars(linkText)}) with the shipped plugin; the file it pointed to was not touched`);
261
266
  return true;
262
267
  }
263
268
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yeison.restrepo.r/code-conductor",
3
- "version": "1.52.7",
3
+ "version": "1.52.9",
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",
@@ -24,11 +24,14 @@ export const DIR_MAX = V3_CAPS['ops.scope'][1] - (GROUP_MAX + '/'.length + '/**'
24
24
 
25
25
  const CODE = 'ORCH_DOC_LOCATION_INVALID';
26
26
  // A recorded folder becomes the spec and plan agents' Guard 5 write scope, so it may not cover
27
- // the orchestrator write surface, git internals, or any folder that holds enforcement code
28
- // (`.opencode` holds the OpenCode guard). Inside `.claude`, only specs and plans may hold
29
- // documents: everything else there is agent instructions or configuration (skills, settings,
30
- // rules), so the rule below it is an allowlist, not this deny list.
31
- const RESERVED = ['.claude/memory', '.claude/hooks', '.claude/agents', '.claude/commands', '.claude/scripts', '.conductor', '.git', '.github', '.opencode', 'scripts'];
27
+ // the orchestrator write surface, git internals, any folder that holds enforcement code
28
+ // (`.opencode` holds the OpenCode guard), or a conventional code folder (`bin`, `lib`, `tools`).
29
+ // Inside `.claude`, only specs and plans may hold documents: everything else there is agent
30
+ // instructions or configuration (skills, settings, rules), so that rule is an allowlist, not
31
+ // this deny list. Every other root dot-directory is refused as a class (BUG-072): tools run
32
+ // what `.husky`, `.vscode` or `.devcontainer` hold on their own, and the class is open-ended,
33
+ // so no list of names can close it.
34
+ const RESERVED = ['.claude/memory', '.claude/hooks', '.claude/agents', '.claude/commands', '.claude/scripts', '.conductor', '.git', '.github', '.opencode', 'bin', 'lib', 'scripts', 'tools'];
32
35
  const CLAUDE_DOCS = ['.claude/specs', '.claude/plans'];
33
36
  const GROUP_RE = /^(#{1,5})\s+(phase|epic|pillar)\b[\s:#-]*(\d+)?[\s:.-]*(.*)$/i;
34
37
  const HEADING_RE = /^(#{1,6})\s/;
@@ -57,6 +60,10 @@ function reservedReason(value) {
57
60
  if (underRoot(folded, '.claude') && !CLAUDE_DOCS.some((ok) => underRoot(folded, ok))) {
58
61
  return 'sits in `.claude`, where only `.claude/specs` and `.claude/plans` may hold documents';
59
62
  }
63
+ const rootSegment = folded.split('/')[0];
64
+ if (rootSegment.startsWith('.') && rootSegment !== '.claude') {
65
+ return `sits in the root dot-directory \`${rootSegment}\`; among root dot-directories only \`.claude/specs\` and \`.claude/plans\` may hold documents`;
66
+ }
60
67
  return '';
61
68
  }
62
69