omp-conductor 0.3.6 → 0.3.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omp-conductor",
-  "version": "0.3.6",
+  "version": "0.3.7",
   "type": "module",
   "license": "MIT",
   "description": "A 24/7 dispatcher that takes ready GitHub issues to green, mergeable PRs using omp coding sessions, with tiered escalation first to an orchestrator session and then to a human.",

package/src/worktree.ts

@@ -102,15 +102,27 @@ const EXCLUDE_END = "# <<< omp-conductor";
 
 /**
  * Appended to every mirror's `info/exclude`, and so in force in every worktree
- * cut from it. Deliberately the same shapes salvage therefore skips, and
- * for the same reason — a worker's own scaffolding is not the repo's business.
+ * cut from it: a worker's own scaffolding is not the repo's business, and
+ * keeping it out of `git status` keeps it out of the worker's own `git add -A`
+ * as well as out of salvage.
  *
- * Two layers because they catch different moments: this one keeps scratch out
- * of a worker's own `git add -A` and out of its `git status`, which salvage
- * never observes; the salvage list catches whatever a worker created before
- * this landed, or wrote past an ignore with `add -f`.
+ * **Only the directory form of `.scratch*`; the slash is the design.** An ignore
+ * here applies to every repo this fleet touches, and an ignored *new* file is
+ * invisible to salvage — `git add -A` skips it, and a tree holding only such
+ * files reports `nothing`. So a name that could plausibly be a deliverable must
+ * never appear in this list. The first version also carried `.env.local` and
+ * `*.local.sh`; its first correction still carried an unqualified `.scratch*`.
+ * All three make the same mistake: repos can legitimately ship an `.env.local`
+ * template, `bootstrap.local.sh`, `.scratchrc`, or `.scratchpad`, and a worker
+ * asked to add one would watch it vanish.
+ *
+ * The directory-only pattern survives because its trailing slash limits it to a
+ * directory whose name announces that its contents are disposable. That was
+ * the 2026-08-07 incident's exact shape (`.scratch82/env.sh`). Broader
+ * conventions belong in a repo's own `.gitignore`, where its operator chooses
+ * them, rather than being imposed by whatever dispatcher happens to be driving.
  */
-const LOCAL_EXCLUDE = [".scratch*/", ".scratch*", ".env.local", "*.local.sh"];
+const LOCAL_EXCLUDE = [".scratch*/"];
 
 /**
  * Adds the managed block to an `info/exclude`, preserving everything else.