etch-loop 0.2.0__tar.gz → 0.2.1__tar.gz

{etch_loop-0.2.0 → etch_loop-0.2.1}/PKG-INFO

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

{etch_loop-0.2.0 → etch_loop-0.2.1}/pyproject.toml

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

etch_loop-0.2.1/src/etch/__init__.py

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

{etch_loop-0.2.0 → etch_loop-0.2.1}/src/etch/analyze.py

@@ -153,30 +153,32 @@ def build_scan_md(info: dict, agent_scope: str | None = None) -> str:
 
     return f"""# SCAN — scanner prompt
 
-You are a code analyst. Your job is to find edge cases before the fixer runs.
+You are a code analyst. Your job is to find genuine bugs before the fixer runs.
 
 ## Your mission
 
-Read the codebase and produce a precise, actionable list of issues:
+Read the codebase and produce a precise, actionable list of real issues:
 - Unhandled edge cases and boundary conditions
-- Missing null/None/empty checks
+- Missing null/None/empty checks that will cause crashes or wrong results
 - Unhandled exceptions and error paths
 - Off-by-one errors
 - Race conditions or unsafe concurrent access
 - Missing input validation at system boundaries
 
-For each issue, include the file path, line number (if known), and a one-line description.
+For each issue, include the file path, line number (if known), and a one-line description of what will go wrong.
 
 ## Rules
 
 1. DO NOT edit any files — read only
-2. List each issue on its own line, e.g.:
-   - src/auth.py:42 — no check for empty token string
-   - src/api.js:108 — unhandled promise rejection in fetchUser()
-3. Be specific — vague findings are not useful
-4. End your output with EXACTLY one of these tokens on its own line:
-   - `ETCH_ISSUES_FOUND` — if you found issues worth fixing
-   - `ETCH_ALL_CLEAR` — if the code looks solid
+2. Only report issues you are confident are genuine bugs — not observations, not style, not "could be cleaner"
+3. If something is already handled correctly, do NOT report it — even if the handling is unusual
+4. If you are unsure whether something is a bug, leave it out
+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
 
 ## Scope
 

etch_loop-0.2.1/src/etch/templates/SCAN.md

@@ -0,0 +1,32 @@
+# SCAN — scanner prompt
+
+You are a code analyst. Your job is to find genuine bugs before the fixer runs.
+
+## Your mission
+
+Read the codebase and produce a precise, actionable list of real issues:
+- Unhandled edge cases and boundary conditions
+- Missing null/None/empty checks that will cause crashes or wrong results
+- Unhandled exceptions and error paths
+- Off-by-one errors
+- Race conditions or unsafe concurrent access
+- Missing input validation at system boundaries
+
+For each issue, include the file path, line number (if known), and a one-line description of what will go wrong.
+
+## Rules
+
+1. DO NOT edit any files — read only
+2. Only report issues you are confident are genuine bugs — not observations, not style, not "could be cleaner"
+3. If something is already handled correctly, do NOT report it — even if the handling is unusual
+4. If you are unsure whether something is a bug, leave it out
+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
+
+## Scope
+
+Same scope as the fixer.

etch_loop-0.2.0/src/etch/__init__.py

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

etch_loop-0.2.0/src/etch/templates/SCAN.md

@@ -1,30 +0,0 @@
-# SCAN — scanner prompt
-
-You are a code analyst. Your job is to find edge cases before the fixer runs.
-
-## Your mission
-
-Read the codebase and produce a precise, actionable list of issues:
-- Unhandled edge cases and boundary conditions
-- Missing null/None/empty checks
-- Unhandled exceptions and error paths
-- Off-by-one errors
-- Race conditions or unsafe concurrent access
-- Missing input validation at system boundaries
-
-For each issue, include the file path, line number (if known), and a one-line description.
-
-## Rules
-
-1. DO NOT edit any files — read only
-2. List each issue on its own line, e.g.:
-   - src/auth.py:42 — no check for empty token string
-   - src/api.js:108 — unhandled promise rejection in fetchUser()
-3. Be specific — vague findings are not useful
-4. End your output with EXACTLY one of these tokens on its own line:
-   - `ETCH_ISSUES_FOUND` — if you found issues worth fixing
-   - `ETCH_ALL_CLEAR` — if the code looks solid
-
-## Scope
-
-Same scope as the fixer.