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

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

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

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

@@ -1,6 +1,6 @@
 [project]
 name = "etch-loop"
-version = "0.4.3"
+version = "0.4.5"
 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.5/src/etch/__init__.py

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

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

@@ -270,26 +270,38 @@ def build_run_md(info: dict) -> str:
     else:
         cmd_list = "- (detect and run the appropriate build/test command for this project)"
 
-    return f"""# RUN — build and test validation
+    return f"""# RUN — test writer and build validator
 
-You are a build validator. The fixer has made changes. Your job is to run the project's build and test suite to confirm everything still works.
+You are a test engineer. The fixer has just made changes. Your job is to write tests for what was changed, then run the full suite to confirm everything works.
 
-## Commands to run
+## Your mission
+
+1. **Write or update tests** — look at what the fixer changed and write targeted tests covering:
+   - The specific edge cases that were fixed
+   - Boundary conditions around the changed code
+   - Any regression paths that could break silently
+   Write tests in the project's existing test style and location.
+
+2. **Run the test suite** — run the full build and test commands to confirm everything passes.
+
+## Build and test commands
 
 {cmd_list}
 
 ## Rules
 
-1. Run each command and observe the output
-2. If ALL commands pass:
-   - Write `ETCH_SUMMARY: <e.g. "all 47 tests passed">`
-   - Write `ETCH_ALL_CLEAR`
-3. If ANY command fails:
-   - Write `ETCH_SUMMARY: <what failed, e.g. "3 tests failed in test_auth.py — TypeError on line 42">`
-   - Include the relevant error output so the fixer can diagnose it
-   - Write `ETCH_ISSUES_FOUND`
-
-Do not fix anything — only run and report.
+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
 """
 
 

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

@@ -6,36 +6,30 @@ _PUNCTUATION_ONLY = set("-=*_`~><|")
 
 
 def parse(output: str) -> str:
-    """Parse breaker agent output for control tokens.
+    """Parse agent output for control tokens.
 
-    Returns the signal corresponding to whichever token appears first.
-    If both appear, the earlier one wins. If neither appears, returns
-    "issues" as a fail-safe.
+    Tokens must appear alone on their own line (after stripping whitespace
+    and backtick wrappers). This prevents false matches when agents quote the
+    token strings in explanations like `ETCH_ALL_CLEAR`.
+
+    The first matching line wins. If neither token is found, returns "issues"
+    as a fail-safe.
 
     Returns:
-        "clear"  — ETCH_ALL_CLEAR found (and appears before ETCH_ISSUES_FOUND)
-        "issues" — ETCH_ISSUES_FOUND found, appears first, or neither found
+        "clear"  — ETCH_ALL_CLEAR found on its own line first
+        "issues" — ETCH_ISSUES_FOUND found on its own line first, or no token found
     """
     if not isinstance(output, str):
         return "issues"
 
-    clear_pos = output.find(_TOKEN_CLEAR)
-    issues_pos = output.find(_TOKEN_ISSUES)
-
-    if clear_pos == -1 and issues_pos == -1:
-        # Fail-safe: no token found → assume issues
-        return "issues"
-
-    if clear_pos == -1:
-        return "issues"
-
-    if issues_pos == -1:
-        return "clear"
+    for line in output.splitlines():
+        stripped = line.strip().strip("`").strip()
+        if stripped == _TOKEN_CLEAR:
+            return "clear"
+        if stripped == _TOKEN_ISSUES:
+            return "issues"
 
-    # Both found — whichever appears first wins
-    if clear_pos < issues_pos:
-        return "clear"
-    return "issues"
+    return "issues"  # fail-safe: no token found
 
 
 def extract_commit_message(output: str, fallback: str) -> str:
@@ -93,35 +87,23 @@ def extract_summary(output: str) -> str:
 
 
 def extract_finding(output: str) -> str:
-    """Extract first meaningful line before the signal token.
+    """Extract the last meaningful line before the signal token line.
 
-    Returns the first non-empty, non-header line that appears before
-    the signal token, or an empty string if nothing useful is found.
+    Scans line by line, stops at the first line that IS a token (exact match).
+    Returns the last non-empty, non-header line before that point.
     """
     if not isinstance(output, str) or not output.strip():
         return ""
 
-    # Find the position of either token
-    clear_pos = output.find(_TOKEN_CLEAR)
-    issues_pos = output.find(_TOKEN_ISSUES)
-
-    # Determine the cutoff point (use whichever token appears first)
-    cutoff = len(output)
-    if clear_pos >= 0 and issues_pos >= 0:
-        cutoff = min(clear_pos, issues_pos)
-    elif clear_pos >= 0:
-        cutoff = clear_pos
-    elif issues_pos >= 0:
-        cutoff = issues_pos
-
-    text_before = output[:cutoff].strip()
-    if not text_before:
-        return ""
+    lines_before: list[str] = []
+    for line in output.splitlines():
+        stripped = line.strip().strip("`").strip()
+        if stripped in (_TOKEN_CLEAR, _TOKEN_ISSUES):
+            break
+        lines_before.append(line)
 
-    lines = text_before.splitlines()
-    for line in reversed(lines):
+    for line in reversed(lines_before):
         stripped = line.strip().strip("`").strip()
-        # Skip empty lines, markdown headers, separator lines, and bare punctuation
         if not stripped:
             continue
         if stripped.startswith("#"):

etch_loop-0.4.5/src/etch/templates/RUN.md

@@ -0,0 +1,32 @@
+# RUN — test writer and build validator
+
+You are a test engineer. The fixer has just made changes. Your job is to write tests for what was changed, then run the full suite to confirm everything works.
+
+## Your mission
+
+1. **Write or update tests** — look at what the fixer changed and write targeted tests covering:
+   - The specific edge cases that were fixed
+   - Boundary conditions around the changed code
+   - Any regression paths that could break silently
+   Write tests in the project's existing test style and location.
+
+2. **Run the test suite** — run the full build and test commands to confirm everything passes.
+
+## Build and test commands
+
+[configured by etch init]
+
+## Rules
+
+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

etch_loop-0.4.3/src/etch/__init__.py

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

etch_loop-0.4.3/src/etch/templates/RUN.md

@@ -1,20 +0,0 @@
-# RUN — build and test validation
-
-You are a build validator. The fixer has made changes. Your job is to run the project's build and test suite to confirm everything still works.
-
-## Commands to run
-
-[configured by etch init]
-
-## Rules
-
-1. Run each command and observe the output
-2. If ALL commands pass:
-   - Write `ETCH_SUMMARY: <e.g. "all 47 tests passed">`
-   - Write `ETCH_ALL_CLEAR`
-3. If ANY command fails:
-   - Write `ETCH_SUMMARY: <what failed, e.g. "3 tests failed in test_auth.py — TypeError on line 42">`
-   - Include the relevant error output so the fixer can diagnose it
-   - Write `ETCH_ISSUES_FOUND`
-
-Do not fix anything — only run and report.