@yeison.restrepo.r/code-conductor 1.52.8 → 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
@@ -501,7 +501,6 @@ The backup and temp rules keep the installer's own backups and crash-stranded te
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
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
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.
504
- - **`[BUG-088]`, open:** when `code-conductor --opencode` replaces a symlink at `.opencode/plugin/conductor-guard.js`, `lib/installer/deploy.mjs` prints the old link text to stderr verbatim, so a crafted checkout's link target can carry ANSI escape sequences or newlines that spoof or hide part of the installer's terminal output; it does not execute code or write files. Until it is fixed, inspect that path (`ls -l .opencode/plugin/conductor-guard.js`) in an untrusted checkout before installing with `--opencode`, and do not trust installer output that follows a symlink-replacement warning.
505
504
  - **The `P7` false positive** described under [Guard 3, and what it learned](#guard-3-and-what-it-learned) is still live.
506
505
  - **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.
507
506
  - **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.
@@ -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.8",
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",