@yeison.restrepo.r/code-conductor 1.52.10 → 1.52.11
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
|
@@ -499,7 +499,6 @@ The backup and temp rules keep the installer's own backups and crash-stranded te
|
|
|
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
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.
|
|
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.
|
|
503
502
|
- **The `P7` false positive** described under [Guard 3, and what it learned](#guard-3-and-what-it-learned) is still live.
|
|
504
503
|
- **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.
|
|
505
504
|
- **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.11",
|
|
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",
|
|
@@ -5,7 +5,7 @@ tools: Read, Grep, Glob, Write, Edit, Bash
|
|
|
5
5
|
default-model: sonnet
|
|
6
6
|
---
|
|
7
7
|
|
|
8
|
-
You are the `code` role of a code-conductor orchestrated run. The orchestrator dispatched you with a brief naming one task of the approved plan, and installed your band envelope at `.claude/memory/band-envelope.json`. Read the envelope first: its `ops.scope` is the task's files plus the plan file.
|
|
8
|
+
You are the `code` role of a code-conductor orchestrated run. The orchestrator dispatched you with a brief naming one task of the approved plan, and installed your band envelope at `.claude/memory/band-envelope.json`. Read the envelope first: its `ops.scope` is the task's files plus the plan file; in a fix round it is the files the review names, without the plan.
|
|
9
9
|
|
|
10
10
|
## Your job
|
|
11
11
|
|
package/scripts/orchestrate.mjs
CHANGED
|
@@ -321,24 +321,30 @@ export function extractTasks(planText) {
|
|
|
321
321
|
}
|
|
322
322
|
|
|
323
323
|
// D9: an empty scope is a plan defect, never a read-only fallback; scopes are never truncated.
|
|
324
|
-
|
|
325
|
-
|
|
326
|
-
|
|
324
|
+
// The empty check reads the declared files, so the plan alone never passes as a task's scope.
|
|
325
|
+
function checkedScope(id, files, added) {
|
|
326
|
+
if (files.length === 0) throw new Halt('ORCH_EMPTY_SCOPE', `${id} declares no files`);
|
|
327
|
+
const scope = [...new Set([...files, ...added])];
|
|
327
328
|
const [cap, elemCap] = V3_CAPS['ops.scope'];
|
|
328
|
-
if (scope.length > cap) throw new Halt('ORCH_SCOPE_OVER_CAP', `${
|
|
329
|
+
if (scope.length > cap) throw new Halt('ORCH_SCOPE_OVER_CAP', `${id} needs ${scope.length} scope entries; the cap is ${cap}`);
|
|
329
330
|
const long = scope.find((p) => elementLength(p) > elemCap);
|
|
330
|
-
if (long) throw new Halt('ORCH_SCOPE_OVER_CAP', `${
|
|
331
|
+
if (long) throw new Halt('ORCH_SCOPE_OVER_CAP', `${id} has a ${elementLength(long)}-character path; the cap is ${elemCap}`);
|
|
331
332
|
return scope;
|
|
332
333
|
}
|
|
333
334
|
|
|
335
|
+
export function taskScope(task, planRel) {
|
|
336
|
+
return checkedScope(task.id, task.files, [planRel]);
|
|
337
|
+
}
|
|
338
|
+
|
|
334
339
|
// FEAT-057: the audit text is not owner-approved, so it may name only files the approved plan's tasks
|
|
335
340
|
// declare, never the approved documents themselves (owner decision, 2026-11-13).
|
|
341
|
+
// A fix round ticks no boxes, so the plan stays out of its write scope and Guard 5 enforces that (BUG-078).
|
|
336
342
|
function fixScope(root, run, files, round) {
|
|
337
343
|
const planned = new Set(extractTasks(readDoc(root, run.plan, `cannot read ${run.plan}`).toString('utf8')).flatMap((t) => t.files));
|
|
338
344
|
const approved = [run.plan, run.approvals.spec?.path];
|
|
339
345
|
const outside = files.find((p) => typeof p !== 'string' || !planned.has(p) || approved.includes(p));
|
|
340
346
|
if (outside !== undefined) throw new Halt('ORCH_FIX_SCOPE_UNAPPROVED', `${outside} is not a file the approved plan declares; the fix scope stays inside the plan`);
|
|
341
|
-
return
|
|
347
|
+
return checkedScope(`fix round ${round}`, files, []);
|
|
342
348
|
}
|
|
343
349
|
|
|
344
350
|
// FEAT-047: one glob per role, checked against the element cap once, at start.
|