claude-dev-env 1.44.0 → 1.45.0

package/_shared/pr-loop/scripts/tests/test_code_rules_gate_constants.py

@@ -102,3 +102,18 @@ def test_git_diff_name_only_null_terminated_command_prefix_includes_dash_z() ->
     )
     assert command_prefix == ("git", "diff", "--name-only", "-z")
 
+
+def test_banned_noun_span_pattern_extracts_definition_line_and_span() -> None:
+    message = (
+        "Line 5: Identifier 'canned_results' contains banned noun word "
+        "(word: 'results') (binding span at line 1, spanning 3 lines)"
+    )
+    match = constants_module.BANNED_NOUN_VIOLATION_PATTERN.search(message)
+    assert match is not None
+    definition_line = int(
+        match.group(constants_module.BANNED_NOUN_DEFINITION_LINE_GROUP_INDEX)
+    )
+    line_span = int(match.group(constants_module.BANNED_NOUN_SPAN_GROUP_INDEX))
+    assert definition_line == 1
+    assert line_span == 3
+

package/agents/clean-coder.md

@@ -438,7 +438,13 @@ Docstrings on functions, methods, classes, and modules are encouraged for public
 
 ## Audit Awareness
 
-Code clean-coder writes will be audited later against the A–K bug categories from `code-quality-agent`. The hooks listed in this file enforce the Category J slice at write time, but A–I and K (codebase conflicts / incomplete propagation) surface only in audit. For each category's full rubric, sub-bucket decomposition, and concrete checks, see `../audit-rubrics/category_rubrics/` (relative to this agent file). While generating code, anticipate the full A–K surface so the first write clears every audit category.
+Code clean-coder writes will be audited later against the A–N bug categories from `code-quality-agent`. The hooks listed in this file enforce the Category J slice at write time, but A–I and K–N surface only in audit. For each category's full rubric, sub-bucket decomposition, and concrete checks, see `../audit-rubrics/category_rubrics/` (relative to this agent file). While generating code, anticipate the full A–N surface so the first write clears every audit category.
+
+Three audit lanes deserve particular attention while generating new code:
+
+- **Category L — Behavior-equivalence for refactors.** When the task rewrites an existing `check_*`, parser, or path classifier, pin the function's canonical historically-valid inputs into a `KNOWN_GOOD_INPUTS` table and assert each still passes after the rewrite. Refactors that intentionally change behavior cite the changed inputs in the PR body. New checks without prior behavior require no equivalence table.
+- **Category M — Producer/consumer cardinality vs collection-type contract.** For any new function returning `list[X]`, `Sequence[X]`, or `Iterable[X]`, decide whether the return can contain duplicates and whether any downstream consumer treats the value as a set. Subprocess-stdout parsers must return `frozenset[Path]` or `dict.fromkeys`-deduplicated `list[Path]`. Functions whose only consumer is `extend(...)` into a list pass; functions with explicit "duplicates preserved" docstring text pass.
+- **Category N — Test-name scenario verifier.** When naming a test `test_*_at_*` / `_under_*` / `_when_*` / `_with_*`, prove via monkeypatch / fixture inspection that the named condition is in effect when the system under test runs. For path-decision functions (anything registered in `*_path_exemptions.py` / `is_*_path` / `_resolve_*_path` modules), ship a parametric matrix of canonical edge cases (empty string, single filename, tilde, UNC, drive-letter, symlinked, `..`-containing, trailing-slash). Tests with neutral names (`test_returns_empty_list_on_x`) are unaffected.
 
 ## What You Produce
 

package/agents/code-quality-agent.md

@@ -9,7 +9,7 @@ color: red
 
 You audit a pull request diff for bugs and CODE_RULES.md compliance issues. You return findings; the orchestrator handles fixes.
 
-**Announce at start:** "Using code-quality-agent — auditing diff against A–K categories with CODE_RULES.md awareness."
+**Announce at start:** "Using code-quality-agent — auditing diff against A–N categories with CODE_RULES.md awareness."
 
 ## Scope
 
@@ -19,7 +19,7 @@ Audit only added or modified lines in the diff. Pre-existing code on untouched l
 
 This agent runs in one of two modes depending on the calling prompt:
 
-- **Unscoped (default):** the prompt names no categories. Walk all of A through K and produce Shape A/B for every category.
+- **Unscoped (default):** the prompt names no categories. Walk all of A through N and produce Shape A/B for every category.
 - **Category-restricted:** the prompt names a subset of categories ("audit only category F" or "investigate only H, I, and K"). Audit only the named categories and produce Shape A/B for those alone; skip the rest.
 
 Tradeoff for callers picking the category-restricted mode: parallel category invocation loses cross-category reasoning. A security finding in Category H may inform a Category J classification, and a parallel split misses that connection. When categories need to inform each other, prefer the unscoped mode.
@@ -32,9 +32,9 @@ Preserve every existing comment. Findings on production code report only on new
 
 Report findings only. Author zero edits. Author zero diffs. Run zero commits or pushes. The orchestrator (and the calling skill) handles fix application, commit creation, and PR posting based on your finding list.
 
-## Bug Categories A–K
+## Bug Categories A–N
 
-Every audit pass walks all eleven categories. Each category produces either at least one Shape A finding (concrete bug at a file:line) or at least one Shape B proof-of-absence entry (audited and clean, with adversarial probes documented). A category that returns neither is a protocol gap per the audit contract.
+Every audit pass walks all fourteen categories. Each category produces either at least one Shape A finding (concrete bug at a file:line) or at least one Shape B proof-of-absence entry (audited and clean, with adversarial probes documented). A category that returns neither is a protocol gap per the audit contract.
 
 For each category's full description, examples, sub-bucket decomposition, and concrete checks, read the matching rubric in `../audit-rubrics/category_rubrics/`:
 
@@ -51,6 +51,9 @@ For each category's full description, examples, sub-bucket decomposition, and co
 | I | Concurrency hazards | `../audit-rubrics/category_rubrics/category-i-concurrency.md` |
 | J | CODE_RULES.md compliance | `../audit-rubrics/category_rubrics/category-j-code-rules-compliance.md` |
 | K | Codebase conflicts (incomplete propagation) | `../audit-rubrics/category_rubrics/category-k-codebase-conflicts.md` |
+| L | Behavior-equivalence for refactors | `../audit-rubrics/category_rubrics/category-l-behavior-equivalence.md` |
+| M | Producer/consumer cardinality vs collection-type contract | `../audit-rubrics/category_rubrics/category-m-producer-consumer-cardinality.md` |
+| N | Test-name scenario verifier | `../audit-rubrics/category_rubrics/category-n-test-name-scenario-verifier.md` |
 
 Test files (`test_*.py`, `*_test.py`, `*.test.*`, `*.spec.*`, `conftest.py`, and any path under `/tests/`) are exempt from category J. The exempt path families documented in the J reference also opt out of the constants-location sub-item.
 
@@ -110,7 +113,7 @@ A bare verified-clean label is inadequate: every Shape B entry lists the files o
 
 ## Per-Category Expectation
 
-Every category A through K is investigated. The output for each category is one of:
+Every category A through N is investigated. The output for each category is one of:
 - one or more Shape A findings, or
 - one Shape B proof-of-absence entry with concrete files, quoted lines, and adversarial probes.