@yeison.restrepo.r/code-conductor 1.52.0 → 1.52.2
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 +4 -2
- package/package.json +3 -3
- package/scripts/adopt-claude-md.mjs +11 -1
- package/scripts/orchestrate.mjs +11 -2
package/README.md
CHANGED
|
@@ -483,7 +483,7 @@ The backup and temp rules keep the installer's own backups and crash-stranded te
|
|
|
483
483
|
| `systemMessage` | `default` | yes, for example Guard 2's overwrite prompt | no: the warning is lost |
|
|
484
484
|
- Agent definitions provided by plugins are not searched.
|
|
485
485
|
- `resume` (`[FEAT-055]`) needs approvals that recorded their commit: a run approved before it is refused `ORCH_RESUME_UNANCHORED` and still needs `end`, then `start`, and a Build task entry without a stored SNAP is redone.
|
|
486
|
-
- Unattended mode (`[FEAT-054]`) binds the agents, not the orchestrator session: the run file is inside the orchestrator's write surface, so a hand edit could set `unattended` just as it could forge an approval, and Guard 6 does not stop it. Its deterministic plan check covers only the orchestrator write surface and the control-plane files (`[BUG-080]`); every other judgement is the delegated reviewer's.
|
|
486
|
+
- Unattended mode (`[FEAT-054]`) binds the agents, not the orchestrator session: the run file is inside the orchestrator's write surface, so a hand edit could set `unattended` just as it could forge an approval, and Guard 6 does not stop it. Its deterministic plan check covers only the orchestrator write surface, any `Files` entry outside printable ASCII (`[BUG-086]`) and the control-plane files, including those that run code outside the run (`[BUG-080]`, `[BUG-081]`); every other judgement is the delegated reviewer's.
|
|
487
487
|
|
|
488
488
|
The five role agent definitions it dispatches ship from `1.37.0`; their limits are the next item.
|
|
489
489
|
- **The role agents (`1.37.0`) are bounded by their tool masks, and Guard 7 bounds one thing beneath them: the shell.**
|
|
@@ -500,12 +500,14 @@ The backup and temp rules keep the installer's own backups and crash-stranded te
|
|
|
500
500
|
- **`[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.
|
|
501
501
|
- **`[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.
|
|
502
502
|
- **`[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.
|
|
503
|
-
- **`[BUG-073]`, open:** the publish workflow installs and runs dev dependencies (`npm ci`, `npx vitest run`) in the same job that holds `id-token: write` for `npm publish --provenance`, while the dev dependency tree carries high and critical audit advisories; runtime dependencies are empty, so installs are unaffected. Until it is fixed, the exposure is limited to the maintainer's tag-triggered publish job; users need no action.
|
|
504
503
|
- **`[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.
|
|
505
504
|
- **`[BUG-075]`, open:** `scripts/orchestrate.mjs` validates only the shape of a role hand-back, so it accepts a `build_executed` whose report says the suite failed or whose `ops.f` lists out-of-scope paths, lets `end` close a run with no `verify_pass`, and stamps an approval with the global `git config user.name`; Guards 5 and 7 still block the out-of-scope writes themselves. Until it is fixed, check that a run reached `verify_pass` before trusting its record, and do not read the approval name as proof of who approved.
|
|
506
505
|
- **`[BUG-077]`, open:** `scripts/orchestrate.mjs` lets `approve spec <path> <sha256>` accept any file path relative to the run root, without checking that it is the spec the `spec` role handed back or that it sits under the run's `docs.specs` folder, so approving the wrong path makes the post-approval hash check in `install` protect that file while later edits to the real spec go undetected. Until it is fixed, confirm that the path you approve is the spec the `spec` role handed back, under the run's recorded specs folder.
|
|
507
506
|
- **`[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.
|
|
508
507
|
- **`[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.
|
|
508
|
+
- **`[BUG-082]`, open:** the unattended plan check escalates only the root, `.claude/` and `project-template/` `CLAUDE.md` files, so in an `--unattended` run a delegated plan can write a nested `CLAUDE.md` (such as `src/CLAUDE.md`) whose content can reach later reviewers in the same run; hooks and guards are unaffected. Until it is fixed, check an `--unattended` run's diff for new or changed `CLAUDE.md` or `CLAUDE.local.md` files in subdirectories.
|
|
509
|
+
- **`[BUG-083]`, open:** the `publish` job in `.github/workflows/publish.yml` avoids an npm cache only by omitting `cache:` from `actions/setup-node`, which v5+ overrides when `package.json` declares a `packageManager` (or `devEngines.packageManager`) field; no such field exists today, so there is no current impact, but adding one would let the job holding `id-token: write` restore a cache the `verify` job populated. Until it is fixed, do not add a `packageManager` or `devEngines.packageManager` field to `package.json`, or set `package-manager-cache: false` on the `publish` job's `setup-node` step in a fork.
|
|
510
|
+
- **`[BUG-085]`, open:** the unattended plan check's `CONTROL_PLANE` list in `scripts/orchestrate.mjs` does not yet cover config-read hook runners, editor and container auto-run configuration, other package managers' files or other CI systems, so in an `--unattended` run a plan approved only by the delegated review can write files that run code outside the run. Until it is fixed, check an `--unattended` run's diff for changes to such files before committing, opening the project in an editor or container, installing dependencies or pushing.
|
|
509
511
|
- **The `P7` false positive** described under [Guard 3, and what it learned](#guard-3-and-what-it-learned) is still live.
|
|
510
512
|
- **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.
|
|
511
513
|
- **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.52.
|
|
3
|
+
"version": "1.52.2",
|
|
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",
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"coverage": "vitest run --coverage"
|
|
43
43
|
},
|
|
44
44
|
"devDependencies": {
|
|
45
|
-
"@vitest/coverage-v8": "^
|
|
46
|
-
"vitest": "^
|
|
45
|
+
"@vitest/coverage-v8": "^4.1.12",
|
|
46
|
+
"vitest": "^4.1.12"
|
|
47
47
|
}
|
|
48
48
|
}
|
|
@@ -220,7 +220,17 @@ function main([command, file, planFile, token]) {
|
|
|
220
220
|
throw new AdoptError('usage: adopt-claude-md.mjs sections|render|apply <file> [plan.json] [token]');
|
|
221
221
|
}
|
|
222
222
|
|
|
223
|
-
|
|
223
|
+
// Node's ESM loader sets import.meta.url to the module's realpath, so argv[1] must be
|
|
224
|
+
// realpath-resolved too, or a launch through a symlinked directory skips the main block.
|
|
225
|
+
function invokedDirectly() {
|
|
226
|
+
const argv1 = process.argv[1];
|
|
227
|
+
if (!argv1) return false;
|
|
228
|
+
let resolved;
|
|
229
|
+
try { resolved = fs.realpathSync(argv1); } catch { resolved = argv1; }
|
|
230
|
+
return import.meta.url === pathToFileURL(resolved).href;
|
|
231
|
+
}
|
|
232
|
+
|
|
233
|
+
if (invokedDirectly()) {
|
|
224
234
|
try { main(process.argv.slice(2)); } catch (err) {
|
|
225
235
|
if (!(err instanceof AdoptError)) throw err;
|
|
226
236
|
console.error(`ERROR: ${err.message}`);
|
package/scripts/orchestrate.mjs
CHANGED
|
@@ -22,6 +22,7 @@ export const ENVELOPE_FILE = '.claude/memory/band-envelope.json';
|
|
|
22
22
|
export const WRITE_SURFACE = [RUN_FILE, ENVELOPE_FILE, '.claude/memory/session-snapshot.json', '.conductor/**'];
|
|
23
23
|
// Owner decision (BUG-080): the files that enforce the guards or steer later dispatches, in both mirrors. Same notation
|
|
24
24
|
// as WRITE_SURFACE; a trailing `/**` protects the whole directory, so a file added to it is covered too.
|
|
25
|
+
// Owner decision (BUG-081): also the files that run code outside the run, after it ends.
|
|
25
26
|
export const CONTROL_PLANE = [
|
|
26
27
|
'.claude/hooks/**', 'project-template/.claude/hooks/**',
|
|
27
28
|
'.opencode/plugin/**', 'project-template/.opencode/plugin/**',
|
|
@@ -35,6 +36,11 @@ export const CONTROL_PLANE = [
|
|
|
35
36
|
// The router, the three modules it imports at load time, and the scan; the installer deploys them to .claude/scripts/.
|
|
36
37
|
'scripts/orchestrate.mjs', 'scripts/snap-contract.mjs', 'scripts/ticket.mjs', 'scripts/doc-locations.mjs', 'scripts/security-scan.mjs',
|
|
37
38
|
'.claude/scripts/**',
|
|
39
|
+
// BUG-081: these run code after the run ends (git, MCP and OpenCode servers, the status line, CI, npm).
|
|
40
|
+
'.git/**', '.husky/**', '.githooks/**', '.mcp.json', 'opencode.json', 'opencode.jsonc',
|
|
41
|
+
'.claude/flow-status.mjs', 'project-template/.claude/flow-status.mjs',
|
|
42
|
+
'.github/workflows/**', '.github/actions/**',
|
|
43
|
+
'package.json', 'package-lock.json', 'npm-shrinkwrap.json', '.npmrc',
|
|
38
44
|
];
|
|
39
45
|
// Where /cc-orchestrate writes each agent's final message for `handback` to read: inside
|
|
40
46
|
// the surface, and cleared with the run so file names never collide across runs.
|
|
@@ -1071,11 +1077,14 @@ function reachesList(glob, list) {
|
|
|
1071
1077
|
const taskGlob = (entry) => entry.replace(/^\.\//, '').toLowerCase();
|
|
1072
1078
|
// NTFS aliases one file under other spellings: a data stream, an 8.3 short name, a trailing dot or space.
|
|
1073
1079
|
const ntfsAlias = (glob) => glob.split('/').some((seg) => /[:~]|[. ]$/.test(seg));
|
|
1080
|
+
// Outside printable ASCII, no lexical test can tell which file a filesystem or tool resolves; tested before taskGlob
|
|
1081
|
+
// folds case, because toLowerCase maps some of these characters to ASCII (U+212A KELVIN SIGN to `k`).
|
|
1082
|
+
const nonAscii = (entry) => /[^\x20-\x7e]/.test(entry);
|
|
1074
1083
|
function inSurface(entry) {
|
|
1075
1084
|
const glob = taskGlob(entry);
|
|
1076
|
-
return ntfsAlias(glob) || reachesList(glob, WRITE_SURFACE);
|
|
1085
|
+
return nonAscii(entry) || ntfsAlias(glob) || reachesList(glob, WRITE_SURFACE);
|
|
1077
1086
|
}
|
|
1078
|
-
// No alias test: surfaceTask runs inSurface first, and it escalates every alias.
|
|
1087
|
+
// No alias or non-ASCII test: surfaceTask runs inSurface first, and it escalates every alias and every non-ASCII entry.
|
|
1079
1088
|
const inControlPlane = (entry) => reachesList(taskGlob(entry), CONTROL_PLANE);
|
|
1080
1089
|
|
|
1081
1090
|
// Owner decisions (FEAT-054, BUG-080): a plan whose task would write the run's own record, or the files that enforce
|