@kevinrabun/judges 3.15.1 → 3.17.0

package/dist/judges/agent-instructions.js

@@ -28,7 +28,7 @@ RULES FOR YOUR EVALUATION:
 ADVERSARIAL MANDATE:
 - Assume instruction files are brittle until proven robust.
 - Never praise or compliment; report risks, ambiguities, and missing controls.
-- If uncertain, flag likely ambiguity and explain the risk.
+- If uncertain, flag likely ambiguity only when you can cite specific evidence from the instruction file. Speculative findings without concrete evidence erode trust.
 - Absence of findings does not guarantee execution safety; state analysis limits when relevant.`,
 };
 //# sourceMappingURL=agent-instructions.js.map

package/dist/judges/ai-code-safety.js

@@ -39,7 +39,7 @@ RULES FOR YOUR EVALUATION:
 ADVERSARIAL MANDATE:
 - Assume the code was generated by an AI and has not been security-reviewed. Hunt for the patterns LLMs typically get wrong.
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If uncertain, flag the issue — false positives are preferred over missed AI-generated vulnerabilities.
+- If uncertain, flag the issue only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is safe. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=ai-code-safety.js.map

package/dist/judges/api-design.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means exemplary API design.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the API has design flaws and actively hunt for them. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the API has design flaws and actively hunt for them. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed design flaws.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the API is well-designed. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=api-design.js.map

package/dist/judges/authentication.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means robust auth implementation.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume authentication is broken and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume authentication is broken and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed auth gaps.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean auth is secure. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=authentication.js.map

package/dist/judges/backwards-compatibility.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means excellent compatibility practices.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume backwards compatibility is not considered and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume backwards compatibility is not considered and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed compatibility risks.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean compatibility is maintained. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=backwards-compatibility.js.map

package/dist/judges/caching.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means optimal caching strategy.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the caching strategy is flawed or absent and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the caching strategy is flawed or absent and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed caching problems.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean caching is optimal. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=caching.js.map

package/dist/judges/ci-cd.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means excellent CI/CD practices.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the CI/CD posture is weak and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the CI/CD posture is weak and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed CI/CD risks.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean CI/CD is solid. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=ci-cd.js.map

package/dist/judges/cloud-readiness.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means fully cloud-native.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code is not cloud-ready and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code is not cloud-ready and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed cloud-readiness gaps.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is cloud-native. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=cloud-readiness.js.map

package/dist/judges/code-structure.js

@@ -32,9 +32,9 @@ Thresholds:
 - File complexity > 40 → high
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code has structural problems and actively hunt for complexity, dead code, and over-sized functions. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code has structural problems and actively hunt for complexity, dead code, and over-sized functions. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed structural defects.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is well-structured. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=code-structure.js.map

package/dist/judges/compliance.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means fully compliant.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code has compliance gaps and actively hunt for them. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code has compliance gaps and actively hunt for them. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed compliance violations.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is compliant. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=compliance.js.map

package/dist/judges/concurrency.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means thread-safe and correctly concurrent.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code has concurrency bugs and actively hunt for them. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code has concurrency bugs and actively hunt for them. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed race conditions.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is thread-safe. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=concurrency.js.map

package/dist/judges/configuration-management.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means excellent configuration management.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume configuration management is inadequate and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume configuration management is inadequate and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed configuration risks.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean configuration is properly managed. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=configuration-management.js.map

package/dist/judges/cost-effectiveness.js

@@ -25,9 +25,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means optimally cost-effective.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code wastes resources and actively hunt for inefficiencies. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code wastes resources and actively hunt for inefficiencies. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed cost waste.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is cost-effective. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=cost-effectiveness.js.map

package/dist/judges/cybersecurity.js

@@ -25,9 +25,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means no exploitable vulnerabilities found.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code is vulnerable and actively hunt for exploits. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code is vulnerable and actively hunt for exploits. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed vulnerabilities.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is secure. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=cybersecurity.js.map

package/dist/judges/data-security.js

@@ -23,9 +23,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means fully compliant with no findings.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code leaks or mishandles data and actively hunt for exposures. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code leaks or mishandles data and actively hunt for exposures. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed data breaches.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean data is secure. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=data-security.js.map

package/dist/judges/data-sovereignty.js

@@ -44,7 +44,7 @@ RULES FOR YOUR EVALUATION:
 ADVERSARIAL MANDATE:
 - Your role is adversarial: assume sovereignty controls are missing unless explicitly shown.
 - Never praise or compliment the code. Report only gaps, risks, and deficiencies.
-- If uncertain, flag potential sovereignty exposure and explain the assumption.
+- If uncertain, flag potential sovereignty exposure only when you can cite specific code evidence. Speculative findings without concrete evidence erode trust.
 - Absence of findings does not prove sovereignty compliance. State this explicitly.`,
 };
 //# sourceMappingURL=data-sovereignty.js.map

