rule-hunter: an absence claim with no budget for its listing is unverified

core/agents/rule-hunter.md

@@ -110,7 +110,9 @@ verdicts without evidence. If evidence is absent, there is no finding. A finding
 something is missing — a test file, a doc, a case, a cleanup — carries the listing
 that looked for it: the `ls`, `find` or `grep` command, run over the repository and
 never only the bundle, since a file outside the scope still exists, and its output,
-empty or not. A claim of absence without that listing is not a finding. Never justify
+empty or not. A claim of absence without that listing is not a finding. When the
+budget leaves no call for that listing, name the claim in the `not reached:` line as
+`unverified: <claim>`, never drop it. Never justify
 a finding by a design maxim or general principle ("tell don't ask", "law of
 Demeter") — maxims propose, evidence disposes; only your rule's detection commands
 convict.

go-linter-driven-development/CHANGELOG.md

@@ -12,6 +12,8 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versio
   command that looked for it, run over the repository and not only the review's
   bundle, and that command's output. Without the listing there is no finding. A
   hunter once reported a test file as missing when it existed outside the scope.
+  When the hunter's budget leaves no call for the listing, the claim appears in the
+  hunter's `not reached:` line as `unverified`; the report never drops it.
 
 ## [2.15.1] - 2026-10-15
 

go-linter-driven-development/agents/rule-hunter.md

@@ -110,7 +110,9 @@ verdicts without evidence. If evidence is absent, there is no finding. A finding
 something is missing — a test file, a doc, a case, a cleanup — carries the listing
 that looked for it: the `ls`, `find` or `grep` command, run over the repository and
 never only the bundle, since a file outside the scope still exists, and its output,
-empty or not. A claim of absence without that listing is not a finding. Never justify
+empty or not. A claim of absence without that listing is not a finding. When the
+budget leaves no call for that listing, name the claim in the `not reached:` line as
+`unverified: <claim>`, never drop it. Never justify
 a finding by a design maxim or general principle ("tell don't ask", "law of
 Demeter") — maxims propose, evidence disposes; only your rule's detection commands
 convict.

lang/generic/passthrough/CHANGELOG.md

@@ -12,6 +12,8 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versio
   command that looked for it, run over the repository and not only the review's
   bundle, and that command's output. Without the listing there is no finding. A
   hunter once reported a test file as missing when it existed outside the scope.
+  When the hunter's budget leaves no call for the listing, the claim appears in the
+  hunter's `not reached:` line as `unverified`; the report never drops it.
 
 ## [0.5.0] - 2026-10-15
 

lang/go/passthrough/CHANGELOG.md

@@ -12,6 +12,8 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versio
   command that looked for it, run over the repository and not only the review's
   bundle, and that command's output. Without the listing there is no finding. A
   hunter once reported a test file as missing when it existed outside the scope.
+  When the hunter's budget leaves no call for the listing, the claim appears in the
+  hunter's `not reached:` line as `unverified`; the report never drops it.
 
 ## [2.15.1] - 2026-10-15
 

lang/python/passthrough/CHANGELOG.md

@@ -12,6 +12,8 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versio
   command that looked for it, run over the repository and not only the review's
   bundle, and that command's output. Without the listing there is no finding. A
   hunter once reported a test file as missing when it existed outside the scope.
+  When the hunter's budget leaves no call for the listing, the claim appears in the
+  hunter's `not reached:` line as `unverified`; the report never drops it.
 
 ## [0.4.1] - 2026-10-15
 

lang/ts-react/passthrough/CHANGELOG.md

@@ -12,6 +12,8 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versio
   command that looked for it, run over the repository and not only the review's
   bundle, and that command's output. Without the listing there is no finding. A
   hunter once reported a test file as missing when it existed outside the scope.
+  When the hunter's budget leaves no call for the listing, the claim appears in the
+  hunter's `not reached:` line as `unverified`; the report never drops it.
 
 ## [2.0.1] - 2026-10-15
 

linter-driven-development/CHANGELOG.md

@@ -12,6 +12,8 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versio
   command that looked for it, run over the repository and not only the review's
   bundle, and that command's output. Without the listing there is no finding. A
   hunter once reported a test file as missing when it existed outside the scope.
+  When the hunter's budget leaves no call for the listing, the claim appears in the
+  hunter's `not reached:` line as `unverified`; the report never drops it.
 
 ## [0.5.0] - 2026-10-15
 

linter-driven-development/agents/rule-hunter.md

@@ -110,7 +110,9 @@ verdicts without evidence. If evidence is absent, there is no finding. A finding
 something is missing — a test file, a doc, a case, a cleanup — carries the listing
 that looked for it: the `ls`, `find` or `grep` command, run over the repository and
 never only the bundle, since a file outside the scope still exists, and its output,
-empty or not. A claim of absence without that listing is not a finding. Never justify
+empty or not. A claim of absence without that listing is not a finding. When the
+budget leaves no call for that listing, name the claim in the `not reached:` line as
+`unverified: <claim>`, never drop it. Never justify
 a finding by a design maxim or general principle ("tell don't ask", "law of
 Demeter") — maxims propose, evidence disposes; only your rule's detection commands
 convict.

python-linter-driven-development/CHANGELOG.md

@@ -12,6 +12,8 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versio
   command that looked for it, run over the repository and not only the review's
   bundle, and that command's output. Without the listing there is no finding. A
   hunter once reported a test file as missing when it existed outside the scope.
+  When the hunter's budget leaves no call for the listing, the claim appears in the
+  hunter's `not reached:` line as `unverified`; the report never drops it.
 
 ## [0.4.1] - 2026-10-15
 

python-linter-driven-development/agents/rule-hunter.md

@@ -110,7 +110,9 @@ verdicts without evidence. If evidence is absent, there is no finding. A finding
 something is missing — a test file, a doc, a case, a cleanup — carries the listing
 that looked for it: the `ls`, `find` or `grep` command, run over the repository and
 never only the bundle, since a file outside the scope still exists, and its output,
-empty or not. A claim of absence without that listing is not a finding. Never justify
+empty or not. A claim of absence without that listing is not a finding. When the
+budget leaves no call for that listing, name the claim in the `not reached:` line as
+`unverified: <claim>`, never drop it. Never justify
 a finding by a design maxim or general principle ("tell don't ask", "law of
 Demeter") — maxims propose, evidence disposes; only your rule's detection commands
 convict.

ts-react-linter-driven-development/CHANGELOG.md

@@ -12,6 +12,8 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versio
   command that looked for it, run over the repository and not only the review's
   bundle, and that command's output. Without the listing there is no finding. A
   hunter once reported a test file as missing when it existed outside the scope.
+  When the hunter's budget leaves no call for the listing, the claim appears in the
+  hunter's `not reached:` line as `unverified`; the report never drops it.
 
 ## [2.0.1] - 2026-10-15
 

ts-react-linter-driven-development/agents/rule-hunter.md

@@ -110,7 +110,9 @@ verdicts without evidence. If evidence is absent, there is no finding. A finding
 something is missing — a test file, a doc, a case, a cleanup — carries the listing
 that looked for it: the `ls`, `find` or `grep` command, run over the repository and
 never only the bundle, since a file outside the scope still exists, and its output,
-empty or not. A claim of absence without that listing is not a finding. Never justify
+empty or not. A claim of absence without that listing is not a finding. When the
+budget leaves no call for that listing, name the claim in the `not reached:` line as
+`unverified: <claim>`, never drop it. Never justify
 a finding by a design maxim or general principle ("tell don't ask", "law of
 Demeter") — maxims propose, evidence disposes; only your rule's detection commands
 convict.