etch-loop 0.4.5__tar.gz → 0.4.7__tar.gz

{etch_loop-0.4.5 → etch_loop-0.4.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: etch-loop
-Version: 0.4.5
+Version: 0.4.7
 Summary: Run Claude Code in a fix-break loop until your codebase is clean
 License: MIT
 Requires-Python: >=3.11

{etch_loop-0.4.5 → etch_loop-0.4.7}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "etch-loop"
-version = "0.4.5"
+version = "0.4.7"
 requires-python = ">=3.11"
 description = "Run Claude Code in a fix-break loop until your codebase is clean"
 readme = "README.md"

etch_loop-0.4.7/src/etch/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.4.7"

{etch_loop-0.4.5 → etch_loop-0.4.7}/src/etch/analyze.py

@@ -179,9 +179,12 @@ For each issue, include the file path, line number (if known), and a one-line de
 5. List each confirmed issue on its own line, e.g.:
    - src/auth.py:42 — crashes with empty token string (no guard)
    - src/api.js:108 — unhandled promise rejection will silently fail
-6. End your output with EXACTLY one of these tokens on its own line:
-   - `ETCH_ISSUES_FOUND` — if you found confirmed bugs worth fixing
-   - `ETCH_ALL_CLEAR` — if the code looks solid or you found nothing certain
+6. Before the signal token, write your summary in this exact format — it appears directly in the terminal:
+   `<etch_summary>3 bugs found — null deref in auth.py:42, off-by-one in parser.py:88</etch_summary>`
+   `<etch_summary>no confirmed bugs found</etch_summary>`
+7. End with EXACTLY one of these on its own line:
+   `ETCH_ISSUES_FOUND`
+   `ETCH_ALL_CLEAR`
 
 ## Scope
 
@@ -210,18 +213,18 @@ Scan the codebase for:
 ## Rules
 
 1. Fix only what you find — do not refactor, rename, or reorganize
-2. One logical fix per commit (the harness will commit for you)
-3. Do not add comments explaining what you fixed
-4. If you find nothing, make no changes
+2. Do not add comments explaining what you fixed
+3. If you find nothing, make no changes
 
 ## Scope
 
 {scope}
 
-## Commit format
+## Terminal output (required)
 
-The harness commits automatically. Each commit will be:
-  fix(edge): <short description of what was fixed>
+After making changes (or deciding there is nothing to fix), write your summary in this exact format — it appears in the terminal and is used as the commit message:
+  `<etch_summary>fixed 3 issues — null guard in auth.py, bounds check in parser.py, timeout in agent.py</etch_summary>`
+  `<etch_summary>nothing to fix — all reported issues were already handled</etch_summary>`
 """
 
 
@@ -250,9 +253,12 @@ Be adversarial — think like someone actively trying to make this code fail.
 
 1. DO NOT edit any files — read only
 2. Report your findings clearly, one per line
-3. End your output with EXACTLY one of these tokens on its own line:
-   - `ETCH_ISSUES_FOUND` — if you found anything worth fixing
-   - `ETCH_ALL_CLEAR` — if the code looks solid
+3. Before the signal token, write your summary in this exact format — it appears directly in the terminal:
+   `<etch_summary>2 issues — unguarded empty list in sorter.py:14, exception swallowed in loader.py:67</etch_summary>`
+   `<etch_summary>no issues found — code looks solid</etch_summary>`
+4. End with EXACTLY one of these on its own line:
+   `ETCH_ISSUES_FOUND`
+   `ETCH_ALL_CLEAR`
 
 ## Scope
 
@@ -292,16 +298,13 @@ You are a test engineer. The fixer has just made changes. Your job is to write t
 
 1. You MAY edit test files — that is your job
 2. Do NOT touch production code — only tests
-3. After running, report clearly:
-   - If ALL tests pass:
-     - `ETCH_SUMMARY: <e.g. "wrote 4 tests, all 51 passed">`
-     - `ETCH_ALL_CLEAR`
-   - If ANY test fails due to a bug in the production code:
-     - `ETCH_SUMMARY: <what failed and why>`
-     - Include the relevant error output
-     - `ETCH_ISSUES_FOUND`
-   - If tests fail because the tests themselves are wrong (flawed test logic):
-     - Fix the test and re-run before reporting
+3. If tests fail because of flawed test logic, fix the test and re-run before reporting
+4. When done, write your summary in this exact format — it appears directly in the terminal:
+   `<etch_summary>wrote 4 tests, all 51 passed</etch_summary>`
+   `<etch_summary>2 tests failed — TypeError in test_auth.py:38, production bug in token.py:12</etch_summary>`
+5. End with EXACTLY one of these on its own line:
+   `ETCH_ALL_CLEAR` — if all tests pass
+   `ETCH_ISSUES_FOUND` — if tests reveal a bug in production code
 """
 
 

{etch_loop-0.4.5 → etch_loop-0.4.7}/src/etch/signals.py

@@ -1,5 +1,7 @@
 """Signal parsing for breaker agent output."""
 
+import re
+
 _TOKEN_CLEAR = "ETCH_ALL_CLEAR"
 _TOKEN_ISSUES = "ETCH_ISSUES_FOUND"
 _PUNCTUATION_ONLY = set("-=*_`~><|")
@@ -35,14 +37,22 @@ def parse(output: str) -> str:
 def extract_commit_message(output: str, fallback: str) -> str:
     """Extract a short commit message from fixer output.
 
-    Looks for the first substantive line that describes what was changed.
-    Falls back to `fallback` if nothing useful is found.
+    Tries ETCH_SUMMARY first (the explicit summary line), then falls back to
+    scanning for the first substantive line that describes what was changed.
     Returns a string starting with 'fix(edge): '.
     """
     if not isinstance(output, str) or not output.strip():
         return fallback
 
-    _SKIP_STARTS = ("i ", "i've ", "i have ", "here ", "the following", "done", "no ")
+    # Prefer the explicit ETCH_SUMMARY line
+    summary = extract_summary(output)
+    if summary:
+        msg = summary[:72].rstrip(".,;:")
+        if not msg.lower().startswith("fix"):
+            msg = f"fix(edge): {msg[0].lower()}{msg[1:]}"
+        return msg
+
+    _SKIP_STARTS = ("i ", "i've ", "i have ", "here ", "here's", "the following", "done", "no ", "summary", "below")
     _SKIP_WORDS = {"ok", "done", "nothing", "complete", "finished"}
 
     for line in output.splitlines():
@@ -70,19 +80,18 @@ def extract_commit_message(output: str, fallback: str) -> str:
 
 
 def extract_summary(output: str) -> str:
-    """Extract the ETCH_SUMMARY line written by an agent.
+    """Extract the summary from an <etch_summary> tag in agent output.
 
-    Agents are prompted to write a line like:
-        ETCH_SUMMARY: fixed 3 null-guard issues in auth.py
+    Agents are prompted to write:
+        <etch_summary>fixed 3 null-guard issues in auth.py</etch_summary>
 
     Returns the summary text, or empty string if not found.
     """
     if not isinstance(output, str):
         return ""
-    for line in output.splitlines():
-        stripped = line.strip()
-        if stripped.startswith("ETCH_SUMMARY:"):
-            return stripped[len("ETCH_SUMMARY:"):].strip()
+    m = re.search(r"<etch_summary>(.*?)</etch_summary>", output, re.DOTALL)
+    if m:
+        return m.group(1).strip()
     return ""
 
 

{etch_loop-0.4.5 → etch_loop-0.4.7}/src/etch/templates/BREAK.md

@@ -19,12 +19,12 @@ Be adversarial — think like someone actively trying to make this code fail.
 
 1. DO NOT edit any files — read only
 2. Report your findings clearly, one per line
-3. Before the signal token, write one line starting with `ETCH_SUMMARY:` summarising what you found:
-   - `ETCH_SUMMARY: 2 issues — unguarded empty list in sorter.py:14, exception swallowed in loader.py:67`
-   - `ETCH_SUMMARY: no issues found — code looks solid`
-4. End your output with EXACTLY one of these tokens on its own line:
-   - `ETCH_ISSUES_FOUND` — if you found anything worth fixing
-   - `ETCH_ALL_CLEAR` — if the code looks solid
+3. Before the signal token, write your summary in this exact format — it appears directly in the terminal:
+   `<etch_summary>2 issues — unguarded empty list in sorter.py:14, exception swallowed in loader.py:67</etch_summary>`
+   `<etch_summary>no issues found — code looks solid</etch_summary>`
+4. End with EXACTLY one of these on its own line:
+   `ETCH_ISSUES_FOUND`
+   `ETCH_ALL_CLEAR`
 
 ## Scope
 

{etch_loop-0.4.5 → etch_loop-0.4.7}/src/etch/templates/ETCH.md

@@ -15,19 +15,15 @@ Scan the codebase for:
 ## Rules
 
 1. Fix only what you find — do not refactor, rename, or reorganize
-2. One logical fix per commit (the harness will commit for you)
-3. Do not add comments explaining what you fixed
-4. If you find nothing, make no changes
+2. Do not add comments explaining what you fixed
+3. If you find nothing, make no changes
 
 ## Scope
 
 Focus on: [edit this to narrow your scope, e.g. "src/auth/", "the payment module"]
 
-## Output format
+## Terminal output (required)
 
-After making your changes, write one line at the end of your output:
-  ETCH_SUMMARY: <concise summary, e.g. "fixed 3 issues — added null guards in auth.py, guarded empty input in parser.py">
-  ETCH_SUMMARY: no changes — nothing to fix
-
-The harness commits automatically. Each commit will be:
-  fix(edge): <short description of what was fixed>
+After making changes (or deciding there is nothing to fix), write your summary in this exact format — it appears in the terminal and is used as the commit message:
+  `<etch_summary>fixed 3 issues — null guard in auth.py, bounds check in parser.py, timeout in agent.py</etch_summary>`
+  `<etch_summary>nothing to fix — all reported issues were already handled</etch_summary>`

{etch_loop-0.4.5 → etch_loop-0.4.7}/src/etch/templates/RUN.md

@@ -20,13 +20,10 @@ You are a test engineer. The fixer has just made changes. Your job is to write t
 
 1. You MAY edit test files — that is your job
 2. Do NOT touch production code — only tests
-3. After running, report clearly:
-   - If ALL tests pass:
-     - `ETCH_SUMMARY: <e.g. "wrote 4 tests, all 51 passed">`
-     - `ETCH_ALL_CLEAR`
-   - If ANY test fails due to a bug in the production code:
-     - `ETCH_SUMMARY: <what failed and why>`
-     - Include the relevant error output
-     - `ETCH_ISSUES_FOUND`
-   - If tests fail because the tests themselves are wrong (flawed test logic):
-     - Fix the test and re-run before reporting
+3. If tests fail because of flawed test logic, fix the test and re-run before reporting
+4. When done, write your summary in this exact format — it appears directly in the terminal:
+   `<etch_summary>wrote 4 tests, all 51 passed</etch_summary>`
+   `<etch_summary>2 tests failed — TypeError in test_auth.py:38, production bug in token.py:12</etch_summary>`
+5. End with EXACTLY one of these on its own line:
+   `ETCH_ALL_CLEAR` — if all tests pass
+   `ETCH_ISSUES_FOUND` — if tests reveal a bug in production code

{etch_loop-0.4.5 → etch_loop-0.4.7}/src/etch/templates/SCAN.md

@@ -23,12 +23,12 @@ For each issue, include the file path, line number (if known), and a one-line de
 5. List each confirmed issue on its own line, e.g.:
    - src/auth.py:42 — crashes with empty token string (no guard)
    - src/api.js:108 — unhandled promise rejection will silently fail
-6. Before the signal token, write one line starting with `ETCH_SUMMARY:` summarising what you found in plain English:
-   - `ETCH_SUMMARY: found 3 issues — null dereference in auth.py:42, off-by-one in parser.py:88, unhandled OSError in git.py:31`
-   - `ETCH_SUMMARY: no confirmed bugs found`
-7. End your output with EXACTLY one of these tokens on its own line:
-   - `ETCH_ISSUES_FOUND` — if you found confirmed bugs worth fixing
-   - `ETCH_ALL_CLEAR` — if the code looks solid or you found nothing certain
+6. Before the signal token, write your summary in this exact format — it appears directly in the terminal:
+   `<etch_summary>3 bugs found — null deref in auth.py:42, off-by-one in parser.py:88</etch_summary>`
+   `<etch_summary>no confirmed bugs found</etch_summary>`
+7. End with EXACTLY one of these on its own line:
+   `ETCH_ISSUES_FOUND`
+   `ETCH_ALL_CLEAR`
 
 ## Scope
 

etch_loop-0.4.5/src/etch/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.4.5"