codemuster 0.3.3 → 0.3.5

package/CHANGELOG.md

@@ -4,6 +4,33 @@ User-visible changes by released version. Add upcoming changes under Unreleased;
 move them to a dated version heading before publishing. Historical entries below
 start with 0.2.8.
 
+## 0.3.5 - 2026-09-21
+
+- A repair that cannot be integrated no longer ends the whole run. Previously one
+  such file cancelled every other worker mid-call, so a parallel `fix` could pay
+  for many agent calls and keep no repairs. The run now stops starting new
+  repairs, lets the calls already running finish, and retains each of those
+  repairs unapplied in its own worker checkout with the path reported, so they
+  can still be recovered. The file that could not be integrated is reported and
+  the command exits non-zero.
+- The message for a file changed outside the allowed scope during validation no
+  longer blames the configured test command. CodeMuster compares the checkout
+  before and after validation, so it now says the change came either from the
+  test command or from something else using the same checkout. Running `fix`
+  while another tool or agent writes to the same checkout is what produces this.
+
+## 0.3.4 - 2026-09-20
+
+- `codemuster fix` no longer stops the whole run when one file is too large for a
+  whole-file pack. Previously a single oversized file at the head of the queue
+  ended the run with nothing repaired. That file is now recorded as skipped with
+  its reason, every other file is still repaired and committed, the summary
+  reports the skipped count, and the exit code stays zero. Raise
+  `slice_token_budget` in `.codemuster/config.json` or split the file and the next
+  `fix` picks it up, with no extra flag and no rescan.
+- A file whose repair already completed is revisited when the audit later confirms
+  a finding in it that the repair never answered.
+
 ## 0.3.3 - 2026-09-19
 
 - Show the actual Codex model and thinking level before agent work by reading

package/README.md

@@ -149,6 +149,10 @@ are rejected and reported with a retained worker path. The untracked Impeccable
 excluded from the patch and does not block it. Without `test_command`, CodeMuster warns that
 it is accepting fixes without running your tests.
 
+A file whose whole-file pack exceeds `slice_token_budget` is skipped with its reason, counted in the
+run summary, and left unanalyzed without spending an attempt; the other files are still fixed.
+Raise `slice_token_budget` or split the file and the next `fix` picks it up with no flag.
+
 Retry declines through `fix --retry-declined`. For a repair spanning related files, select an
 exact primary `--path` and `--include-related path/to/caller,path/to/catalog -j 1`; all paths
 must be existing tracked files. The worker stays inside that explicit scope.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codemuster",
-  "version": "0.3.3",
+  "version": "0.3.5",
   "description": "CodeMuster: full-coverage codebase audits with a coverage number, driven by your coding agent through one skill.",
   "license": "SEE LICENSE IN LICENSE",
   "author": "Tim Carter",
@@ -37,11 +37,11 @@
     "test": "node --test test/launcher.test.js test/plugin.test.js test/release.test.js"
   },
   "optionalDependencies": {
-    "@codemuster/darwin-arm64": "0.3.3",
-    "@codemuster/darwin-x64": "0.3.3",
-    "@codemuster/linux-arm64": "0.3.3",
-    "@codemuster/linux-x64": "0.3.3",
-    "@codemuster/win32-arm64": "0.3.3",
-    "@codemuster/win32-x64": "0.3.3"
+    "@codemuster/darwin-arm64": "0.3.5",
+    "@codemuster/darwin-x64": "0.3.5",
+    "@codemuster/linux-arm64": "0.3.5",
+    "@codemuster/linux-x64": "0.3.5",
+    "@codemuster/win32-arm64": "0.3.5",
+    "@codemuster/win32-x64": "0.3.5"
   }
 }