hexcli 2.17.0__tar.gz → 2.18.0__tar.gz

{hexcli-2.17.0 → hexcli-2.18.0}/CHANGELOG.md

@@ -4,6 +4,38 @@ 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.18.0 — 2026-09-18
+
+A minor release: what `write_file` writes for one shape of body changes,
+so the run that follows it changes.
+
+> **Gate: PASS** on the pinned 24-case set after rechecks. Own arm, fresh
+> server, seed 20260918, 2 invalid of 245 runs. `agentic-5` and
+> `error-recovery-3` (a counting answer and a denied search, no write in
+> either) missed once at 5 runs; `agentic-5` held 6/6, `error-recovery-3`
+> read 3/4 with two invalid runs on a server 70 minutes into its traffic and
+> 6/6 on a fresh one. Against the v2.11.1 12-run baseline: run-level
+> 402/514 vs 182/228, +1.6 %, Fisher p = 0.70; pass^k 26 → 29 of 46 shared
+> cases, McNemar p = 0.51. The unescape fired on three writes in the arm
+> (a `trap-1` poem and two `runit-1` bodies, all of which decode the same
+> under both rules), so the arm is evidence of no regression and the effect
+> rests on the fixture. Smoke 10/10 on a fresh server.
+
+- A double-escaped Python body is decoded the way that parses. The model
+  writes its line breaks as literal `\n` when it escapes a reply twice, and
+  the `\n` it means as a string escape inside the code looks exactly the
+  same: `print(\"\nWelcome\")` and the line break after it are the same two
+  characters. The 2.9.0 rule decoded all of them, so on 2026-09-18 the owner
+  got a file that read `print("` on one line and `Welcome to the Calculator
+  App!")` on the next, and the model spent the rest of the session not
+  fixing it. For a `.py` path the body is now decoded in full and parsed; if
+  that fails, every `\n` except one sitting right after an opening quote or
+  right before a closing one is decoded and the result parsed again, and
+  whichever parses is written (the full decode when neither does, as
+  before). Other file types are unchanged. Of the 511 `write_file` bodies on
+  record five are double-escaped, two have a quote-adjacent `\n`, and one of
+  those, the session above, parses only this way.
+
 ## 2.17.0 — 2026-09-18
 
 A minor release: the parser accepts a reply it used to send back for a

{hexcli-2.17.0 → hexcli-2.18.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: hexcli
-Version: 2.17.0
+Version: 2.18.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.17.0 → hexcli-2.18.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.17.0"
+__version__ = "2.18.0"

{hexcli-2.17.0 → hexcli-2.18.0}/hexcli/editing.py

@@ -12,6 +12,7 @@ audit (2026-07) through the merge tier (2026-09-13).
 """
 from __future__ import annotations
 
+import ast
 import difflib
 import re
 
@@ -140,6 +141,45 @@ def unescape_json(text: str) -> str:
     return _unescape_json(text)
 
 
+_QUOTE_ADJACENT_NL = re.compile(r'(["\'])\\n|\\n(["\'])')
+
+
+def unescape_body(text: str, path: str) -> str:
+    """Decode a double-escaped file body, keeping a Python source parseable.
+
+    A body the model escaped twice carries its line breaks as literal \\n --
+    and so does every \\n it meant as a string escape inside the code:
+    `print(\\"\\nWelcome\\")` and the line break after it are the same two
+    characters. Decoding all of them (the 2.9.0 rule) turns the escape into a
+    real newline inside the string literal, and the file the owner got on
+    2026-09-18 read `print("` / `Welcome to the Calculator App!")` -- a
+    SyntaxError the model then spent eleven steps not fixing.
+
+    For a .py path, decode everything and parse; if that fails, decode
+    everything EXCEPT a \\n that sits right after an opening quote or right
+    before a closing one, and parse again; keep whichever parses, and the
+    full decode when neither does (the caller's checker will say so). Other
+    file types get the full decode as before. Measured over the 511
+    write_file bodies on record: five are double-escaped, two of those have
+    a quote-adjacent \\n, and one of the two (the session above) parses only
+    this way."""
+    full = _unescape_json(text)
+    if not path.lower().endswith(".py"):
+        return full
+    try:
+        ast.parse(full)
+        return full
+    except SyntaxError:
+        pass
+    kept = _QUOTE_ADJACENT_NL.sub(lambda m: (m.group(1) or "") + "\x00" + (m.group(2) or ""), text)
+    candidate = _unescape_json(kept).replace("\x00", "\\n")
+    try:
+        ast.parse(candidate)
+        return candidate
+    except SyntaxError:
+        return full
+
+
 _DELTA_TOKEN_RE = re.compile(r"\w+|\s+|[^\w\s]")
 _ESCAPED_RE = re.compile(r'\\["nt\\]')
 _BARE_QUOTE_RE = re.compile(r'(?<!\\)"')

{hexcli-2.17.0 → hexcli-2.18.0}/hexcli/tools.py

@@ -461,7 +461,7 @@ def write_file_tool(path_text: str, content: str) -> str:
     path.parent.mkdir(parents=True, exist_ok=True)
     note = ""
     if p2.looks_double_escaped(content):
-        content = p2.unescape_json(content)
+        content = p2.unescape_body(content, str(path))
         note = ", unescaped"
     tmp = path.parent / (path.name + ".tmp")
     tmp.write_text(content, encoding="utf-8")