hexcli 2.14.0__tar.gz → 2.16.0__tar.gz

{hexcli-2.14.0 → hexcli-2.16.0}/CHANGELOG.md

@@ -4,6 +4,63 @@ Full evidence for every claim below — including the experiments that failed
 lives in `docs/V2_PLAN.md` §14. Numbers are pass^k over repeated live runs on
 the Hexagon NPU, not single-run anecdotes.
 
+## 2.16.0 — 2026-09-18
+
+A minor release: a tool result the model reads changes (`find_files` returns
+a listing where it returned an argument error).
+
+> **Gate: PASS** on the pinned 24-case set after one recheck (`agentic-4`
+> and `agentic-5`, neither of which calls `find_files`, missed once at 5
+> runs and then held at 6). Own arm, fresh server, seed 20260918, 8 invalid
+> of 245 runs. Against the v2.11.1 12-run baseline: run-level 402/514 vs
+> 174/222, +0.2 %, Fisher p = 1.00; pass^k 26 → 30 of 46 shared cases,
+> McNemar p = 0.29. **The alias did not fire in this arm**: all ten
+> `find_files` calls carried `glob` (two also sent `pattern`, and `glob`
+> won as designed), so the arm is evidence of no regression, and the case
+> for the change rests on the 21 of 170 recorded calls that would have
+> hit it. `findfile-1` 2/5, all three misses the decoy answer, which is
+> the separate finding still open. Smoke 10/10 on a fresh server.
+
+- `find_files` takes `pattern` as its glob when no `glob` is sent. The
+  model names the file under the key `search_files` uses in 21 of the 170
+  `find_files` calls on record, across eight cases and one of the owner's
+  sessions, and each one came back "find_files requires 'glob'". In the
+  2.12.0 arm three of `findfile-1`'s twelve runs spent two to three steps
+  on it and one reached the step limit that way. The value is what the
+  model meant to look for either way, and a bare name is a valid glob for
+  that exact name; `glob` still wins when both are sent, and a call with
+  neither is still an error.
+
+## 2.15.0 — 2026-09-18
+
+A minor release: one tool error the model reads is new (`edit_file` on
+identical strings).
+
+> **Gate: PASS** on the pinned 24-case set after one recheck (`agentic-5`
+> 4/5, a counting answer with no edit in it, then 6/6). Own arm, fresh
+> server, seed 20260917, 9 invalid of 245 runs. Against the v2.11.1 12-run
+> baseline: run-level 402/514 vs 172/221, −0.4 %, Fisher p = 0.92; pass^k
+> 26 → 28 of 46 shared cases, McNemar p = 0.63. The error fired in the arm
+> on 3 `tests-claim-1` runs and nowhere else; that case went 4/5 against
+> 12/24 (p = 0.34, ceiling). `self-correct-1` read 2/5 in the arm on a
+> server 75 minutes into its traffic (the arm's invalid runs were climbing),
+> and the error had not fired in any of its runs; a paired control on a
+> fresh server, ten runs each on the parent tree and this one, came back
+> **10/10 vs 9/10, p = 1.0**. In the one control run where the error did
+> fire the model had sent a hallucinated `main()` as both strings, was told
+> nothing changed, read the file, and then made the real fix. Smoke miss
+> on `agentic-2` re-measured 9/10 against its recorded 75 %.
+
+- `edit_file` refuses an edit whose `old_string` and `new_string` are the
+  same text, instead of answering "Edited". 37 of the 840 `edit_file` calls
+  on record sent identical strings and were told the edit landed; the model
+  then ran or read the file believing it had changed it (`tests-claim-1`:
+  "The median function was correctly fixed", after an edit of `mean` to
+  itself; `runit-1` before 2.14.0: the broken line edited to itself, twice,
+  to the step limit). The tool now says nothing changed and what to send
+  instead, and leaves the file byte-identical. A missing file still reports
+  the path first.
+
 ## 2.14.0 — 2026-09-17
 
 A minor release: one tool behaves differently for the model (a `write_file`

{hexcli-2.14.0 → hexcli-2.16.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: hexcli
-Version: 2.14.0
+Version: 2.16.0
 Summary: Local Hexagon NPU terminal agent for Snapdragon X Elite Windows ARM64
 Project-URL: Homepage, https://github.com/NathanL15/Hex-CLI
 Project-URL: Repository, https://github.com/NathanL15/Hex-CLI

{hexcli-2.14.0 → hexcli-2.16.0}/hexcli/__init__.py

@@ -3,4 +3,4 @@
 # The one place the version is written. pyproject.toml reads it (hatch
 # dynamic version), agent.VERSION re-exports it, and CI refuses a release
 # tag that does not match it.
-__version__ = "2.14.0"
+__version__ = "2.16.0"

{hexcli-2.14.0 → hexcli-2.16.0}/hexcli/agent.py

@@ -826,7 +826,12 @@ def execute_tool_call(config: dict[str, Any], action: dict[str, Any], shell_exe:
             raise RuntimeError("search_files requires 'pattern'.")
         return search_files_tool(pattern, path, glob_pat, limit)
     if tool == "find_files":
-        glob_pat = str(args.get("glob") or "").strip()
+        # 21 of the 170 find_files calls on record (2026-09-17) sent the
+        # name under "pattern", the key search_files uses, and got "requires
+        # 'glob'" -- three of findfile-1's twelve runs burned steps on it,
+        # one to the step limit. The value is what the model meant to look
+        # for either way; a bare name is a valid glob for that exact name.
+        glob_pat = str(args.get("glob") or args.get("pattern") or "").strip()
         path = str(args.get("path") or ".").strip() or "."
         if not glob_pat:
             raise RuntimeError("find_files requires 'glob'.")

{hexcli-2.14.0 → hexcli-2.16.0}/hexcli/tools.py

@@ -423,6 +423,17 @@ def edit_file_tool(path_text: str, old_string: str, new_string: str) -> str:
         raise RuntimeError("edit_file requires a non-empty 'old_string'. Use write_file to overwrite the whole file.")
     if not path.exists():
         raise RuntimeError(f"File not found: {path}.{missing_path_hint(path)}")
+    if old_string == new_string:
+        # 37 of the 840 edit_file calls on record (2026-09-17) sent the same
+        # text as old and new and were told "Edited"; the model then ran or
+        # read the file believing it had changed it (tests-claim-1: "The
+        # median function was correctly fixed", after an edit of mean to
+        # itself). A no-op is not an edit, and saying so is the only way the
+        # next step can be the change that was meant.
+        raise RuntimeError(
+            f"old_string and new_string are identical, so nothing changed in {path}. "
+            "Put the changed text in new_string, or read_file to see what is there now."
+        )
     content = path.read_text(encoding="utf-8")
     tier = "exact"
     if content.count(old_string) == 1: