Skip to content

rule-hunter: a claim of absence carries the command that looked - #93

Closed
buzzdan wants to merge 1 commit into
mainfrom
claude/hunter-absence-evidence
Closed

buzzdan wants to merge 1 commit into
mainfrom
claude/hunter-absence-evidence

Conversation

@buzzdan

@buzzdan buzzdan commented Oct 14, 2026

Copy link
Copy Markdown
Owner

What

A hunter finding that rests on something not existing (no test file, no caller, never imported) now carries the command that looked and its empty result as evidence: an ls listing, or a grep … | wc -l that prints 0. When the budget does not allow that call, the lead goes in the not reached: line as unverified: <claim>, never as a finding.

Why

In the ts-react A/B, the R7 hunter wrote "picker.test.ts is absent" while src/pages/Devices/placement/picker.test.ts existed. The evidence protocol asked for file:line and an excerpt, but said nothing about claims of absence. This happens only sometimes: case C passed both baseline runs.

Changes

  • core/agents/rule-hunter.md: a "Claims of absence" paragraph after the evidence protocol, and one line for it under the output block.
  • The four generated plugins, regenerated.

Checks

  • task check, task lint-core, task docs:check: green.
  • Grader: buzzdan/ldd-evals PR "case C: a grader for claims that the picker test file is absent" adds no-absent-test-claim to case C in all three suites.
  • Not measured yet: case C ×2 on ts-react before and after, and go/py case C once each.

🤖 Generated with Claude Code

A hunter wrote "picker.test.ts is absent" while the file existed. The
evidence protocol asked for file:line and an excerpt for a finding, but said
nothing about findings that rest on something not existing. Such a finding now
carries the command and its empty result (an ls listing, a grep count of 0).
When the budget does not allow that call, the lead goes in the not-reached line
as unverified, never as a finding.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@buzzdan

buzzdan commented Oct 14, 2026

Copy link
Copy Markdown
Owner Author

Grader: buzzdan/ldd-evals#44

@buzzdan

buzzdan commented Oct 18, 2026

Copy link
Copy Markdown
Owner Author

Closed: #91 (merged) makes the same fix, and it also requires the search over the whole repository. The budget clause of this PR is in #99. The grader buzzdan/ldd-evals#44 stays open and works with #91.

@buzzdan buzzdan closed this Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant