@lyupro/codex-bridge 0.6.14 → 0.6.15

package/CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.6.15] - 2026-10-12
+
+### Fixed
+
+- The `codex-bridge guidance order` topic and the instruction given to Codex itself now name all six folders a
+  build scope may never include, `.omc/` among them. Both had dropped it, so an orchestrator could be refused for a
+  folder its guidance never mentioned, and Codex was never told the folder was off limits. The scope check, the
+  verdict and the Codex instruction now share one list, and a repository test fails when any complete list in the
+  docs falls out of step with it.
+
 ## [0.6.14] - 2026-10-11
 
 ### Added

package/README.md

@@ -62,7 +62,7 @@ Run records in `~/.lyupro/.codex-bridge/runs/` (or `~/.claude/codex-runs/` befor
 - **Every run leaves an audit folder.** The verbatim task, scope, before/after git state, events, report, verdict, and reason remain together.
 - **Zero runtime dependencies and zero build steps.** The package is plain `.mjs` on the Node.js standard library.
 
-The current suite contains **3654 automated tests: 3651 passing and 3 skipped**.
+The current suite contains **3664 automated tests: 3661 passing and 3 skipped**.
 
 ## Verify
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lyupro/codex-bridge",
-  "version": "0.6.14",
-  "description": "Claude Code-to-Codex delegation with 8 guards, 3654 tests, zero runtime dependencies, and zero build steps.",
+  "version": "0.6.15",
+  "description": "Claude Code-to-Codex delegation with 8 guards, 3664 tests, zero runtime dependencies, and zero build steps.",
   "keywords": [
     "claude-code",
     "codex",

package/src/home/guidance/order.md

@@ -36,7 +36,9 @@ Keep header values short and free of forbidden shell sequences. Empty or placeho
 
 `scope new`: Comma-separated globs for new files this build may create, relative to the repository root.
 `scope` must declare at least one existing path pattern; `scope new` does not replace it.
-Never name service folders in scope: `.git/`, `.claude/`, `.codex/`, `.omx/`, `node_modules/`.
+<!-- service-folders:begin -->
+Never name service folders in scope: `.git/`, `.claude/`, `.codex/`, `.omx/`, `.omc/`, `node_modules/`.
+<!-- service-folders:end -->
 
 Example build header:
 

package/src/home/lib/meta/paths.mjs

@@ -89,7 +89,12 @@ export const changedPaths = (before, after) => {
 };
 
 /** Directories a delegated build has no business editing, whatever the task says. */
-export const SERVICE_RE = /^(\.omx|\.omc|\.claude|\.codex|\.git|node_modules)\//;
+export const SERVICE_FOLDERS = Object.freeze([
+  '.omx', '.omc', '.claude', '.codex', '.git', 'node_modules',
+]);
+export const SERVICE_RE = new RegExp(
+  `^(${SERVICE_FOLDERS.map((name) => name.replace(/[.*+?^${}()|[\]\\]/g, '\\$&')).join('|')})/`,
+);
 
 /**
  * Paths arrive from two sides that spell them differently: git prints repo-relative with

package/src/home/lib/runner/prompts.mjs

@@ -8,6 +8,7 @@
  * (`…cli/install.mjs:` + U+0000) and 2026-09-28 (`…(docs/plans/Plan_` + `恋`).
  */
 import { DEFAULTS } from '../run-config.mjs';
+import { SERVICE_FOLDERS } from '../meta/paths.mjs';
 import { RUN_ENV } from './run-env.mjs';
 import { advisorSchema, schemaFor } from './schemas.mjs';
 import { QUESTION_KIND } from './question-kind.mjs';
@@ -140,8 +141,7 @@ Working rules:
   (\`dir/{a,b}.ts\`), and lists separated by \`;\` or \`,\` are prohibited: a collapsed entry will
   match no file when the report is checked against the worktree and will fail the run even if
   the work was done honestly.
-- Do not fix the environment. Service directories (\`.omx/\`, \`.claude/\`, \`.codex/\`, \`.git/\`,
-  \`node_modules/\`) and other sessions are not your task, even if they prevent you from working
+- Do not fix the environment. Service directories (${SERVICE_FOLDERS.map((name) => `\`${name}/\``).join(', ')}) and other sessions are not your task, even if they prevent you from working
   or finishing. Put the obstacle in leftovers instead of changing them.
 - report_markdown is a full markdown report with sections: “What was done”, “Changes”
   (file / what changed / why table), “Verification” (command and its actual output),