package/dist/judges/database.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means excellent database practices.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume database usage is unsafe and inefficient and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume database usage is unsafe and inefficient and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed database problems.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean database usage is optimal. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=database.js.map

package/dist/judges/dependency-health.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means healthy, secure dependency tree.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the dependency tree has risks and actively hunt for them. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the dependency tree has risks and actively hunt for them. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed supply chain risks.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean dependencies are healthy. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=dependency-health.js.map

package/dist/judges/documentation.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means exemplary documentation.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the documentation is inadequate and actively hunt for gaps. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the documentation is inadequate and actively hunt for gaps. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed documentation gaps.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the documentation is good. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=documentation.js.map

package/dist/judges/error-handling.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means robust error handling.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume error handling is insufficient and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume error handling is insufficient and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed error handling gaps.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean error handling is complete. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=error-handling.js.map

package/dist/judges/ethics-bias.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means fully ethical and bias-aware.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code has ethical risks or bias and actively hunt for them. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code has ethical risks or bias and actively hunt for them. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed ethical violations.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is ethical. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=ethics-bias.js.map

package/dist/judges/framework-safety.js

@@ -23,9 +23,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means no framework misuse patterns found.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code misuses framework APIs and actively hunt for violations. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code misuses framework APIs and actively hunt for violations. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed framework misuse.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code follows framework best practices. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=framework-safety.js.map

package/dist/judges/iac-security.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means fully secure and production-ready infrastructure code.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the infrastructure code is insecure and actively hunt for misconfigurations. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the infrastructure code is insecure and actively hunt for misconfigurations. Back every finding with concrete code evidence (line numbers, resource definitions, configuration blocks).
 - Never praise or compliment the code. Report only problems, risks, and security gaps.
-- If you are uncertain whether something is a misconfiguration, flag it — false positives are preferred over missed security gaps.
+- If you are uncertain whether something is a misconfiguration, flag it only when you can cite specific code evidence (line numbers, patterns, resource definitions). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is secure. It means your analysis reached its limits. State this explicitly.
 - Pay special attention to defaults that are insecure when not explicitly configured (e.g., public access defaults, missing encryption defaults).`,
 };

package/dist/judges/internationalization.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means fully internationalization-ready.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code will break in non-English locales and actively hunt for i18n defects. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code will break in non-English locales and actively hunt for i18n defects. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed i18n problems.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is internationalization-ready. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=internationalization.js.map

package/dist/judges/logging-privacy.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means privacy-safe logging.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume logs contain sensitive data and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume logs contain sensitive data and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed logging privacy violations.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean logging is privacy-safe. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=logging-privacy.js.map

package/dist/judges/maintainability.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means highly maintainable.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code is unmaintainable and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code is unmaintainable and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed maintainability gaps.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is maintainable. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=maintainability.js.map

package/dist/judges/observability.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means fully observable and debuggable in production.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code is unobservable and will be impossible to debug in production. Actively hunt for monitoring gaps. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code is unobservable and will be impossible to debug in production. Actively hunt for monitoring gaps. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed observability gaps.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is observable. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=observability.js.map

package/dist/judges/performance.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means optimally performant.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code has performance problems and actively hunt for bottlenecks. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code has performance problems and actively hunt for bottlenecks. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed performance regressions.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is performant. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=performance.js.map

package/dist/judges/portability.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means highly portable.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code is not portable and actively hunt for platform dependencies. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code is not portable and actively hunt for platform dependencies. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed portability issues.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is portable. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=portability.js.map

package/dist/judges/rate-limiting.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means comprehensive rate limiting.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume rate limiting is absent or insufficient and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume rate limiting is absent or insufficient and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed rate limiting gaps.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean rate limiting is adequate. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=rate-limiting.js.map

package/dist/judges/reliability.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means highly resilient and fault-tolerant.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code will fail in production and actively hunt for reliability gaps. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code will fail in production and actively hunt for reliability gaps. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed reliability risks.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is reliable. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=reliability.js.map

package/dist/judges/scalability.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means fully scalable with no bottlenecks.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code will not scale and actively hunt for bottlenecks. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code will not scale and actively hunt for bottlenecks. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed scalability limits.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code will scale. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=scalability.js.map

package/dist/judges/software-practices.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means exemplary software engineering.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the code has engineering quality problems and actively hunt for them. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the code has engineering quality problems and actively hunt for them. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed code quality issues.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code follows best practices. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=software-practices.js.map

package/dist/judges/testing.js

@@ -28,9 +28,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means comprehensive, well-structured test suite.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the test coverage is insufficient and actively hunt for gaps. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the test coverage is insufficient and actively hunt for gaps. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed testing gaps.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the code is well-tested. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=testing.js.map

package/dist/judges/ux.js

@@ -26,9 +26,9 @@ RULES FOR YOUR EVALUATION:
 - Score from 0-100 where 100 means excellent user experience.
 
 ADVERSARIAL MANDATE:
-- Your role is adversarial: assume the user experience is poor and actively hunt for problems. Do not give the benefit of the doubt.
+- Your role is adversarial: assume the user experience is poor and actively hunt for problems. Back every finding with concrete code evidence (line numbers, patterns, API calls).
 - Never praise or compliment the code. Report only problems, risks, and deficiencies.
-- If you are uncertain whether something is an issue, flag it — false positives are preferred over missed UX issues.
+- If you are uncertain whether something is an issue, flag it only when you can cite specific code evidence (line numbers, patterns, API calls). Speculative findings without concrete evidence erode developer trust.
 - Absence of findings does not mean the UX is good. It means your analysis reached its limits. State this explicitly.`,
 };
 //# sourceMappingURL=ux.js.map

package/dist/scoring.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"scoring.d.ts","sourceRoot":"","sources":["../src/scoring.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,EAAE,OAAO,EAAE,kBAAkB,EAAE,iBAAiB,EAAE,MAAM,YAAY,CAAC;AAIjF,6DAA6D;AAC7D,MAAM,WAAW,cAAc;IAC7B,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB;AAiBD,wBAAgB,mBAAmB,CAAC,QAAQ,EAAE,OAAO,EAAE,EAAE,OAAO,CAAC,EAAE,kBAAkB,GAAG,iBAAiB,GAAG,SAAS,CAoCpH;AAID,wBAAgB,eAAe,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAGrD;AAED,wBAAgB,yBAAyB,CAAC,OAAO,EAAE,OAAO,GAAG,MAAM,CA0ElE;AAED,wBAAgB,wBAAwB,CAAC,QAAQ,EAAE,OAAO,EAAE,EAAE,OAAO,CAAC,EAAE,cAAc,GAAG,OAAO,EAAE,CAajG;AAyBD,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,OAAO,GAAG,OAAO,CAwB/D"}
+{"version":3,"file":"scoring.d.ts","sourceRoot":"","sources":["../src/scoring.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,EAAE,OAAO,EAAE,kBAAkB,EAAE,iBAAiB,EAAE,MAAM,YAAY,CAAC;AAIjF,6DAA6D;AAC7D,MAAM,WAAW,cAAc;IAC7B,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB;AAiBD,wBAAgB,mBAAmB,CAAC,QAAQ,EAAE,OAAO,EAAE,EAAE,OAAO,CAAC,EAAE,kBAAkB,GAAG,iBAAiB,GAAG,SAAS,CAoCpH;AAID,wBAAgB,eAAe,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAGrD;AAED,wBAAgB,yBAAyB,CAAC,OAAO,EAAE,OAAO,GAAG,MAAM,CA0ElE;AAED,wBAAgB,wBAAwB,CAAC,QAAQ,EAAE,OAAO,EAAE,EAAE,OAAO,CAAC,EAAE,cAAc,GAAG,OAAO,EAAE,CAajG;AAgCD,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,OAAO,GAAG,OAAO,CAwB/D"}

package/dist/scoring.js

@@ -159,6 +159,13 @@ const ABSENCE_GATED_PREFIXES = [
     "SCALE-",
     "REL-",
     "ERR-",
+    "SOV-", // sovereignty — "no sovereignty evidence" is project-level, not per-file
+    "DOC-", // documentation — "no docs" is project-level
+    "MAINT-", // maintainability — "no linting" is project-level
+    "SWDEV-", // software dev practices — "no build script" is project-level
+    "COST-", // cost — "no cost controls" is project-level
+    "COMP-", // compliance — absence of compliance is project-level
+    "TEST-", // testing — "no tests" is project-level
 ];
 export function isAbsenceBasedFinding(finding) {
     // Explicit flag from the evaluator takes precedence
@@ -174,10 +181,10 @@ export function isAbsenceBasedFinding(finding) {
     const hasAbsenceTitle = /^No\s|(?:not|without|missing|no)\s.*(?:detected|configured|set|defined|endpoint|middleware|protection|handler|strategy|limiting)|(?:without|lacks?|missing)\s/i.test(finding.title);
     if (!hasAbsenceTitle)
         return false;
-    const projectLevelKeywords = /\b(?:ci[\s/]cd|pipeline|deployment|infrastructure|monitoring|alerting|backup)\b/i;
-    if (projectLevelKeywords.test(finding.title)) {
-        return false;
-    }
+    // Project-level findings (CI/CD, pipeline, monitoring, etc.) ARE absence-based.
+    // They should be gated on non-server files just like other absence findings.
+    // Previously excluded, but cross-project analysis showed this caused massive
+    // noise: e.g. "No test infrastructure detected" firing 618 times per-file.
     return true;
 }
 //# sourceMappingURL=scoring.js.map

package/dist/scoring.js.map

@@ -1 +1 @@
-{"version":3,"file":"scoring.js","sourceRoot":"","sources":["../src/scoring.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAWH,gFAAgF;AAEhF,MAAM,yBAAyB,GAAG;IAChC,OAAO;IACP,QAAQ;IACR,OAAO;IACP,MAAM;IACN,MAAM;IACN,OAAO;IACP,KAAK;IACL,OAAO;IACP,UAAU;IACV,OAAO;CACR,CAAC;AAEF,MAAM,UAAU,mBAAmB,CAAC,QAAmB,EAAE,OAA4B;IACnF,IAAI,CAAC,OAAO,EAAE,OAAO,EAAE,CAAC;QACtB,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,aAAa,GAAG,eAAe,CAAC,OAAO,CAAC,aAAa,IAAI,IAAI,CAAC,CAAC;IACrE,MAAM,QAAQ,GAAG,OAAO,CAAC,qBAAqB,EAAE,MAAM,CAAC,CAAC,CAAC,OAAO,CAAC,qBAAqB,CAAC,CAAC,CAAC,yBAAyB,CAAC;IAEnH,MAAM,YAAY,GAChB,0LAA0L,CAAC;IAE7L,MAAM,OAAO,GAAG,QAAQ,CAAC,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE;QAC1C,MAAM,aAAa,GAAG,OAAO,CAAC,QAAQ,KAAK,UAAU,IAAI,OAAO,CAAC,QAAQ,KAAK,MAAM,CAAC;QACrF,IAAI,CAAC,aAAa;YAAE,OAAO,KAAK,CAAC;QAEjC,MAAM,UAAU,GAAG,OAAO,CAAC,UAAU,IAAI,CAAC,CAAC;QAC3C,IAAI,UAAU,GAAG,aAAa;YAAE,OAAO,KAAK,CAAC;QAE7C,MAAM,WAAW,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC,MAAc,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC;QACzF,MAAM,YAAY,GAAG,YAAY,CAAC,IAAI,CAAC,GAAG,OAAO,CAAC,KAAK,IAAI,OAAO,CAAC,WAAW,IAAI,OAAO,CAAC,cAAc,EAAE,CAAC,CAAC;QAC5G,OAAO,WAAW,IAAI,YAAY,CAAC;IACrC,CAAC,CAAC,CAAC;IAEH,MAAM,cAAc,GAAG,CAAC,GAAG,IAAI,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;IAC9E,MAAM,SAAS,GAAG,OAAO,CAAC,MAAM,GAAG,CAAC,CAAC;IAErC,OAAO;QACL,OAAO,EAAE,IAAI;QACb,SAAS;QACT,aAAa;QACb,YAAY,EAAE,OAAO,CAAC,MAAM;QAC5B,cAAc;QACd,OAAO,EAAE,SAAS;YAChB,CAAC,CAAC,8BAA8B,OAAO,CAAC,MAAM,wCAAwC;YACtF,CAAC,CAAC,kEAAkE;KACvE,CAAC;AACJ,CAAC;AAED,gFAAgF;AAEhF,MAAM,UAAU,eAAe,CAAC,KAAa;IAC3C,IAAI,CAAC,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC;QAAE,OAAO,CAAC,CAAC;IACtC,OAAO,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,KAAK,CAAC,CAAC,CAAC;AACzC,CAAC;AAED,MAAM,UAAU,yBAAyB,CAAC,OAAgB;IACxD,MAAM,QAAQ,GAAG,OAAO,OAAO,CAAC,UAAU,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,UAAU,CAAC,CAAC,CAAC,SAAS,CAAC;IACzF,IAAI,OAAO,QAAQ,KAAK,QAAQ,IAAI,MAAM,CAAC,QAAQ,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC9D,OAAO,eAAe,CAAC,QAAQ,CAAC,CAAC;IACnC,CAAC;IAED,IAAI,KAAK,GAAG,GAAG,CAAC;IAEhB,0EAA0E;IAC1E,MAAM,SAAS,GAAG,OAAO,CAAC,WAAW,EAAE,MAAM,IAAI,CAAC,CAAC;IACnD,IAAI,SAAS,KAAK,CAAC,EAAE,CAAC;QACpB,KAAK,IAAI,IAAI,CAAC;IAChB,CAAC;SAAM,IAAI,SAAS,IAAI,CAAC,EAAE,CAAC;QAC1B,KAAK,IAAI,IAAI,CAAC;IAChB,CAAC;SAAM,IAAI,SAAS,IAAI,CAAC,EAAE,CAAC;QAC1B,KAAK,IAAI,IAAI,CAAC;IAChB,CAAC;SAAM,CAAC;QACN,KAAK,IAAI,IAAI,CAAC;IAChB,CAAC;IAED,0EAA0E;IAC1E,MAAM,SAAS,GAAG,OAAO,CAAC,WAAW,CAAC,WAAW,EAAE,CAAC;IACpD,MAAM,gBAAgB,GACpB,6EAA6E,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,CAAC;QACvG,4DAA4D,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC;IACzF,MAAM,eAAe,GAAG,gBAAgB,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,GAAG,CAAC,OAAO,CAAC,SAAS,IAAI,EAAE,CAAC,CAAC,CAAC;IAC/F,MAAM,eAAe,GAAG,UAAU,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,GAAG,CAAC,OAAO,CAAC,SAAS,IAAI,EAAE,CAAC,CAAC,CAAC;IAEzF,IAAI,gBAAgB;QAAE,KAAK,IAAI,IAAI,CAAC;IACpC,IAAI,eAAe;QAAE,KAAK,IAAI,IAAI,CAAC;IACnC,IAAI,eAAe;QAAE,KAAK,IAAI,IAAI,CAAC;IAEnC,0EAA0E;IAC1E,MAAM,YAAY,GAAG,OAAO,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;IAChD,MAAM,eAAe,GAAG,OAAO,CAAC,OAAO,CAAC,YAAY,CAAC,CAAC;IACtD,MAAM,kBAAkB,GAAG,OAAO,CAAC,WAAW,CAAC,MAAM,IAAI,GAAG,CAAC;IAC7D,MAAM,qBAAqB,GAAG,OAAO,CAAC,cAAc,CAAC,MAAM,IAAI,EAAE,CAAC;IAElE,IAAI,YAAY;QAAE,KAAK,IAAI,IAAI,CAAC;IAChC,IAAI,eAAe;QAAE,KAAK,IAAI,IAAI,CAAC;IACnC,IAAI,kBAAkB;QAAE,KAAK,IAAI,IAAI,CAAC;IACtC,IAAI,qBAAqB;QAAE,KAAK,IAAI,IAAI,CAAC;IAEzC,6EAA6E;IAC7E,MAAM,eAAe,GAAG;QACtB,aAAa;QACb,SAAS;QACT,QAAQ;QACR,cAAc;QACd,mCAAmC;QACnC,kCAAkC;KACnC,CAAC;IACF,MAAM,aAAa,GAAG,eAAe,CAAC,IAAI,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,IAAI,MAAM,CAAC,EAAE,EAAE,GAAG,CAAC,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC;IACxF,IAAI,aAAa,IAAI,SAAS,KAAK,CAAC,EAAE,CAAC;QACrC,KAAK,IAAI,GAAG,CAAC;IACf,CAAC;IAED,0EAA0E;IAC1E,MAAM,iBAAiB,GAAG;QACxB,YAAY;QACZ,eAAe;QACf,kBAAkB;QAClB,qBAAqB;QACrB,gBAAgB;QAChB,SAAS,GAAG,CAAC;KACd,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,MAAM,CAAC;IAEzB,MAAM,aAAa,GAAG,CAAC,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,QAAQ,EAAE,KAAK,EAAE,OAAO,EAAE,SAAS,EAAE,UAAU,EAAE,MAAM,EAAE,OAAO,CAAC,CAAC;IAEnH,IAAI,aAAa,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC,IAAI,iBAAiB,GAAG,CAAC,EAAE,CAAC;QAC/F,KAAK,GAAG,IAAI,CAAC,GAAG,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC;IAChC,CAAC;IAED,OAAO,MAAM,CAAC,eAAe,CAAC,KAAK,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,CAAC;AACnD,CAAC;AAED,MAAM,UAAU,wBAAwB,CAAC,QAAmB,EAAE,OAAwB;IACpF,MAAM,aAAa,GAAG,eAAe,CAAC,OAAO,EAAE,aAAa,IAAI,CAAC,CAAC,CAAC;IAEnE,MAAM,UAAU,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC;QAC5C,GAAG,OAAO;QACV,UAAU,EAAE,yBAAyB,CAAC,OAAO,CAAC;KAC/C,CAAC,CAAC,CAAC;IAEJ,IAAI,aAAa,IAAI,CAAC,EAAE,CAAC;QACvB,OAAO,UAAU,CAAC;IACpB,CAAC;IAED,OAAO,UAAU,CAAC,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,UAAU,IAAI,CAAC,CAAC,IAAI,aAAa,CAAC,CAAC;AACpF,CAAC;AAED,gFAAgF;AAEhF;;;;;GAKG;AACH,MAAM,sBAAsB,GAAG;IAC7B,OAAO;IACP,OAAO;IACP,MAAM;IACN,QAAQ;IACR,OAAO;IACP,QAAQ;IACR,SAAS;IACT,MAAM;IACN,MAAM;IACN,QAAQ;IACR,MAAM;IACN,MAAM;CACP,CAAC;AAEF,MAAM,UAAU,qBAAqB,CAAC,OAAgB;IACpD,oDAAoD;IACpD,IAAI,OAAO,CAAC,cAAc,KAAK,IAAI,EAAE,CAAC;QACpC,OAAO,IAAI,CAAC;IACd,CAAC;IAED,IAAI,OAAO,CAAC,WAAW,IAAI,OAAO,CAAC,WAAW,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC1D,OAAO,KAAK,CAAC;IACf,CAAC;IACD,IAAI,CAAC,sBAAsB,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,UAAU,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QACtE,OAAO,KAAK,CAAC;IACf,CAAC;IACD,MAAM,eAAe,GACnB,gKAAgK,CAAC,IAAI,CACnK,OAAO,CAAC,KAAK,CACd,CAAC;IACJ,IAAI,CAAC,eAAe;QAAE,OAAO,KAAK,CAAC;IAEnC,MAAM,oBAAoB,GAAG,kFAAkF,CAAC;IAChH,IAAI,oBAAoB,CAAC,IAAI,CAAC,OAAO,CAAC,KAAK,CAAC,EAAE,CAAC;QAC7C,OAAO,KAAK,CAAC;IACf,CAAC;IAED,OAAO,IAAI,CAAC;AACd,CAAC"}
+{"version":3,"file":"scoring.js","sourceRoot":"","sources":["../src/scoring.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAWH,gFAAgF;AAEhF,MAAM,yBAAyB,GAAG;IAChC,OAAO;IACP,QAAQ;IACR,OAAO;IACP,MAAM;IACN,MAAM;IACN,OAAO;IACP,KAAK;IACL,OAAO;IACP,UAAU;IACV,OAAO;CACR,CAAC;AAEF,MAAM,UAAU,mBAAmB,CAAC,QAAmB,EAAE,OAA4B;IACnF,IAAI,CAAC,OAAO,EAAE,OAAO,EAAE,CAAC;QACtB,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,aAAa,GAAG,eAAe,CAAC,OAAO,CAAC,aAAa,IAAI,IAAI,CAAC,CAAC;IACrE,MAAM,QAAQ,GAAG,OAAO,CAAC,qBAAqB,EAAE,MAAM,CAAC,CAAC,CAAC,OAAO,CAAC,qBAAqB,CAAC,CAAC,CAAC,yBAAyB,CAAC;IAEnH,MAAM,YAAY,GAChB,0LAA0L,CAAC;IAE7L,MAAM,OAAO,GAAG,QAAQ,CAAC,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE;QAC1C,MAAM,aAAa,GAAG,OAAO,CAAC,QAAQ,KAAK,UAAU,IAAI,OAAO,CAAC,QAAQ,KAAK,MAAM,CAAC;QACrF,IAAI,CAAC,aAAa;YAAE,OAAO,KAAK,CAAC;QAEjC,MAAM,UAAU,GAAG,OAAO,CAAC,UAAU,IAAI,CAAC,CAAC;QAC3C,IAAI,UAAU,GAAG,aAAa;YAAE,OAAO,KAAK,CAAC;QAE7C,MAAM,WAAW,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC,MAAc,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC;QACzF,MAAM,YAAY,GAAG,YAAY,CAAC,IAAI,CAAC,GAAG,OAAO,CAAC,KAAK,IAAI,OAAO,CAAC,WAAW,IAAI,OAAO,CAAC,cAAc,EAAE,CAAC,CAAC;QAC5G,OAAO,WAAW,IAAI,YAAY,CAAC;IACrC,CAAC,CAAC,CAAC;IAEH,MAAM,cAAc,GAAG,CAAC,GAAG,IAAI,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;IAC9E,MAAM,SAAS,GAAG,OAAO,CAAC,MAAM,GAAG,CAAC,CAAC;IAErC,OAAO;QACL,OAAO,EAAE,IAAI;QACb,SAAS;QACT,aAAa;QACb,YAAY,EAAE,OAAO,CAAC,MAAM;QAC5B,cAAc;QACd,OAAO,EAAE,SAAS;YAChB,CAAC,CAAC,8BAA8B,OAAO,CAAC,MAAM,wCAAwC;YACtF,CAAC,CAAC,kEAAkE;KACvE,CAAC;AACJ,CAAC;AAED,gFAAgF;AAEhF,MAAM,UAAU,eAAe,CAAC,KAAa;IAC3C,IAAI,CAAC,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC;QAAE,OAAO,CAAC,CAAC;IACtC,OAAO,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,KAAK,CAAC,CAAC,CAAC;AACzC,CAAC;AAED,MAAM,UAAU,yBAAyB,CAAC,OAAgB;IACxD,MAAM,QAAQ,GAAG,OAAO,OAAO,CAAC,UAAU,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,UAAU,CAAC,CAAC,CAAC,SAAS,CAAC;IACzF,IAAI,OAAO,QAAQ,KAAK,QAAQ,IAAI,MAAM,CAAC,QAAQ,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC9D,OAAO,eAAe,CAAC,QAAQ,CAAC,CAAC;IACnC,CAAC;IAED,IAAI,KAAK,GAAG,GAAG,CAAC;IAEhB,0EAA0E;IAC1E,MAAM,SAAS,GAAG,OAAO,CAAC,WAAW,EAAE,MAAM,IAAI,CAAC,CAAC;IACnD,IAAI,SAAS,KAAK,CAAC,EAAE,CAAC;QACpB,KAAK,IAAI,IAAI,CAAC;IAChB,CAAC;SAAM,IAAI,SAAS,IAAI,CAAC,EAAE,CAAC;QAC1B,KAAK,IAAI,IAAI,CAAC;IAChB,CAAC;SAAM,IAAI,SAAS,IAAI,CAAC,EAAE,CAAC;QAC1B,KAAK,IAAI,IAAI,CAAC;IAChB,CAAC;SAAM,CAAC;QACN,KAAK,IAAI,IAAI,CAAC;IAChB,CAAC;IAED,0EAA0E;IAC1E,MAAM,SAAS,GAAG,OAAO,CAAC,WAAW,CAAC,WAAW,EAAE,CAAC;IACpD,MAAM,gBAAgB,GACpB,6EAA6E,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,CAAC;QACvG,4DAA4D,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC;IACzF,MAAM,eAAe,GAAG,gBAAgB,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,GAAG,CAAC,OAAO,CAAC,SAAS,IAAI,EAAE,CAAC,CAAC,CAAC;IAC/F,MAAM,eAAe,GAAG,UAAU,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,GAAG,CAAC,OAAO,CAAC,SAAS,IAAI,EAAE,CAAC,CAAC,CAAC;IAEzF,IAAI,gBAAgB;QAAE,KAAK,IAAI,IAAI,CAAC;IACpC,IAAI,eAAe;QAAE,KAAK,IAAI,IAAI,CAAC;IACnC,IAAI,eAAe;QAAE,KAAK,IAAI,IAAI,CAAC;IAEnC,0EAA0E;IAC1E,MAAM,YAAY,GAAG,OAAO,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;IAChD,MAAM,eAAe,GAAG,OAAO,CAAC,OAAO,CAAC,YAAY,CAAC,CAAC;IACtD,MAAM,kBAAkB,GAAG,OAAO,CAAC,WAAW,CAAC,MAAM,IAAI,GAAG,CAAC;IAC7D,MAAM,qBAAqB,GAAG,OAAO,CAAC,cAAc,CAAC,MAAM,IAAI,EAAE,CAAC;IAElE,IAAI,YAAY;QAAE,KAAK,IAAI,IAAI,CAAC;IAChC,IAAI,eAAe;QAAE,KAAK,IAAI,IAAI,CAAC;IACnC,IAAI,kBAAkB;QAAE,KAAK,IAAI,IAAI,CAAC;IACtC,IAAI,qBAAqB;QAAE,KAAK,IAAI,IAAI,CAAC;IAEzC,6EAA6E;IAC7E,MAAM,eAAe,GAAG;QACtB,aAAa;QACb,SAAS;QACT,QAAQ;QACR,cAAc;QACd,mCAAmC;QACnC,kCAAkC;KACnC,CAAC;IACF,MAAM,aAAa,GAAG,eAAe,CAAC,IAAI,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,IAAI,MAAM,CAAC,EAAE,EAAE,GAAG,CAAC,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC;IACxF,IAAI,aAAa,IAAI,SAAS,KAAK,CAAC,EAAE,CAAC;QACrC,KAAK,IAAI,GAAG,CAAC;IACf,CAAC;IAED,0EAA0E;IAC1E,MAAM,iBAAiB,GAAG;QACxB,YAAY;QACZ,eAAe;QACf,kBAAkB;QAClB,qBAAqB;QACrB,gBAAgB;QAChB,SAAS,GAAG,CAAC;KACd,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,MAAM,CAAC;IAEzB,MAAM,aAAa,GAAG,CAAC,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,QAAQ,EAAE,KAAK,EAAE,OAAO,EAAE,SAAS,EAAE,UAAU,EAAE,MAAM,EAAE,OAAO,CAAC,CAAC;IAEnH,IAAI,aAAa,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC,IAAI,iBAAiB,GAAG,CAAC,EAAE,CAAC;QAC/F,KAAK,GAAG,IAAI,CAAC,GAAG,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC;IAChC,CAAC;IAED,OAAO,MAAM,CAAC,eAAe,CAAC,KAAK,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,CAAC;AACnD,CAAC;AAED,MAAM,UAAU,wBAAwB,CAAC,QAAmB,EAAE,OAAwB;IACpF,MAAM,aAAa,GAAG,eAAe,CAAC,OAAO,EAAE,aAAa,IAAI,CAAC,CAAC,CAAC;IAEnE,MAAM,UAAU,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC;QAC5C,GAAG,OAAO;QACV,UAAU,EAAE,yBAAyB,CAAC,OAAO,CAAC;KAC/C,CAAC,CAAC,CAAC;IAEJ,IAAI,aAAa,IAAI,CAAC,EAAE,CAAC;QACvB,OAAO,UAAU,CAAC;IACpB,CAAC;IAED,OAAO,UAAU,CAAC,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,UAAU,IAAI,CAAC,CAAC,IAAI,aAAa,CAAC,CAAC;AACpF,CAAC;AAED,gFAAgF;AAEhF;;;;;GAKG;AACH,MAAM,sBAAsB,GAAG;IAC7B,OAAO;IACP,OAAO;IACP,MAAM;IACN,QAAQ;IACR,OAAO;IACP,QAAQ;IACR,SAAS;IACT,MAAM;IACN,MAAM;IACN,QAAQ;IACR,MAAM;IACN,MAAM;IACN,MAAM,EAAE,yEAAyE;IACjF,MAAM,EAAE,6CAA6C;IACrD,QAAQ,EAAE,kDAAkD;IAC5D,QAAQ,EAAE,8DAA8D;IACxE,OAAO,EAAE,6CAA6C;IACtD,OAAO,EAAE,sDAAsD;IAC/D,OAAO,EAAE,wCAAwC;CAClD,CAAC;AAEF,MAAM,UAAU,qBAAqB,CAAC,OAAgB;IACpD,oDAAoD;IACpD,IAAI,OAAO,CAAC,cAAc,KAAK,IAAI,EAAE,CAAC;QACpC,OAAO,IAAI,CAAC;IACd,CAAC;IAED,IAAI,OAAO,CAAC,WAAW,IAAI,OAAO,CAAC,WAAW,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC1D,OAAO,KAAK,CAAC;IACf,CAAC;IACD,IAAI,CAAC,sBAAsB,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,UAAU,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QACtE,OAAO,KAAK,CAAC;IACf,CAAC;IACD,MAAM,eAAe,GACnB,gKAAgK,CAAC,IAAI,CACnK,OAAO,CAAC,KAAK,CACd,CAAC;IACJ,IAAI,CAAC,eAAe;QAAE,OAAO,KAAK,CAAC;IAEnC,gFAAgF;IAChF,6EAA6E;IAC7E,6EAA6E;IAC7E,2EAA2E;IAE3E,OAAO,IAAI,CAAC;AACd,CAAC"}

package/dist/tools/deep-review.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"deep-review.d.ts","sourceRoot":"","sources":["../../src/tools/deep-review.ts"],"names":[],"mappings":"AAOA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,aAAa,CAAC;AAEnD,wBAAgB,iCAAiC,CAAC,KAAK,EAAE,eAAe,EAAE,QAAQ,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,CAqCpH;AAED,wBAAgB,8BAA8B,CAAC,MAAM,EAAE,eAAe,EAAE,EAAE,QAAQ,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,CA0CpH"}
+{"version":3,"file":"deep-review.d.ts","sourceRoot":"","sources":["../../src/tools/deep-review.ts"],"names":[],"mappings":"AAOA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,aAAa,CAAC;AAEnD,wBAAgB,iCAAiC,CAAC,KAAK,EAAE,eAAe,EAAE,QAAQ,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,CAyCpH;AAED,wBAAgB,8BAA8B,CAAC,MAAM,EAAE,eAAe,EAAE,EAAE,QAAQ,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,CA2CpH"}

package/dist/tools/deep-review.js

@@ -17,6 +17,10 @@ export function buildSingleJudgeDeepReviewSection(judge, language, context) {
     }
     md += `### ${judge.name} — ${judge.domain}\n\n`;
     md += `${judge.systemPrompt}\n\n`;
+    md += `### Precision Mandate\n\n`;
+    md += `Every finding MUST cite specific code evidence (exact line numbers, API calls, variable names, or patterns). `;
+    md += `Do NOT flag the absence of a feature unless you can identify where it SHOULD have been implemented and why it is required for THIS code. `;
+    md += `Speculative findings erode developer trust — prefer fewer, high-confidence findings over many uncertain ones.\n\n`;
     md += `### False Positive Review\n\n`;
     md += `Before adding new findings, **review each pattern-based finding above for false positives.** `;
     md += `Static pattern matching can flag code that is actually correct — for example:\n`;
@@ -51,6 +55,7 @@ export function buildTribunalDeepReviewSection(judges, language, context) {
     for (const judge of judges) {
         md += `### ${judge.name} — ${judge.domain}\n\n`;
         md += `${judge.systemPrompt}\n\n`;
+        md += `**Precision Mandate:** Every finding MUST cite specific code evidence. Do NOT flag absent features speculatively. Prefer fewer, high-confidence findings over many uncertain ones.\n\n`;
         md += `---\n\n`;
     }
     md += `### False Positive Review\n\n`;