docs(README): update real-app precision to 4/4 = 100% after v0.53.1 validation#270
Merged
Merged
Conversation
Spoonworks v0.53.1 validation (run si4uxdehzj5v6od6027pkt3o) emitted 4 clusters, all real `vulnerable_dependency_high`. The missing_state_change FP that lingered in v0.52 cleared after PR #269 restored the execute.ts mutation-count threading dropped by PR #268's squash merge. Honest framing: includes the camofox cache failure caveat (3047/3338 tests completed). The 4 real-bug clusters were captured before the env issue triggered `max_infra_failures`.
|
✅ BugHunter Calibration | | 2026-05-16 Overall: tp=0 fp=0 fn=0 precision=1 recall=1 f1=0
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Spoonworks v0.53.1 validation (run `si4uxdehzj5v6od6027pkt3o`, 2026-05-16) emitted 4 clusters, all real `vulnerable_dependency_high` confirmed against `npm audit`. The missing_state_change FP that lingered in v0.52 cleared after PR #269 restored the execute.ts mutation-count threading that PR #268's squash merge silently dropped.
Trajectory now
Caveat (kept in the README)
The v0.53.1 run hit a camofox cache issue mid-execution (`~/.cache/camoufox/version.json` was missing → `camoufox fetch` required) and stopped at `max_infra_failures` with 3047/3338 UI tests completed. Precision is over what completed; the four real-bug clusters were captured before the env issue triggered.
Not a BugHunter issue — env state. Future runs from a clean camofox cache should complete the full test plan and confirm the number sticks.
🤖 Generated with Claude Code