Skip to content

Retune precision for monorepo false positives - #89

Closed
alxxjohn wants to merge 1 commit into
mainfrom
fix/naming-precision-followup
Closed

Retune precision for monorepo false positives#89
alxxjohn wants to merge 1 commit into
mainfrom
fix/naming-precision-followup

Conversation

@alxxjohn

@alxxjohn alxxjohn commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • harden precision rules for false positives across UI helpers, integration adapters, scripts, routing/orchestration, duplicated enum literals, and central data-client fan-in
  • keep real hidden-mutation and collaborator side-effect coverage with focused tests
  • remove the need for downstream waivers while preserving zero findings with the retuned scanner

Verification

  • env -u GOROOT GOCACHE=/private/tmp/codeguard-go-cache go test ./tests/checks -run 'Test(FunctionHiddenMutation|FunctionCommandQueryMix|QualityNaming|QualityDuplicatedKnowledge|Defensive|Design|Environment|Switch|QualityAI|LocalDesign)'
  • downstream no-waiver scan with rebuilt branch binary: total findings 0

@alxxjohn
alxxjohn force-pushed the fix/naming-precision-followup branch from 76093d6 to 7422df9 Compare July 29, 2026 01:02
@alxxjohn alxxjohn changed the title Retune precision for Legal Nest zero findings Retune precision for monorepo false positives Jul 29, 2026
@alxxjohn

Copy link
Copy Markdown
Contributor Author

Superseded by sanitized replacement PR #90.

@alxxjohn alxxjohn closed this Jul 29, 2026
@alxxjohn
alxxjohn deleted the fix/naming-precision-followup branch July 29, 2026 01:04
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