diff --git a/core/agents/rule-hunter.md b/core/agents/rule-hunter.md index 3db55e1..6182427 100644 --- a/core/agents/rule-hunter.md +++ b/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: `, 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. diff --git a/go-linter-driven-development/CHANGELOG.md b/go-linter-driven-development/CHANGELOG.md index 01649b6..532da3a 100644 --- a/go-linter-driven-development/CHANGELOG.md +++ b/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 diff --git a/go-linter-driven-development/agents/rule-hunter.md b/go-linter-driven-development/agents/rule-hunter.md index 6bf0e57..7b3a66f 100644 --- a/go-linter-driven-development/agents/rule-hunter.md +++ b/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: `, 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. diff --git a/lang/generic/passthrough/CHANGELOG.md b/lang/generic/passthrough/CHANGELOG.md index b63f092..6b238b8 100644 --- a/lang/generic/passthrough/CHANGELOG.md +++ b/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 diff --git a/lang/go/passthrough/CHANGELOG.md b/lang/go/passthrough/CHANGELOG.md index 01649b6..532da3a 100644 --- a/lang/go/passthrough/CHANGELOG.md +++ b/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 diff --git a/lang/python/passthrough/CHANGELOG.md b/lang/python/passthrough/CHANGELOG.md index ad70984..7082a34 100644 --- a/lang/python/passthrough/CHANGELOG.md +++ b/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 diff --git a/lang/ts-react/passthrough/CHANGELOG.md b/lang/ts-react/passthrough/CHANGELOG.md index ddc0c6e..9261f59 100644 --- a/lang/ts-react/passthrough/CHANGELOG.md +++ b/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 diff --git a/linter-driven-development/CHANGELOG.md b/linter-driven-development/CHANGELOG.md index b63f092..6b238b8 100644 --- a/linter-driven-development/CHANGELOG.md +++ b/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 diff --git a/linter-driven-development/agents/rule-hunter.md b/linter-driven-development/agents/rule-hunter.md index 44448a5..f9b34a9 100644 --- a/linter-driven-development/agents/rule-hunter.md +++ b/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: `, 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. diff --git a/python-linter-driven-development/CHANGELOG.md b/python-linter-driven-development/CHANGELOG.md index ad70984..7082a34 100644 --- a/python-linter-driven-development/CHANGELOG.md +++ b/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 diff --git a/python-linter-driven-development/agents/rule-hunter.md b/python-linter-driven-development/agents/rule-hunter.md index 32b494e..5c7704c 100644 --- a/python-linter-driven-development/agents/rule-hunter.md +++ b/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: `, 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. diff --git a/ts-react-linter-driven-development/CHANGELOG.md b/ts-react-linter-driven-development/CHANGELOG.md index ddc0c6e..9261f59 100644 --- a/ts-react-linter-driven-development/CHANGELOG.md +++ b/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 diff --git a/ts-react-linter-driven-development/agents/rule-hunter.md b/ts-react-linter-driven-development/agents/rule-hunter.md index a644e78..186ef51 100644 --- a/ts-react-linter-driven-development/agents/rule-hunter.md +++ b/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: `, 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.