@kevinrabun/judges 3.111.0 → 3.113.0

package/CHANGELOG.md

@@ -1,2741 +0,0 @@
-# Changelog
-
-All notable changes to **@kevinrabun/judges** are documented here.
-
-## [3.111.0] — 2026-03-14
-
-### Added
-- **finding-resolution-workflow** — Guide through severity-based resolution workflows with step checklists
-- **review-quality-baseline** — Compare current review quality against historical baseline
-- **finding-context-link** — Link findings to relevant documentation via keyword matching
-- **review-team-velocity** — Track team review velocity metrics with trend detection
-- **finding-auto-priority** — Auto-prioritise findings with multi-factor scoring (P0–P4)
-- **review-retrospective** — Generate review retrospective summaries (went well, needs improvement, action items)
-- **finding-dependency-impact** — Show impact of dependency-related findings and blast radius
-- **review-mentor-suggest** — Suggest mentor pairings based on expertise gaps in review history
-- **finding-cluster-summary** — Summarise finding clusters by domain with severity breakdown
-
-## [3.110.0] — 2026-03-14
-
-### Added
-- **finding-risk-label** — Label findings with risk categories (exploitable, data-loss, compliance, etc.)
-- **review-feedback-summary** — Summarize reviewer feedback trends from review history
-- **finding-fix-chain** — Chain related fixes together for batch remediation
-- **review-config-health** — Assess configuration health and suggest improvements
-- **finding-owner-notify** — Generate ownership-based notification lists for findings
-- **review-progress-report** — Generate progress reports from review history
-- **finding-patch-chain** — Link and order patches for safe sequential application
-- **review-engagement-score** — Score team engagement with code reviews
-- **finding-effort-rank** — Rank findings by estimated fix effort
-
-## [3.109.0] — 2026-03-14
-
-### Added
-- **finding-compliance-tag** — Tag findings with compliance framework identifiers (SOC2, PCI-DSS, GDPR)
-- **review-team-coverage** — Show review coverage distribution across team members
-- **finding-severity-rebalance** — Rebalance finding severities based on project context
-- **review-stakeholder-notify** — Format notifications for different stakeholder roles
-- **finding-fix-playbook** — Generate step-by-step fix playbooks for common finding patterns
-- **review-adoption-score** — Calculate project adoption readiness score
-- **finding-dedup-merge** — Merge duplicate findings across review runs
-- **review-team-rotation** — Manage reviewer rotation schedules
-- **review-goal-track** — Track team review quality goals over time
-
-## [3.108.0] — 2026-03-14
-
-### Added
-- Action item generation: review-action-item-gen
-- Policy enforcement: review-policy-enforce
-- Time-to-fix estimates: finding-time-to-fix
-- Sprint planning: review-sprint-plan
-- Finding ancestry tracing: finding-ancestry-trace
-- Escalation paths: review-escalation-path
-- Remediation cost estimates: finding-remediation-cost
-- Review digest generation: review-digest-gen
-- Recurrence checking: finding-recurrence-check
-
-## [3.107.0] — 2026-03-14
-
-### Added
-- Auto-fix suggestions: finding-auto-fix-suggest
-- Scope-based finding filter: finding-scope-filter
-- Finding noise reduction: finding-noise-reduce
-- Release gate evaluation: review-release-gate
-- Code ownership mapping: review-code-ownership
-- Batch triage: finding-batch-triage
-- PR label suggestions: review-pr-label-suggest
-- Confidence boost analysis: finding-confidence-boost
-- Review cadence analysis: review-review-cadence
-
-## [3.106.0] — 2026-03-14
-
-### Added
-- Quality gate evaluation: review-quality-gate
-- Reopened finding detection: finding-reopen-detect
-- Finding priority ranking: finding-priority-rank
-- Dependency risk review: review-dependency-review
-- Merge readiness assessment: review-merge-readiness
-- Security posture analysis: review-security-posture
-- Knowledge capture: review-knowledge-capture
-- Onboarding checklist: review-onboarding-check
-- Regression detection: finding-regression-detect
-
-## [3.105.0] — 2026-03-14
-
-### Added
-- Risk matrix view: review-risk-matrix
-- Approval criteria checks: review-approval-criteria
-- Finding context summaries: finding-context-summary
-- Changelog impact assessment: review-changelog-impact
-- Commit quality scoring: review-commit-quality
-- Auto-categorize findings: finding-auto-categorize
-- Stale finding cleanup: review-stale-finding-clean
-- Impact radius analysis: finding-impact-radius
-- Reviewer matching: review-reviewer-match
-
-## [3.104.0] — 2026-03-14
-
-### Added
-- Review template suggestions: review-template-suggest
-- Code hotspot detection: finding-hotspot-detect
-- Code health scoring: review-code-health-score
-- Review velocity tracking: review-velocity-track
-- Cross-file finding links: finding-cross-file-link
-- PR size analysis: review-pr-size-check
-- Review focus areas: review-focus-area
-- Team review analytics: review-team-analytics
-- Similar finding matching: finding-similar-match
-
-## [3.103.0] — 2026-03-14
-
-### Added
-- Confidence explainability: review-confidence-explain
-- Cross-branch finding merge: finding-merge-strategy
-- Review scope suggestions: review-scope-suggest
-- AI feedback loop: review-ai-feedback-loop
-- Finding trend alerts: finding-trend-alert
-- Workload balancing: review-workload-balance
-- Smart deduplication: finding-dedup-smart
-- Annotation export: finding-annotation-export
-- CI pipeline insights: review-ci-insight
-
-## [3.102.0] — 2026-03-14
-
-### Added
-- Quality trend tracking: review-quality-trend
-- Batch finding suppression: finding-batch-suppress
-- Severity drift detection: finding-severity-drift
-- PR comment generation: review-pr-comment-gen
-- Finding dependency linking: finding-dependency-link
-- Reviewer role assignment: review-role-assignment
-- Archived review search: review-archive-search
-- Incident linking: review-incident-link
-- Finding search index: finding-search-index
-
-## [3.101.0] — 2026-03-14
-
-### Added
-- Configure custom judge settings per project: review-custom-judge-config
-- Manage branch-level review policies: review-branch-policy
-- Detect recurring findings across review runs: finding-recurrence-detect
-- Check health of Judges integrations: review-integration-health
-- Export review metrics for external dashboards: review-metric-export
-- Assign ownership of findings to team members: finding-ownership-assign
-- Generate notification digests for review activity: review-notification-digest
-- View and manage review access logs: review-access-log
-- Manage tags for reviews and findings: review-tag-manager
-
-## [3.100.0] — 2026-03-14
-
-### Added
-- Auto-triage findings by severity, confidence, and rules: finding-auto-triage
-- Generate stakeholder-facing summaries from review verdicts: review-stakeholder-report
-- Assess impact of code changes on existing findings: finding-change-impact
-- Configure deployment gates with threshold-based blocking: review-deployment-gate
-- Manage per-environment review configurations: review-environment-config
-- Track and learn from false positive patterns: finding-false-positive-learn
-- Synchronize review configs across multiple repositories: review-multi-repo-sync
-- Replay and inspect past review sessions: review-session-replay
-- Enrich findings with surrounding code context: finding-context-enrich
-
-## [3.99.0] — 2026-03-14
-
-### Added
-- Auto-suppress findings matching criteria: finding-auto-suppress
-- Generate structured review comments from findings: review-review-comments
-- Role-based permission management for review workflows: review-permission-model
-- Onboard a repository to Judges with config and baseline: review-repo-onboard
-- Manage finding dismissals with reasons and audit trail: finding-dismiss-workflow
-- Configure local data retention policies and cleanup: review-data-retention
-- Check if findings reference reachable code paths: finding-reachability-check
-- Export audit data in JSON/CSV for compliance: review-audit-export
-- Monitor review pipeline and integration status: review-pipeline-status
-
-## [3.98.0] — 2026-03-14
-
-### Added
-- Analyze review findings distribution by language: review-language-profile
-- Look up CWE details for finding rule IDs: finding-cwe-lookup
-- Generate CI/CD integration configs (GitHub Actions, GitLab, Azure Pipelines, Jenkins): review-cicd-integrate
-- Preview how patches would modify source files: finding-patch-preview
-- Organization-wide review dashboard: review-org-dashboard
-- Detect duplicate or near-duplicate findings: finding-duplicate-detect
-- Create urgency x impact priority matrix: finding-priority-matrix
-- Configure SLA targets for review resolution: review-sla-config
-- Archive and manage historical review reports: review-report-archive
-
-## [3.97.0] — 2026-03-14
-
-### Added
-- Define and enforce local code-review policies: review-policy-engine
-- Configure webhook endpoints for review events: review-webhook-dispatch
-- Calculate composite risk scores for findings: finding-risk-score
-- Map findings to compliance frameworks (OWASP, CWE, PCI-DSS): review-compliance-map
-- Forecast finding trends from historical data: finding-trend-forecast
-- Rank findings by estimated business impact: finding-impact-rank
-- Generate phased rollout plans for adoption: review-rollout-plan
-- Add contextual annotations to findings: finding-annotation-layer
-- Configure quality gates for review pipelines: review-gate-config
-
-## [3.96.0] — 2026-03-14
-
-### Added
-- Apply suggested fixes in bulk across findings: review-bulk-apply
-- Severity distribution heatmap visualization: finding-severity-heatmap
-- Migrate configs between Judges versions: review-config-migrate
-- Compare review history across time periods: review-history-compare
-- Team-level review dashboard with aggregates: review-team-dashboard
-- Calibrate confidence thresholds from feedback: finding-confidence-calibrate
-- Transform review output between formats: review-output-transform
-- Track Judges adoption metrics over time: review-adoption-metrics
-- Initialize workspace with Judges config files: review-workspace-init
-
-## [3.95.0] — 2026-03-14
-
-### Added
-- Aggregate review dashboard with key metrics: review-summary-dashboard
-- Format findings for merge/pull request comments: review-merge-request
-- Group findings by source file path: finding-groupby-file
-- Deduplicate findings across multiple review files: finding-dedup-cross
-- Select review scope by path patterns and extensions: review-scope-select
-- Export review data in API-compatible JSON format: review-api-export
-- Map correlations between related findings: finding-correlation-map
-- Library of reusable review templates: review-template-library
-- Configure notification preferences for review results: review-notification-config
-
-## [3.94.0] — 2026-03-14
-
-### Added
-- Interactive quickstart guide for new users: review-quickstart
-- Step-by-step finding walkthrough sessions: review-interactive
-- Detailed finding explanations with context: finding-explain
-- Sync review results to IDE formats (VSCode/JetBrains): review-ide-sync
-- Multi-criteria finding filtering and viewing: finding-filter-view
-- Per-tenant/team configuration profiles: review-tenant-config
-- Surrounding code context for findings: finding-code-context
-- Finding resolution status tracking over time: finding-resolution-track
-- Team onboarding checklists for adoption: review-onboard-checklist
-
-## [3.93.0] — 2026-03-14
-
-### Added
-- Format review summaries for Slack-compatible output: review-slack-format
-- Generate config templates for common review scenarios: review-config-template
-- Suggest fixes for findings with code-level recommendations: finding-fix-suggest
-- Track review progress across multiple runs: review-progress-track
-- Map findings to code owners and maintainers: finding-ownership-map
-- Manage scheduled report generation: review-report-schedule
-- Build finding relationship graphs for dependency analysis: finding-link-graph
-- Maintain review audit trails with full history: review-audit-trail
-- Generate compliance reports from review findings: review-compliance-report
-
-## [3.92.0] — 2026-03-14
-
-### Added
-- Auto-group findings into logical categories by content analysis: finding-auto-group
-- Manage finding suppression lists with expiry support: finding-suppression-list
-- Show plugin loading status and domain filtering: review-plugin-status
-- Cross-reference findings across multiple review files: finding-cross-ref
-- CI gate integration with configurable pass/fail policies: review-ci-gate
-- Team review statistics with aggregated metrics: review-team-stats
-- Detect recurring finding patterns and co-occurrences: finding-pattern-detect
-- Identify review coverage gaps and missing judges: review-coverage-gap
-- Track review feedback loop with trend analysis: review-feedback-loop
-
-## [3.91.0] — 2026-03-14
-
-### Added
-- Merge multiple configuration files with conflict detection: review-merge-config
-- Map finding hotspots by line range buckets: finding-hotspot-map
-- Summarize parallel review runs with consensus analysis: review-parallel-run
-- Export findings as GitHub Actions, inline, or JSON annotations: review-annotation-export
-- Estimate finding blast radius with risk scoring: finding-blast-radius
-- Compute multi-dimension quality score with grading: review-quality-score
-- Onboarding wizard with focus-based judge suggestions: review-onboard-wizard
-- Pre-warm review cache for faster subsequent runs: review-cache-warm
-- Enrich findings with judge and domain metadata: finding-metadata-enrich
-
-## [3.90.0] — 2026-03-14
-
-### Added
-- Batch review processing for multiple verdict files: review-batch-mode
-- Finding trend analysis across historical reports: finding-trend-analysis
-- Automatic content-based finding tagging: finding-auto-tag
-- Webhook notification configuration and preview: review-webhook-notify
-- Evidence collection with source code snippets: finding-evidence-collect
-- Compliance gate with configurable policies: review-compliance-gate
-- Finding resolution tracker with sync and status updates: finding-resolution-tracker
-- Threshold tuning suggestions based on historical data: review-threshold-tune
-- Finding cluster grouping by rule prefix: finding-cluster-group
-
-## [3.89.0] — 2026-03-14
-
-### Added
-- Review scope limiter to filter findings by prefix or severity: review-scope-limit
-- Finding regression check comparing current vs baseline verdicts: finding-regression-check
-- Finding fix validation to verify patches and estimate effort: finding-fix-validation
-- Dashboard data generator from verdict reports: review-dashboard-data
-- Finding category mapping with keyword-based classification: finding-category-map
-- Deduplicated findings report with occurrence counts: finding-dedup-report
-- Review performance profiler with judge and source metrics: review-perf-profile
-- False positive tracking log with add/remove/check actions: finding-false-positive-log
-- Review guardrails for enforcing quality gates (no-critical, min-score, max-findings): review-guardrail
-
-## [3.88.0] — 2026-03-14
-
-### Added
-- Dependency tree: finding-dependency-tree (visualize finding dependency relationships)
-- CI integration: review-ci-integration (generate CI pipeline configuration)
-- Comparative review: review-comparative (compare two verdict reports side by side)
-- Suppression audit: finding-suppression-audit (audit suppressed/ignored findings)
-- Custom rules: review-custom-rule (create and manage custom review rules)
-- Notifications: review-notification (configure review notification settings)
-- Age analysis: finding-age-analysis (analyze finding age and lifecycle)
-- Template export: review-template-export (export review templates for reuse)
-- Correlation: finding-correlation (find correlations between findings across reports)
-
-### Tests
-- All 2,267 tests passing (0 failures)
-
-## [3.87.0] — 2026-03-14
-
-### Added
-- Code smell: finding-code-smell (detect code-smell indicators among findings)
-- Related rules: finding-related-rules (find related rules for a finding)
-- Token budget: review-token-budget (estimate and manage token budget usage)
-- Plugin list: review-plugin-list (list available and active plugins)
-- Owner assign: finding-owner-assign (assign finding owners based on rules)
-- Lock file: review-lock-file (analyze lock files for security issues)
-- Pattern library: finding-pattern-library (manage finding pattern library)
-- Status badge: review-status-badge (generate status badges for review results)
-- Rule explain: finding-rule-explain (explain rules in detail with examples)
-
-### Tests
-- All 2,267 tests passing (0 failures)
-
-## [3.86.0] — 2026-03-14
-
-### Added
-- Ignore pattern: review-ignore-pattern (manage review ignore patterns)
-- Quality gate: finding-quality-gate (enforce quality gates on findings)
-- Reachability: finding-reachability (analyze finding reachability)
-- Merge check: review-merge-check (pre-merge review validation)
-- Workspace scan: review-workspace-scan (scan workspace for reviewable files)
-- Context window: finding-context-window (show findings with code context)
-- Severity dist: finding-severity-dist (severity distribution analysis)
-- Report merge: review-report-merge (merge multiple verdict reports)
-- Plugin config: review-plugin-config (manage plugin configuration)
-
-## [3.85.0] — 2026-03-14
-
-### Added
-- Dependency risk: finding-dependency-risk (assess dependency risk levels)
-- PR template: review-pr-template (generate PR templates from findings)
-- Security hotspot: finding-security-hotspot (identify security-sensitive code)
-- Suppression log: finding-suppression-log (log and track suppressed findings)
-- Diff highlight: review-diff-highlight (highlight review differences)
-- CVE lookup: finding-cve-lookup (extract CVE references from findings)
-- Batch run: review-batch-run (run batch review on multiple files)
-- Output filter: review-output-filter (filter and transform review output)
-- Timeline view: finding-timeline-view (show findings on a timeline)
-
-## [3.84.0] — 2026-03-14
-
-### Added
-- Trend report: finding-trend-report (generate trend reports from historical findings)
-- Commit hook: review-commit-hook (install/manage git commit hooks for reviews)
-- Noise filter: finding-noise-filter (filter out noisy/low-value findings)
-- Fix priority: finding-fix-priority (prioritize findings for fixing by impact)
-- Quota check: review-quota-check (check review quotas and rate limits)
-- Cluster analysis: finding-cluster-analysis (cluster findings by similarity)
-- Session save: review-session-save (save and restore review sessions)
-- Evidence chain: finding-evidence-chain (build evidence chains across findings)
-- File complexity: review-file-complexity (analyze file complexity metrics)
-
-## [3.83.0] — 2026-03-14
-
-### Added
-- Finding link: review-finding-link (link related findings together)
-- Team assign: review-team-assign (assign findings to team members)
-- Compare runs: finding-compare-runs (compare findings across runs)
-- Skip list: review-skip-list (manage review skip list)
-- Hotfix suggest: finding-hotfix-suggest (suggest quick hotfixes)
-- Approval gate: review-approval-gate (configurable quality gates)
-- Changelog entry: review-changelog-entry (generate changelog from findings)
-- Branch compare: review-branch-compare (compare reviews between branches)
-- Category stats: finding-category-stats (category statistics)
-
-## [3.82.0] — 2026-03-14
-
-### Added
-- Scope lock: review-scope-lock (lock review scope to files/directories)
-- Duplicate rule: finding-duplicate-rule (detect duplicate/overlapping rules)
-- Watch mode: review-watch-mode (watch files and auto-trigger reviews)
-- Export PDF: review-export-pdf (export results as PDF-ready markdown)
-- Line blame: finding-line-blame (map findings to git blame)
-- Age tracker: finding-age-tracker (track finding ages over time)
-- Parallel files: review-parallel-files (batch files for parallel review)
-- Summary digest: finding-summary-digest (concise finding digests)
-- Code owner: review-code-owner (map findings to CODEOWNERS entries)
-
-## [3.81.0] — 2026-03-14
-
-### Added
-- Dependency graph: review-dependency-graph (visualize finding relationships)
-- Pattern match: finding-pattern-match (custom pattern matching for findings)
-- Diff stats: review-diff-stats (git diff statistics for reviews)
-- CWE map: finding-cwe-map (map findings to CWE identifiers)
-- Exclude vendor: review-exclude-vendor (exclude vendor/third-party code)
-- Risk matrix: finding-risk-matrix (generate risk matrices from findings)
-- File stats: review-file-stats (per-file review statistics)
-- False neg check: finding-false-neg-check (check for potential false negatives)
-- Rule filter: review-rule-filter (filter review results by rule criteria)
-
-## [3.80.0] — 2026-03-14
-
-### Added
-- Blame map: review-blame-map (map findings to git blame authors)
-- Autofix preview: finding-autofix-preview (preview patches before applying)
-- Config diff: review-config-diff (diff two review configurations)
-- Severity trend: finding-severity-trend (track severity trends over time)
-- Batch files: review-batch-files (batch-review multiple files)
-- Context expand: finding-context-expand (expand finding context with source)
-- Output format: review-output-format (configure and manage output formats)
-- Merge results: finding-merge-results (merge results from multiple runs)
-
-## [3.79.0] — 2026-03-14
-
-### Added
-- Group by: finding-group-by (group findings by category/severity/file)
-- Diff highlight: finding-diff-highlight (highlight diff regions related to findings)
-- Fix verify: finding-fix-verify (verify fixes resolve findings)
-- Custom judges: review-custom-judge (register and manage custom judges)
-- Prioritize: finding-prioritize (prioritize findings by business impact)
-- Annotations: review-annotation (add annotations to review results)
-- Multi-repo: review-multi-repo (review across multiple repositories)
-- Finding trace: finding-trace (trace findings to origin commits)
-- Preset save: review-preset-save (save and load review preset configurations)
-
-## [3.78.0] — 2026-03-14
-
-### Added
-- File filtering: review-file-filter (filter files for review inclusion/exclusion)
-- Dependency check: finding-dependency-check (check dependency-related findings)
-- Incremental review: review-incremental (review only changed files since last review)
-- Severity histogram: finding-severity-histogram (visualize severity distribution)
-- Plugin management: review-plugin-manage (manage review plugins and extensions)
-- Cross-file dedup: finding-dedup-cross-file (deduplicate findings across result files)
-- Progress tracking: review-progress-bar (track and display review progress)
-- Auto-labeling: finding-auto-label (auto-label findings based on content analysis)
-
-## [3.77.0] — 2026-03-14
-
-### Added
-- Auto-merge: review-auto-merge (auto-merge reviews passing all checks)
-- Finding correlation: finding-correlate (correlate related findings across files)
-- Dry run: review-dry-run (simulate reviews without persisting results)
-- Suppress patterns: finding-suppress-pattern (suppress findings by glob pattern)
-- Cache management: review-cache-clear (clear review caches selectively)
-- Impact scoring: finding-impact-score (score findings by estimated impact)
-- Compliance checks: review-compliance-check (OWASP/CWE compliance mapping)
-- Root cause analysis: finding-root-cause (identify root causes of recurring findings)
-
-## [3.76.0] — 2026-03-14
-
-### Added
-- Finding trends: finding-trend (show finding trends over time)
-- Code snippets: finding-snippet (extract code snippets from findings with context)
-- Environment check: review-env-check (verify review environment prerequisites)
-- Batch resolve: finding-batch-resolve (resolve multiple findings in bulk)
-- CI/CD integration test: review-integration-test (validate CI/CD integration)
-- Health check: review-health-check (diagnose review system health)
-- Age report: finding-age-report (report on finding ages and staleness)
-- Rule stats: review-rule-stats (per-rule statistics across reviews)
-- Parallel diff: review-parallel-diff (review multiple diff hunks)
-
-## [3.75.0] — 2026-03-14
-
-### Added
-- Review checklists: review-checklist (manage pre/post-review checklists)
-- Finding categories: finding-category (categorize findings into custom groups)
-- Review locking: review-lock (lock reviews to prevent re-runs)
-- Priority queue: finding-priority-queue (queue findings by priority for triage)
-- Diff annotation: review-diff-annotate (annotate diff hunks with findings)
-- Remediation plans: finding-remediation-plan (generate remediation plans from findings)
-- Config validation: review-config-validate (validate review configuration files)
-- Rate limiting: review-rate-limit (control review execution frequency)
-
-## [3.74.0] — 2026-03-14
-
-### Added
-- Confidence filtering: finding-confidence-filter (filter findings by confidence level)
-- Rule skipping: review-skip-rule (quick skip/disable specific rules)
-- Review notes: review-note (attach notes to reviews)
-- CSV export: finding-export-csv (export findings as CSV)
-- Timeline: review-timeline (show review activity timeline)
-- Snapshot diff: review-snapshot-diff (diff between review snapshots)
-- Resolution tracking: finding-resolution (track finding resolution status)
-- Review ownership: review-owner (assign review ownership to team members)
-
-## [3.73.0] — 2026-03-14
-
-### Added
-- False positive management: finding-false-positive (track and manage false positive findings)
-- Review sessions: review-session (group reviews into named sessions)
-- Bulk actions: review-bulk-action (dismiss, suppress, approve findings in bulk)
-- Review retry: review-retry (retry failed or incomplete reviews)
-- Review depth: review-depth (control review depth — shallow, normal, deep)
-- Finding links: finding-link (link related findings across files)
-- Version comparison: review-compare-version (compare results between code versions)
-- Email summaries: review-summary-email (generate email-ready review summaries)
-
-## [3.72.0] — 2026-03-14
-
-### Added
-- Approval workflows: review-approval (request, approve, reject review results)
-- Severity customization: finding-severity-override (per-project severity overrides)
-- Config sharing: review-config-export (export and import review configurations)
-- PR integration: review-pr-comment (generate PR comment summaries from reviews)
-- Path management: review-ignore-path (manage path ignore lists for reviews)
-- Deduplication: finding-deduplicate (detect and deduplicate similar findings)
-- Score tracking: review-score-history (track review scores over time)
-- Feedback: review-feedback (collect user feedback on review quality)
-
-## [3.71.0] — 2026-03-14
-
-### Added
-- Auto-fix: finding-auto-fix (auto-generate fix suggestions for common patterns)
-- History: review-history-search (search through past review history)
-- Language insights: review-language-stats (language-specific statistics)
-- Coverage: review-coverage-map (map which files have been reviewed)
-- Config management: review-rollback (roll back review config to a previous state)
-- Onboarding: review-onboard (guided onboarding for new team members)
-- Batch review: review-parallel (discover and queue multiple files for review)
-- Context enrichment: finding-context (enrich findings with surrounding code)
-
-## [3.70.0] — 2026-03-14
-
-### Added
-- Organization: review-tag (tag reviews for filtering), review-archive (archive and retrieve old results)
-- Impact analysis: finding-impact (estimate business impact of findings)
-- Allow-listing: review-whitelist (allow-list safe patterns that shouldn't be flagged)
-- Customization: review-custom-prompt (customize review prompts for project needs)
-- Context: review-diff-context (show diff hunks with surrounding file context)
-- CI integration: review-ci-status (check CI pipeline review readiness)
-- Team metrics: review-team-summary (aggregate team review metrics)
-
-## [3.69.0] — 2026-03-14
-
-### Added
-- Daily workflow: review-standup (daily standup-ready summaries), review-changelog-gen (auto-generate changelog from findings)
-- Fix tracking: finding-fix-rate (track resolution speed over time), finding-recurrence (detect findings that keep reappearing)
-- Progress: review-milestone (track and celebrate review milestones), review-benchmark-self (benchmark against your own history)
-- Risk & reporting: review-risk-score (weighted aggregate project risk), review-report-pdf (generate printable markdown review reports)
-
-## [3.68.0] — 2026-03-14
-
-### Added
-- Engagement: review-streak (track consecutive clean review streaks with achievements), review-badge (generate status badges for project READMEs)
-- Pattern analysis: finding-cluster (cluster related findings to reveal systemic AI patterns), finding-hotspot (identify areas with highest finding density)
-- Compliance: review-audit-log (comprehensive local audit log for all review actions)
-- Experimentation: review-sandbox (test review configs safely without affecting real setup), review-ab-test (A/B test review configurations)
-- Onboarding: review-integration (verify CI/CD, IDE, and hook integrations are connected)
-
-## [3.67.0] — 2026-03-14
-
-### Added
-- Tracking: finding-age (track how long findings remain unresolved), finding-rank (rank findings by business impact and fix effort)
-- Insights: review-dashboard (terminal-based review health dashboard with ASCII charts), review-diff-summary (concise PR-ready change summaries)
-- Governance: config-lint (lint and validate .judgesrc configuration), review-quota (local review usage quota tracking)
-- Resilience: review-offline (offline mode support for air-gapped environments), review-notify (configurable local notification rules)
-
-## [3.66.0] — 2026-03-14
-
-### Added
-- Verification: fix-verify (confirm fixes resolved findings), review-comment (generate inline code comments from findings)
-- Tracking: finding-timeline (track finding trends across commits), review-schedule (configure scheduled review cadences)
-- Discovery: rule-catalog (browse and search available rules), review-scope (define review scope boundaries)
-- Export: review-export (unified export to CSV, markdown, HTML), setup-wizard (guided setup for new users/teams)
-
-## [3.65.0] — 2026-03-14
-
-### Added
-- Integrations: review-webhook (webhook notifications for CI/CD), review-annotate (GitHub-compatible PR annotations), review-merge (merge multiple review results)
-- Governance: finding-suppress (suppress findings with expiration), judge-config (per-judge sensitivity overrides), review-checkpoint (save/restore review state)
-- Analysis: review-filter (advanced multi-criteria finding filter), code-health (overall codebase health score with letter grades)
-
-## [3.64.0] — 2026-03-14
-
-### Added
-- Personalization: review-profile (per-developer preferences), review-template (reusable workflow templates), review-stats (personal statistics and improvement trends)
-- Automation: auto-approve (auto-approve below threshold), fix-suggest (concrete fix suggestions with OWASP references)
-- Intelligence: diff-explain (explain why changes were flagged), review-priority (smart prioritization by context/impact), multi-lang-review (cross-language consistency checking)
-
-## [3.63.0] — 2026-03-14
-
-### Added
-- Workflow efficiency: review-cache (cache results for unchanged files), ignore-list (configurable file/rule ignore patterns), incremental-review (only review changed files since last run)
-- Team governance: team-config (shared team-level configuration), review-log (structured audit log of review actions)
-- Developer productivity: finding-group (group related findings into clusters), review-summary (PR-ready summary with metrics), rule-test (test custom rules against sample code)
-
-## [3.62.0] — 2026-03-14
-
-### Added
-- CI/CD integration: review-gate (quality gate with thresholds), diff-review (review only changed lines), batch-review (parallel multi-file review)
-- Customization: custom-rule (user-defined rules), severity-tune (auto-calibrate severity levels)
-- Insights: review-compare (compare review runs), review-explain (plain-language explanations), focus-area (risk-based file prioritization)
-
-## [3.61.0] — 2026-03-14
-
-### Added
-- Trust & transparency: quick-check (sub-100ms pattern review), merge-verdict (single MERGE/HOLD decision), review-handoff (structured human escalation)
-- Evidence & provenance: evidence-chain (traversable reasoning chains), ai-provenance (AI-generated code detection), review-receipt (cryptographic attestation)
-- CI/CD depth: review-contract (versionable review policy), blame-review (git-blame finding attribution)
-
-## [3.60.0] — 2026-03-14
-
-### Added
-- **hallucination-detect** — Find fabricated API calls, non-existent methods, invented config options, and undeclared env vars
-- **context-blind** — Flag when AI reinvents utilities already present in the codebase (duplicate functions, redundant validators)
-- **over-abstraction** — Detect unnecessary abstractions: single-impl abstract classes, barely-used generics, delegation-only wrappers
-- **stale-pattern** — Identify outdated idioms when modern alternatives exist: callback→async, var→const, deprecated APIs, legacy React
-- **security-theater** — Detect security-looking code with no protection: weak hashing, unverified CSRF, wildcard CORS, hardcoded keys
-- **review-digest** — Generate concise role-appropriate review summaries with risk scores, hot files, and action items
-- **adoption-track** — Measure team-level Judges adoption metrics: config completeness, suppression rates, cold spots
-- **finding-budget** — Manage finding volume per PR to prevent alert fatigue with risk-based prioritization and graduated disclosure
-
-## [3.59.0] — 2025-07-25
-
-### Added
-- **logic-lint** — Detect common logic errors AI generates: tautological comparisons, off-by-one loops, constant conditions, invalid typeof
-- **phantom-import** — Find hallucinated imports, non-existent modules, and wrong export names AI invents
-- **example-leak** — Detect AI-copied placeholder URLs, example data, tutorial names, and stub code left in production
-- **completion-audit** — Verify AI code completeness: unmatched brackets, truncation markers, TODO stubs, ellipsis placeholders
-- **spec-conform** — Auto-detect project conventions (semicolons, quotes, indent, naming) and flag AI-generated deviations
-- **cross-file-consistency** — Verify naming, error handling, import styles, and return types are consistent across files
-- **api-misuse** — Detect incorrect API usage: async forEach, unprotected JSON.parse, fetch without status check, Promise anti-patterns
-- **review-focus** — Prioritize human review attention by file risk score (security, payment, DB, complexity, nesting)
-
-## [3.58.0] — 2025-07-25
-
-### Added
-- **dead-code-detect** — Find unreachable code, unused exports, orphaned functions, and dead branches via cross-file analysis
-- **async-safety** — Detect async anti-patterns: fire-and-forget promises, .then() without .catch(), await in loops, async in timers
-- **input-guard** — Verify input validation on route handlers, SQL/command injection, file upload limits, ReDoS, open redirects
-- **clone-detect** — Find duplicated code blocks and functions using normalized comparison across files
-- **contract-verify** — Check API spec vs implementation alignment: unimplemented routes, undocumented statuses, mixed versions
-- **encoding-safety** — Detect encoding/serialization hazards: eval(), unsafe deserialization, innerHTML, RegExp injection
-- **assertion-density** — Audit defensive checks: missing preconditions, division without zero-check, switch without default, unchecked Map.get
-- **state-integrity** — Validate state machine correctness: incomplete enum handling, impossible boolean combos, missing error states
-
-## [3.57.0] — 2025-07-25
-
-### Added
-- **comment-drift** — Detect stale, misleading, or contradictory inline comments (TODO without tickets, renamed variable refs, commented-out code, tautological comments, outdated @param names)
-- **timeout-audit** — Trace timeout and deadline propagation gaps (missing HTTP timeouts, hardcoded values, DB queries, Promise.all guards, downstream > upstream mismatches)
-- **cache-audit** — Audit cache invalidation correctness, TTL consistency, and stampede risk (missing TTL, unbounded caches, write-through gaps, suspicious TTL values)
-- **idempotency-audit** — Verify retried/webhook operations are safely idempotent (INSERT without conflict handling, counter mutation in retries, notification dedup, payment keys)
-- **type-boundary** — Check type safety at serialization boundaries (JSON.parse without validation, unchecked `as` casts, ts-ignore at boundaries, `any` at API boundaries)
-- **event-leak** — Detect orphaned event listeners, unsubscribed observables, dangling async handles (addEventListener without cleanup, setInterval without clear, useEffect leaks)
-- **privilege-path** — Model authorization flows to find privilege-escalation paths (routes without auth, IDOR patterns, JWT decode without verify, CORS misconfig)
-- **error-ux** — Audit user-facing error messages for actionability and safety (generic messages, stack trace leaks, internal path exposure, missing remediation hints)
-
-## [3.56.0] — 2025-07-25
-
-### Added
-- **api-versioning-audit** — Detect breaking changes and versioning policy violations across API surfaces
-- **ownership-map** — Generate and validate CODEOWNERS coverage, stale owners, and orphaned paths
-- **retry-pattern-audit** — Audit retry, backoff, and circuit-breaker patterns for correctness
-- **error-taxonomy** — Classify and standardize error codes, messages, and hierarchies
-- **boundary-enforce** — Validate architectural module boundaries and import rules
-- **log-quality** — Assess logging hygiene: structured format consistency, PII leaks, level correctness
-- **null-safety-audit** — Identify null/undefined dereference risks, missing guards, and inconsistent nullability
-- **test-isolation** — Detect shared mutable state, ordering dependencies, and resource leaks between tests
-
-## [3.55.0] — 2025-07-25
-
-### Added
-- **commit-hygiene** — Audit commit messages and diff structure for AI-generated code submission quality
-- **deploy-readiness** — Pre-deployment production readiness checklist (health checks, graceful shutdown, env validation, rate limiting, CORS, probes)
-- **rollback-safety** — Detect changes unsafe or impossible to roll back (destructive migrations, API removals, encryption changes)
-- **test-quality** — Score test suites for assertion density, boundary coverage, flakiness patterns, and mutation-testing readiness
-- **build-optimize** — Detect build-time inefficiencies (unused imports, barrel re-exports, dynamic require, circular dependencies)
-- **secret-age** — Credential lifecycle and rotation analysis (hardcoded secrets, missing vault refs, disabled rotation)
-- **observability-gap** — Detect missing instrumentation at critical code paths (silent catches, untraced calls, no heartbeats)
-- **migration-safety** — Validate framework/language migration PRs for compatibility gaps and data-loss risks
-
-## [3.54.0] — 2025-07-25
-
-### Added
-- **prompt-replay** — Reverse-engineer AI prompts that generated flagged code and suggest improved prompts
-- **review-replay** — Record, export, and replay full evaluation runs as step-by-step walkthroughs
-- **context-inject** — Feed project-specific context (architecture docs, coding standards) into evaluation
-- **habit-tracker** — Track recurring finding patterns per developer/AI-model with improvement suggestions
-- **finding-contest** — Gamified challenge mode for competitive fix sprints with leaderboards
-- **approve-chain** — Multi-stage approval workflows based on finding severity and code sensitivity
-- **snippet-eval** — Evaluate code snippets from clipboard/stdin without project setup (zero-friction entry)
-- **coach-mode** — Interactive teaching mode with real-world breach examples and secure alternatives
-
-## [3.53.0] — 2025-07-25
-
-### Added
-- **doc-drift** — Detect documentation-to-code drift (@param mismatches, stale @returns, dead doc blocks)
-- **cross-pr-regression** — Track flagged pattern recurrence across PRs (SQL injection, eval, innerHTML, etc.)
-- **code-similarity** — Compare code across files for duplication using line-level and N-gram structural similarity
-- **team-trust** — Aggregate team-wide false-positive/true-positive feedback to build collective trust profiles
-- **exception-consistency** — Detect inconsistent exception handling (empty catch, throw string, mixed strategies)
-- **resource-cleanup** — Validate resource cleanup patterns (file handles, DB connections, timers, streams)
-- **refactor-safety** — Analyze refactoring safety (orphaned imports, deprecated-still-used, dead files)
-- **compliance-weight** — Re-weight finding severity by active compliance frameworks (PCI-DSS, HIPAA, GDPR, SOC2, ISO27001)
-
-## [3.52.0] — 2025-07-25
-
-### Added
-- **`judges watch-judge`** — Continuously monitor files and auto-evaluate on change (live feedback with configurable polling interval and score threshold; single-pass `--once` mode for CI)
-- **`judges impact-scan`** — Cross-file ripple effect detection (broken imports, unused exports, naming conflicts, dependency chain analysis, fragile API signatures)
-- **`judges model-report`** — AI model scorecard and comparison (track evaluations per model, pass rates, failure categories, trend detection; side-by-side model comparison)
-- **`judges trust-adaptive`** — Adaptive trust scoring for developers and AI models (high-trust actors skip non-critical judges, low-trust get strict evaluation with human escalation)
-- **`judges judge-learn`** — Generate custom judges from feedback (record false positives/negatives, extract patterns, auto-generate detection rules with confidence calibration)
-- **`judges chat-notify`** — Publish findings to Slack, Teams, Discord, or custom webhooks (rich formatting with attachments/embeds, critical mention routing, webhook config stored locally)
-- **`judges design-audit`** — Detect code breaking project conventions (convention adherence, abstraction level, orphaned imports, async pattern consistency, error handling, naming coherence)
-- **`judges remediation-lib`** — Proven fix templates ranked by effectiveness (built-in templates for empty catch, SQL injection, XSS, hardcoded secrets; team voting, auto-apply with rollback)
-
-## [3.51.0] — 2025-07-25
-
-### Added
-- **`judges ai-output-compare`** — Compare outputs from multiple AI models (divergence detection across complexity, patterns, structure, dependencies; structural similarity score 0-100)
-- **`judges hallucination-score`** — Hallucination risk score (0-100) with 10 weighted signal detectors: suspicious imports, generic naming, TODOs, dead code, tautologies, copy-paste artifacts, magic numbers, empty catch, commented code, empty functions
-- **`judges ai-gate`** — Pre-commit/pre-PR guard blocking AI-generated code below confidence threshold (8 AI detection signals; --block flag for CI exit code 1; report generation to `.judges-ai-gate/`)
-- **`judges ai-pattern-trend`** — Track AI-generated code pattern evolution over time (snapshot capture to `.judges-ai-trend/history.json`; trend arrows for metric changes across snapshots)
-- **`judges test-suggest`** — Test scenario suggestions for AI-generated code (function extraction; 10 suggestion categories: null input, empty input, error path, async error, boundary, type coercion, regex edge case, file IO, state mutation, return consistency)
-- **`judges vendor-lock-detect`** — Vendor-specific API/SDK detection (AWS, Azure, GCP, Vercel, Cloudflare, Firebase, Stripe, Twilio, Docker, MongoDB, PostgreSQL; portability scoring 0-100)
-- **`judges clarity-score`** — Code readability and self-documentation score (naming quality, comment coverage, function length, line length, nesting depth, magic values, style consistency; A-F grading)
-- **`judges arch-audit`** — Architecture quality audit (coupling, separation of concerns, dependency injection, testability, single responsibility, scalability patterns; A-F grading with issue severity)
-
-## [3.50.0] — 2025-07-25
-
-### Added
-- **`judges secret-scan`** — Scan for hardcoded secrets and API keys (AWS, GitHub, Stripe, Slack, JWT, connection strings; 16 patterns with entropy-based detection)
-- **`judges iac-lint`** — Lint Dockerfiles, Kubernetes manifests, and Helm charts for security misconfigurations (privileged mode, host network, root user, missing resource limits)
-- **`judges pii-scan`** — Detect PII patterns in source code (SSN, credit card with Luhn validation, email, phone, passport, drivers license, PII in logging statements)
-- **`judges api-audit`** — API endpoint security audit (Express, Fastify, Flask, Spring, Django; rate limiting, CORS, authentication, input validation, SQL injection detection)
-- **`judges compliance-map`** — Map findings to compliance frameworks (HIPAA, SOC 2, PCI-DSS v4.0, ISO 27001:2022, NIST 800-53 Rev 5) with cross-walk matrix and gap analysis
-- **`judges perf-compare`** — Before/after performance comparison (loop nesting, allocations, async anti-patterns, Big-O estimation, recursive calls, regex operations)
-- **`judges guided-tour`** — Interactive onboarding tutorials (quick start, CI/CD integration, team adoption tracks with step-by-step guidance and starter .judgesrc generation)
-- **`judges exec-report`** — Executive security dashboard (HTML report with risk posture score, severity distribution, top recurring issues, actionable recommendations)
-
-## [3.49.0] — 2026-03-12
-
-### Added
-- `judges sbom-export` — Generate CycloneDX Software Bill of Materials from project manifests
-- `judges license-scan` — Dependency license compliance scanning with copyleft/unknown detection
-- `judges test-correlate` — Cross-reference test coverage (lcov/istanbul/cobertura) with security findings
-- `judges predict` — Forecast remediation timelines and regression-prone files via linear regression
-- `judges org-policy` — Organization-wide policy management with per-repo compliance checking
-- `judges incident-response` — Incident response playbook generation and tracking
-- `judges risk-heatmap` — File/directory risk visualization with HTML report output
-- `judges learning-path` — Personalized developer security learning with skill progression tracking
-
-## [3.48.0] — 2026-03-12
-
-### Added
-- `judges auto-fix` — Automated fix suggestions with 10 fix templates for common vulnerability patterns
-- `judges audit-trail` — Chain-of-custody tracking for findings (created, reviewed, suppressed, resolved, reopened, escalated, voted)
-- `judges pattern-registry` — Team security pattern knowledge repository with built-in and custom patterns
-- `judges security-maturity` — Security posture maturity assessment across 5 dimensions (scanning, finding mgmt, compliance, collaboration, AI readiness)
-- `judges perf-hotspot` — Performance anti-pattern detection (N+1 queries, unbounded collections, sync I/O, string concat loops)
-- `judges doc-gen` — Generate security documentation (policy, remediation guide, team playbook)
-- `judges dep-correlate` — Dependency vulnerability correlation and upgrade priority recommendations
-- `judges judge-author` — Custom judge authoring toolkit (scaffold, validate, test)
-
-## [3.47.0] — 2026-03-12
-
-### Added
-- **`judges ai-model-trust`** — AI model confidence scoring with LLM source fingerprinting and per-model trust profiles
-- **`judges team-rules-sync`** — Fast team onboarding by applying shared rule templates (security-team, frontend-team, backend-team, etc.)
-- **`judges cost-forecast`** — Security debt cost projections with 30/60/90-day trend forecasting and industry cost-per-finding benchmarks
-- **`judges team-leaderboard`** — Gamified security review engagement tracking with badges, streaks, and team rankings
-- **`judges code-owner-suggest`** — Auto-recommend CODEOWNERS entries based on developer finding resolution history
-- **`judges pr-quality-gate`** — Automated PR pass/fail quality gate with configurable thresholds and decision history
-- **`judges ai-prompt-audit`** — Scan AI-generated code for prompt injection risks (SQL injection, shell injection, SSRF, etc.)
-- **`judges adoption-report`** — Team adoption metrics dashboard with executive summary, trends, and cost savings tracking
-
-## [3.46.0] — 2026-03-12
-
-### Added
-- **`judges audit-bundle`** — Assembles auditor-ready evidence packages with SOC2/ISO27001 control mapping from local data files
-- **`judges dev-score`** — Developer security growth score tracking with leaderboard and streak tracking
-- **`judges model-risk`** — AI model vulnerability risk profiling for gpt-4o, gpt-4, claude, copilot, cursor with recommended judges
-- **`judges retro`** — Security incident retrospective analysis checking if Judges would have caught a vulnerability at a git commit
-- **`judges config-drift`** — Detects config divergence from org baseline with drift scoring and directory scanning
-- **`judges reg-watch`** — Regulatory standard coverage monitor for OWASP Top 10, CWE Top 25, NIST SSDF
-- **`judges learn`** — Personalized developer learning paths with module catalog, exercises, and progress tracking
-- **`judges generate`** — Secure code template generator with pre-hardened templates for Express, React, Flask, Go, and Node.js
-
-## [3.45.0] — 2026-03-12
-
-### Added — Intelligence, Collaboration & Analysis (8 features)
-- **Consensus voting** (`judges vote`) — Multi-developer voting on findings with agree/disagree/unsure verdicts; automatic consensus scoring; dispute detection; local `.judges-votes.json` storage
-- **Advanced finding query** (`judges query`) — Complex finding search with filter keys (severity, rule, confidence, has-patch); negation support; saved queries; aggregate grouping
-- **Judge reputation tracking** (`judges judge-reputation`) — Per-judge accuracy and FP rate tracking over time; confidence calibration scoring; trend analysis (improving/stable/declining); flagged judges alert
-- **Finding correlation** (`judges correlate`) — Link related findings and identify root causes; auto-correlate by rule ID and line overlap; manual root-cause records with severity
-- **Periodic digest** (`judges digest`) — Record point-in-time snapshots and generate daily/weekly/monthly digest reports with trend charts and severity distribution
-- **Rule sharing** (`judges rule-share`) — Export/import custom rule configurations as shareable packages; merge rule overrides, disabled rules, and disabled judges into `.judgesrc`
-- **Finding explanation** (`judges explain-finding`) — Rich context for individual findings with category info, common causes, remediation steps, and external references (OWASP, CWE, NIST)
-- **Run comparison** (`judges compare-runs`) — Save evaluation snapshots and compare side by side; shows added/removed findings, severity deltas, and per-rule changes
-
-## [3.44.0] — 2026-03-12
-
-### Added — Trust, Noise Reduction & Team Adoption (8 features)
-- **Batch FP suppression** (`judges suppress`) — Suppress findings by file glob, rule prefix, severity, or exact rule IDs with full audit trail; supports auto-expiry; `--list` and `--stats`
-- **Rule ownership** (`judges rule-owner`) — Map rules/categories to team owners with contact info and expertise levels; `--find` resolves ownership for any rule ID via prefix matching
-- **Noise advisor** (`judges noise-advisor`) — Analyze rule FP rates by cross-referencing suppressions, false-negative feedback, and confidence scores; recommends disable/raise-threshold/lower-severity actions
-- **Human review queue** (`judges review-queue`) — Surface low-confidence findings needing human judgment; route to experts via rule-owner integration; record verdicts (approve/dismiss/escalate)
-- **Report templates** (`judges report-template`) — 6 predefined templates (exec-summary, dev-detail, compliance, pr-review, trend, onboarding) targeting different audiences; `--output` to write files
-- **Finding burndown** (`judges burndown`) — Track resolution progress over time with visual chart; `--set-target` and `--trajectory` for ETA analysis; local `.judges-burndown.json` storage
-- **Team knowledge base** (`judges kb`) — Store team decisions about rules (not-applicable, accepted-risk, deferred, exception, custom-guidance); searchable with expiry; approved-by audit trail
-- **Judge recommendations** (`judges recommend`) — Analyze project stack (16 framework detectors) and recommend relevant judges; shows coverage estimates and reasons
-
-## [3.43.0] — 2026-03-12
-
-### Added — Workflow Integration & Compliance (9 features)
-- **CI template generator** (`judges ci-template`) — Generate CI pipeline templates for GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines, and CircleCI; auto-detect platform from repo structure; `--write` to create file directly
-- **Policy audit trail** (`judges policy-audit`) — SOC2/ISO27001 compliance audit trail with SHA-256 policy snapshots; records enabled/disabled judges, rules, overrides, and git commit; `--diff` compares policy changes; `--export` for external systems
-- **Remediation guides** (`judges remediation`) — 10 step-by-step fix guides for common finding categories (SQL injection, XSS, command injection, auth, crypto, SSRF, performance, error handling, concurrency, IaC); before/after code examples; OWASP/CWE references
-- **Git hook installation** (`judges hook-install`) — Install pre-commit/pre-push hooks with direct `.git/hooks` or Husky support; `JUDGES_SKIP_HOOK` env var to bypass; timeout protection; `--uninstall` support
-- **False-negative tracking** (`judges false-negatives`) — Local feedback database for tracking missed findings; `--add` with file/line/category/severity/description; `--resolve`; stats by category, severity, and language
-- **Finding assignment** (`judges assign`) — Assign findings to team members with local database; severity filtering; `--resolve` workflow; `--stats` for workload analysis
-- **Ticket sync** (`judges ticket-sync`) — Create tickets from findings in Jira, Linear, or GitHub Issues; severity filtering; `--dry-run` preview; supports `JUDGES_TICKET_TOKEN` env var
-- **SLA tracking** (`judges sla-track`) — Define response-time SLAs per severity and track violations; `--check` for violation detection; `--set-policy` to customize thresholds; local `.judges-sla.json` storage
-- **Regression alerting** (`judges regression-alert`) — Baseline snapshot comparison to detect quality regressions; `--save` to capture baseline; `--check` to compare; `--fail-on-regression` for CI gating; severity and rule-level delta reporting
-
-## [3.42.0] — 2026-03-12
-
-### Added — CI Integration & Review UX (10 features)
-- **SARIF upload to GitHub Code Scanning** (`judges upload`) — Upload SARIF results directly to GitHub's Code Scanning API; auto-detects git ref, SHA, and repo; supports `GITHUB_TOKEN` env var; gzip+base64 encoding
-- **Smart judge selection** (`judges smart-select`) — Auto-select relevant judges based on file language and content signals; reduces noise by skipping irrelevant judges (e.g., IaC judge on `.tsx` files); exports `getRelevantJudges()` for programmatic use
-- **PR summary comment** (`judges pr-summary`) — Post a top-level PR comment with verdict, score, per-judge breakdown, and top findings; updates in-place on subsequent runs via comment marker; supports `--sarif` and `--json` input
-- **Performance profiling** (`judges profile`) — Track evaluation time per judge with `JUDGES_PROFILE=1`; view timing reports with slow-judge warnings; bar chart visualization in terminal
-- **Finding grouping** (`judges group`) — Group findings by category, severity, file, rule, or judge for digest-style review; automatic category classification from rule ID prefixes
-- **Diff-only evaluation** (`judges diff-only`) — Filter findings to only changed lines in a PR; parses unified diff output; supports `--base <ref>` and `--diff-file`; dramatically reduces CI review noise
-- **Confidence auto-triage** (`judges auto-triage`) — Auto-suppress findings below configurable confidence threshold; per-severity threshold overrides; always-keep and always-suppress rule lists; audit trail preserved
-- **Config validation** (`judges validate-config`) — Validate `.judgesrc` against known fields with Levenshtein-based typo suggestions; checks severity, format, concurrency, quality gate, and notification config; `--strict` mode
-- **Rule coverage map** (`judges coverage-map`) — Visual matrix of which rules apply to which languages; stats by language and judge; `--languages` filter; coverage gap identification
-- **Eval cache warming** (`judges warm-cache`) — Pre-populate disk cache with file hashes for faster CI runs; supports `--max`, `--root`, `--extensions`; skips already-warm files
-
-### Tests
-- 2,267 tests passing (1,082 main + 1,185 additional suites), 0 failures
-
-## [3.41.0] — 2026-03-12
-
-### Added — Adoption Gap Closure (12 features)
-- **Webhook notification system** (`judges notify`) — Send evaluation results to Slack, Teams, or generic webhook endpoints; configurable via `.judgesrc` `notifications.channels[]`; HTTPS-only enforcement
-- **Auto-fix PR creation** (`judges fix-pr`) — Evaluate files, apply auto-fix patches on a new git branch, push, and create a GitHub PR via `gh` CLI or REST API; supports `--dry-run`, `--branch`, `--severity`, `--repo`
-- **Configurable quality gates** (`judges quality-gate`) — Composite quality gate definitions with `maxFindings`, `minScore`, `requiredJudges`, `blockerRules`, `maxFpRate`, `minFixRate`, `minConfidence`; configurable via `.judgesrc` `qualityGates`
-- **Parallel file processing** (`src/parallel.ts`) — Async promise pool for concurrent multi-file evaluation; `evaluateParallel()`, `evaluateSequential()`, `batchEvaluate()` with configurable concurrency; auto-detects CPU count
-- **Interactive fix mode** (`judges fix --interactive`) — Per-finding accept/skip/all/quit flow with colored inline diff display and severity-colored headers
-- **Framework-aware detection** (`src/evaluators/framework-rules.ts`) — 10 framework profiles (React, Next.js, Express, Fastify, Django, Flask, FastAPI, Spring, Rails, Angular) with auto-detection, framework-specific rules (FW-REACT-001..003, FW-EXPRESS-001..002, FW-DJANGO-001..002, FW-FLASK-001, FW-SPRING-001, FW-RAILS-001, FW-NEXT-001), and severity adjustments to reduce false positives
-- **Auto-calibration from feedback** (`judges auto-calibrate`) — CLI wrapper for auto-tune engine; analyzes accumulated feedback to recommend threshold adjustments and rule overrides; `--apply` writes to `.judgesrc`
-- **Dependency vulnerability correlation** (`judges dep-audit`) — Runs `npm audit` / `pip-audit` and correlates dependency CVEs with code findings via CWE mapping; supports `--correlate` with existing results
-- **Monorepo workspace support** (`judges monorepo`) — Discovers packages via pnpm-workspace.yaml, lerna.json, turbo.json, npm workspaces, nx.json, or heuristic; per-package cascading config resolution
-- **Config migration assistant** (`judges config-migrate`) — Detects deprecated fields, renamed keys, and structural changes with 10 migration rules; `--apply` flag writes migrated config; `--dry-run` shows changes
-- **Rule deprecation lifecycle** (`judges deprecated`) — Registry of deprecated rules with version info, migration guidance, and replacement rules; `--check` validates `.judgesrc` for stale references
-- **Cross-run finding dedup report** (`judges dedup-report`) — Surfaces new vs recurring vs fixed findings from `.judges-findings.json` with stats, severity breakdown, and filtering (`--new`, `--recurring`, `--fixed`)
-
-### Fixed
-- ESLint: removed all unused import warnings across 7 files (cli.ts, fix-pr.ts, quality-gate.ts, parallel.ts, auto-calibrate.ts, monorepo.ts, dedup-report.ts)
-
-### Tests
-- 2,267 tests passing (1,082 main + 1,185 additional suites), 0 failures
-
-## [3.40.0] — 2026-03-11
-
-### Added — Adoption & Enterprise Features
-- **DataAdapter persistence layer** — All stores (feedback, finding-lifecycle, fix-history, calibration, snapshot) now flow through the pluggable `DataAdapter` interface; users can wire custom backends (REST, DB, cloud) via `.judgesrc` without judges ever hosting their data
-- **Auto-fix verification loop** (`judges fix --verify`) — Re-evaluates code after applying patches; tracks fix success/regression rates per judge
-- **Override/exception workflow** (`judges override`) — Accept-risk, false-positive, and time-limited suppression with audit logging; `override list` and `override audit` subcommands
-- **Evidence-backed explanations** — Every finding now includes an `evidence` array in both text and SARIF output, citing specific AST/pattern matches and confidence scores
-- **Cross-file import context** — `project` evaluator resolves ES/TS/Python/Go imports to detect cross-module issues (unused exports, circular deps, re-export of internals)
-- **Auto-activate model profiles** — Evaluator index detects LLM watermarks (Codex, Copilot, Claude, GPT, Gemini, Cursor) and applies tuned thresholds automatically
-- **Feedback-to-rule pipeline** (`judges feedback-rules`) — Aggregates user feedback to generate candidate custom rules; `--apply` flag writes to `.judgesrc`
-- **IDE fix diff preview** — VS Code extension shows inline diff previews before applying auto-fixes with accept/reject actions
-- **Enhanced `--explain` output** — Layer 2 evidence details with AST node types, pattern matcher names, and confidence breakdowns
-- **Trend regression alerts** — `judges snapshot --check` compares latest snapshot to baseline and exits non-zero on regression; configurable thresholds
-- **Multi-repo governance dashboard** (`judges governance`) — Aggregates findings across repos with risk scoring, trend tracking, and HTML/JSON output
-- **Language pattern parity audit** (`judges parity`) — Compares rule coverage across languages and reports gaps
-- **Semantic intent-drift detection** — Four new evaluator rules (INTENT-007 through INTENT-010): scope creep, naming drift, contract violation, dead intent
-- **Compliance evidence reports** (`judges compliance-report`) — Generates audit-ready evidence packages for SOC 2, ISO 27001, OWASP, PCI DSS frameworks
-- **Staged-only pre-commit** (`--staged-only`) — Single-pass mode for `judges hook` that scans only `git diff --cached` files
-- **Plugin discovery** (`judges plugin-search`) — Enhanced with `list`, `info`, and `init` subcommands for community plugin ecosystem
-
-### Fixed
-- ESLint: removed forbidden `import()` type annotation in CLI compliance-report handler
-- ESLint: removed unused imports (`FeedbackEntry` in data-adapter, `Severity` in org-metrics)
-- ESLint: prefixed unused dashboard variables to satisfy no-unused-vars rule
-
-### Tests
-- 2,267 tests passing (1,082 main + 1,185 additional suites), 0 failures
-
-## [3.39.0] — 2026-03-10
-
-### Added — LLM Prompt Benchmark (Layer 2)
-- **`src/commands/llm-benchmark.ts`** — New module with types, rule-ID parser, prompt construction, stratified sampling, scoring, and markdown formatting for LLM-based benchmark results
-- **`scripts/run-llm-benchmark.ts`** — Standalone LLM benchmark runner supporting OpenAI and Anthropic APIs; configurable via env vars (`LLM_API_KEY`, `LLM_MODEL`, `LLM_PROVIDER`); supports `--sample`, `--mode tribunal|per-judge`, `--dry-run`; saves snapshot JSON to `benchmarks/`
-- **`npm run benchmark:llm`** — New npm script to run LLM benchmarks
-- **`benchmarks/` directory** — Storage for LLM benchmark snapshot results (latest + timestamped archives)
-
-### Improved — Benchmark Report Methodology
-- **"How to Read This Report"** — New methodology preamble explaining the dual-layer architecture (L1 deterministic + L2 LLM prompts), all metrics (Detection Rate, Precision, Recall, F1, FP Rate), and matching types (TP, FP, FN)
-- **Layer headers** — Report now clearly labels "Layer 1 — Deterministic Analysis" and "Layer 2 — LLM Prompt Analysis" sections
-- **Layer comparison table** — Side-by-side L1 vs L2 metrics when LLM snapshot data is available
-- **Auto-load LLM snapshot** — `judges benchmark report` automatically incorporates `benchmarks/llm-snapshot-latest.json` into the published report
-- **Regenerated `docs/benchmark-report.md`** — Updated to v3.39.0 with methodology section; 1,048 cases, Grade A, F1 94.0%, 0 FP
-
-### Added — Tests
-- 15 new unit tests for all LLM benchmark components: `parseLlmRuleIds`, `constructPerJudgePrompt`, `constructTribunalPrompt`, `selectStratifiedSample`, `scoreLlmCase`, `computeLlmMetrics`, `formatLlmSnapshotMarkdown`, `formatLayerComparisonMarkdown`
-
-## [3.38.0] — 2026-03-10
-
-### Fixed — Benchmark Quality (0 failures, all FP rates <30%)
-- **HALLU evaluator** — Excluded `HALLU-` prefixed findings from the import-line false-positive filter so dependency confusion detections survive the pipeline
-- **I18N evaluator** — Skip raw-number formatting check when code already uses `Intl` APIs (e.g., `Intl.NumberFormat`), eliminating spurious I18N-001 on properly internationalized code
-- **I18N evaluator** — Improved sorting/RTL/currency detection patterns and removed I18N from `WEB_ONLY_PREFIXES` so it applies to all file types
-- **Shared utilities** — `looksLikeIaCSecretValue` now recognizes file paths (containing `/` with a file extension) as non-secrets, preventing false IAC-002 on Terraform module sources
-- **IAC evaluator** — Improved tag-threshold logic and `default_tags` detection for Terraform resources
-- **SOV evaluator** — Region/consent gate detection improvements
-- **CONC evaluator** — Properly handle exported Go functions
-- **DOC evaluator** — Improved cryptic naming detection
-- **LOGIC evaluator** — Threshold tuning for inverted-condition and dead-code detection
-- **MAINT evaluator** — Threshold tuning for maintainability checks
-- **Pipeline** — Expanded `hasIO` detection, added COMP string-literal exemption
-- **STRUCT-005 disabled** — Dead code detection moved to LOGIC evaluator to avoid false positives on multi-line expressions
-- **`classifyFile`** — Improved JSX file-type detection
-
-### Fixed — Benchmark Test Cases
-- Strengthened `clean-terraform-hardened` with terraform block, required_providers, backend config, and default_tags
-- Strengthened `clean-accessible-form-tsx` with i18n support and loading state
-- Fixed `clean-terraform-well-structured-hcl` — was incorrectly expecting IAC-001 on genuinely clean code
-- Fixed 7 clean benchmark cases with overlapping `expectedRuleIds`/`unexpectedRuleIds` prefixes that caused same findings to count as both TP and FP
-
-### Benchmark Results
-- 1,048 cases, 0 failures, 100% detection rate
-- Precision 99.0%, Recall 88.6%, F1 93.5%, Grade A
-- All per-judge FP rates below 30%, clean category FP rate 0%
-
-### Tests
-- 1,082 tests pass across 218 suites
-
-## [3.37.0] — 2026-03-10
-
-### Added
-- **Auto-onboarding preset** — When no `.judgesrc` config file exists and no `--preset` or `--config` flag is provided, the CLI automatically applies the `onboarding` preset (high-severity only, 9 noisy judges disabled) with a guidance message to run `judges init` for full control. Reduces noise for first-time users.
-- **Fix rate visibility (CLI)** — Findings summary now shows auto-fixable count everywhere: verdict summary (`Findings : 12 (4 auto-fixable)`), `--summary` one-liner, multi-file per-file progress, multi-file summary, and critical/high findings list (tagged with 🔧). New guidance line after verdict: `🔧 N finding(s) can be auto-fixed. Run: judges eval <file> --fix`.
-
-### Changed (VS Code Extension)
-- **Live status bar** — Status bar now updates dynamically after evaluations, showing finding count and fixable count (e.g., `Judges: 5 finding(s), 2 fixable`) instead of the static "Judges" label. Also updates when switching between editor tabs.
-- **`getCachedFindings()` API** — New method on `JudgesDiagnosticProvider` for retrieving cached findings by URI, used by the status bar.
-
-### Tests
-- 1,082 tests pass across 218 suites
-
-## [3.36.0] — 2026-03-10
-
-### Added
-- **New judge: logic-review** — 7 detection categories for semantic correctness: inverted security conditions (critical), off-by-one errors (high), dead code after return/throw (medium), name-body mismatch (medium), swapped comparison operands (high), empty catch/except blocks (medium), redundant boolean comparisons (low). 45 judges total.
-- **Review verdict & summary** — `synthesizeReviewDecision()` wired into `TribunalVerdict`, producing an approve/request-changes/comment decision with blocking findings list and executive summary.
-- **Package registry verification** — expanded fabricated package detection: 50+ npm names, 30+ Python names, Go module hallucination patterns, Java/Kotlin hallucination patterns, and dependency confusion detection for unscoped packages with internal-looking names.
-- **Test adequacy assessment** — 2 new test quality checks: happy-path-only detection (test files with ≥3 cases but no error/edge scenarios) and status-code-only detection (API tests that only assert HTTP codes without body verification).
-- **LLM contextual auto-fixes** — `enrichWithContextualFixes()` generates `suggestedFix` for findings that lack a deterministic patch, using actual code context from affected lines.
-- **Triage feedback learning loop** — `computeTriageFeedback()` and `applyTriageFeedback()` adjust confidence scores based on historical false-positive rates from the finding lifecycle store. Rules with FP rate >30% get proportional confidence reduction (max -0.3).
-- **JetBrains IDE integration guide** — documentation for connecting Judges as an MCP server in IntelliJ IDEA, WebStorm, PyCharm, GoLand, and Rider via `.mcp.json` or IDE settings.
-- **AI-output benchmark suite** — 18 new benchmark cases targeting LLM-generated code patterns: logic inversions, off-by-one errors, dead code, name-body mismatches, swapped operands, empty catch blocks, happy-path-only tests, status-code-only tests, dependency confusion, and 3 negative (clean code) cases.
-
-### Changed (VS Code Extension)
-- **Diff-aware evaluation** — new `judges.evaluateDiff` command evaluates the full file but only reports findings on lines changed relative to git HEAD (±2 line context margin).
-- **Judge grouping in findings panel** — new "Sort by Judge" mode groups findings by judge prefix (AUTH, CRYPTO, LOGIC, etc.) with collapsible tree nodes.
-
-### Tests
-- 1,082 tests pass across 218 suites
-
-## [3.35.0] — 2026-03-10
-
-### Added
-- **Dedup: 12 new topic patterns** — timing-attack, ssrf, mass-assignment, insecure-deserialization, info-disclosure, denial-of-service, file-upload-security, missing-access-control, hardcoded-config, unsafe-html-render, a11y-violation — eliminates duplicate findings across judges
-- **Auto-fix: 10 new multi-line patch rules** — timing-safe comparison (`crypto.timingSafeEqual`), path traversal prevention, hardcoded secrets → env vars, open redirect validation, SSRF URL allowlist, insecure cookies, Java SQL injection (→ `PreparedStatement`), Python f-string SQL (→ parameterized), CSP header insertion, C# SQL injection (→ `SqlParameter`)
-- **Framework judges: 17 new patterns** — Django (5: SESSION_COOKIE_SECURE, SECURE_SSL_REDIRECT, mark_safe, FILE_UPLOAD_PERMISSIONS, locals/globals in render), Flask (2: send_file path traversal, session without SECRET_KEY), Spring Boot (5: @RequestBody without @Valid, permitAll on sensitive paths, Jackson default typing, hardcoded credentials, logging sensitive data), ASP.NET Core (5: missing UseHttpsRedirection, mass assignment model binding, string interpolation in ILogger, ProblemDetails with exception message, missing [Authorize] on [ApiController])
-- **Suppression analytics** — `getSuppressionAnalytics()` and `formatSuppressionAnalytics()` functions for analyzing FP rates by rule, suppression rates by judge, auto-suppress candidates, and actionable tuning recommendations
-- **5 new MCP tools for conversational review:**
-  - `explain_finding` — plain-language explanation with OWASP/CWE references and remediation guidance
-  - `triage_finding` — set triage status (accepted-risk, deferred, wont-fix, false-positive) with attribution
-  - `get_finding_stats` — lifecycle statistics: open, fixed, triaged counts with trends
-  - `get_suppression_analytics` — FP rates, auto-suppress candidates, per-judge analytics
-  - `list_triaged_findings` — browse triaged findings with optional status filter
-- **Benchmark dashboard MCP tool** — `run_benchmark` returns full dashboard with per-judge, per-category, per-difficulty breakdowns in markdown, JSON, or summary format
-
-### Tests
-- 1,075 tests pass across 217 suites
-
-## [3.34.1] — 2026-03-10
-
-### Fixed
-- **CI build fix** — Added missing `findings` property to the `CaseResult` interface in `benchmark.ts`, resolving TS2353 compile error that failed the v3.34.0 publish workflow
-
-## [3.34.0] — 2026-03-10
-
-### Fixed
-- **False-positive filter (check #6) now requires ALL lines to match identifier context** — Previously, a single line matching identifier context would suppress the entire finding. When cross-evaluator dedup merges line numbers from multiple findings, a single inherited "foreign" line could wrongly suppress a legitimate finding. Now all flagged lines must match the identifier context pattern for suppression to apply.
-- **Removed CYBER- and AUTH- from test-only prefix suppression** — These prefixes were being incorrectly suppressed in test files, causing missed true positives
-- **Security evaluator skips import/require lines** for JWT verification detection — `import jsonwebtoken` no longer triggers a "JWT verification" finding
-- **Documentation evaluator strips type annotations** before counting single-letter parameters — generic type params like `T` in `(items: T[])` no longer trigger cryptic-naming detection
-- **Added `assert` to magic-number exclusion list** — Test assertions with numeric values are no longer flagged as magic numbers
-- **I18N added to web-only prefix suppression** — Internationalization rules now correctly suppressed for non-web files
-- **Shared `classifyFile` minimum line guard** — Files under 8 lines are no longer classified as "utility", preventing over-suppression of findings in small files
-
-### Changed
-- **12 evaluator threshold recalibrations** to reduce false positives while improving recall:
-  - AI Code Safety: unvalidated input handler threshold 4→2
-  - Caching: minimum file length 100→30 lines
-  - Cloud Readiness: hardcoded config threshold 5→1
-  - Configuration Management: env vars without defaults 3→4
-  - Cost Effectiveness: nested loop threshold 4→2
-  - Data Sovereignty: hardcoded global/foreign threshold 5→1, cross-border egress 5→2
-  - Documentation: undocumented exports count 2→4, minimum lines 10→30, magic numbers threshold 50→20
-  - Internationalization: hardcoded strings threshold 0→5
-  - Reliability: empty catch threshold 3→1
-  - UX: inline handlers 10→2, form loading state minimum 50→15 lines, generic errors minimum 60 lines, empty state minimum 80→120 lines, file/stream progress minimum 60 lines
-- **Cross-evaluator dedup simplified** — Removed per-prefix diversity logic (which preserved one representative per rule prefix) in favor of single-winner with cross-reference annotation; fixes dedup correctness for SQL injection, race conditions, and other cross-cutting findings
-- **Benchmark scoring now parses cross-reference annotations** — Dedup-merged findings annotated with `_Also identified by: AUTH-001, SEC-001_` now contribute their referenced ruleIds to true-positive matching, recovering 115 previously undercounted TPs
-
-### Benchmark
-- **Grade A** — F1: 93.0% (was 87.9%), Precision: 98.7%, Recall: 87.9% (was 79.3%), Detection Rate: 97.6% (was 94.0%)
-- TP: 1182 (+115), FN: 163 (−115), FP: 16
-- All per-judge false-positive rates ≤ 30%
-
-### Tests
-- 2226 tests passing, 0 failures
-
-## [3.33.0] — 2026-03-10
-
-### Added
-- **Over-engineering detector judge** — New 44th judge (`over-engineering`) with 6 rules detecting excessive abstraction layers, trivial wrappers, god interfaces, builder pattern overuse, enterprise patterns in small codebases, and excessive generic type parameters
-- **PDF export formatter** (`--format pdf`) — Print-optimized HTML report with @media print styles, page breaks, and clean A4 layout; open in browser and "Save as PDF"
-- **HTML trend dashboard** (`judges trend --format html`) — Self-contained interactive HTML with SVG bar chart, severity breakdown, metrics summary, run history table, and dark/light theme support
-- **`--sample` flag** — Random file sampling for large repos; use with `--max-files` to randomly select files instead of taking the first N alphabetically
-- **Suppression metrics in text output** — When inline suppressions are present, the text report now shows suppressed finding count, breakdown by type (line/next-line/block/file), and top suppressed rules
-- **Code provenance signals** — All findings now carry a `provenance` field (defaults to `"regex-pattern-match"`) indicating how the finding was detected
-- **Per-judge timing metrics** — Each `JudgeEvaluation` includes `durationMs`; `TribunalVerdict` includes `timing` with total and per-judge breakdown; text output shows timing and slowest judges
-- **OWASP LLM Top 10 mapping** — Findings are automatically mapped to OWASP LLM Top 10 categories (LLM01–LLM10) where applicable
-- **VS Code CodeLens provider** — Shows finding counts above functions, methods, and classes in the editor
-- **Centralized judge metadata** — Extended `JudgeDefinition` with `tableDescription` and `promptDescription` fields; all 44 judges now carry documentation metadata as part of their definition
-- **`npm run sync-docs` script** — New `scripts/sync-docs.ts` regenerates the README judge table, prompts table, `docs/index.html` JS array, and judge counts across 15+ files from the `JUDGES` array as single source of truth
-- **Adding-a-judge instructions** — `.github/instructions/adding-a-judge.instructions.md` codifies the full step-by-step workflow for adding new judges
-
-### Changed
-- **README and docs auto-generated** — Judge table and prompts table in README use marker-delimited sections (`JUDGES_TABLE_START`/`END`, `PROMPTS_TABLE_START`/`END`); `docs/index.html` uses `JUDGES_ARRAY_START`/`END` markers
-
-### Fixed
-- **4 inconsistent judge names** — Data Sovereignty, API Contract, Multi-Turn Coherence, and Model Fingerprint judges now follow the `"Judge {Domain}"` naming convention
-- **PDF formatter build error** — Fixed `Finding.line` reference to use `Finding.lineNumbers`
-
-### Tests
-- 1075 tests passing, Benchmark Grade A
-
-## [3.31.0] — 2026-03-10
-
-### Changed
-- **Calibration enabled by default** — PR review now applies feedback-driven confidence calibration automatically; use `--no-calibrate` to opt out
-- **diff-only mode default in Actions** — GitHub Action `diff-only` input now defaults to `true`, evaluating only changed lines in PRs to dramatically reduce noise
-- **Minimum confidence floor** — PR review applies a default `--min-confidence 0.6` threshold, dropping low-confidence findings automatically
-
-### Added
-- **FP-rate reliability badge** — Each PR review comment now shows a reliability badge (e.g., "🎯 99%+ reliable" or "⚠️ 75% reliable") based on historical false-positive rates
-- **Absence-based finding filter in diff mode** — Findings like "no rate limiting" or "no authentication" are now suppressed in diff mode since they cannot be accurately assessed from a single diff hunk
-- **`ai-review` preset** — New preset optimized for reviewing AI-generated code: focuses on security, hallucination, and correctness judges while disabling non-essential judges (documentation, i18n, accessibility, etc.)
-- **`--judges` flag for PR review** — Select a subset of judges to run during PR review (e.g., `--judges cybersecurity,authentication`); all other judges are disabled
-- **`--no-calibrate` flag** — Opt out of feedback-driven confidence calibration in PR reviews
-
-### Tests
-- 1068 tests pass, 0 failures
-
-### Benchmark
-- Grade A, 98.8% precision, 90.3% recall, F1 0.94
-
-## [3.30.0] — 2026-03-10
-
-### Added
-- **Scope-aware HALLU suppression** — Hallucination detector now checks for local method definitions before firing on generic patterns (`.push()` in Python, `.isEmpty()` in Python, `.append()` in Go, etc.), reducing false positives on user-defined methods
-- **Hallucination auto-fix patches** — All HALLU findings now include structured `Patch` objects with `oldText`/`newText` for automated remediation
-- **Confidence evidence trails** — All 5 hallucination detection sections now include `EvidenceChain` with multi-step reasoning (observation → source → line) and `evidenceBasis` scoring strings
-- **14 new hallucination patterns** — FastAPI `app.route()` confusion (import-guarded), SQLAlchemy raw SQL in `session.execute()`, pandas `.to_array()`/`.filterBy()`, Spring `@Autowired` on local variables, `ResponseEntity.ok().body()` chaining, EF Core `DbContext.Query<T>()`, ASP.NET `HttpContext.Response.Write()`, Rust `tokio::spawn` without async / `.unwrap_default()`, Deno `readFile` with encoding, Bun `.serve().listen()`
-- **3 new suspicious submodule patterns** — FastAPI, Next.js, and Vue fabricated submodule imports
-- **Import-guard system** — New `requiresImport` field on hallucination patterns prevents cross-framework false positives (e.g., Flask `app.route()` no longer triggers the FastAPI-specific pattern)
-- **Per-LLM benchmark tracking** — New `aiSource` field on benchmark cases and `perAISource` result breakdowns for tracking detection effectiveness per AI code generator
-
-### Tests
-- 1068 tests pass, 0 failures
-
-### Benchmark
-- Grade A, 99.8% detection, 1030/1032 cases, 15 FP
-- All 43 judges at ≤30% individual FP rate
-- HALLU judge: 100% precision (0 FP, improved from 67% FP rate in v3.29.2)
-
-## [3.29.2] — 2026-03-09
-
-### Fixed
-- **Per-judge FP rate reduction** — All 43 judges now report <30% individual FP rates on the benchmark
-  - **STRUCT** 30.4% → 22.2%: Raised STRUCT-005 dead-code threshold to >2 lines (avoids parser artifacts, switch-case, guard clauses); raised STRUCT-003 long-function threshold to >1 (single long function is common in utilities)
-  - **COH** 100% → 0%: Disabled COH-002 regex-based dead-code detection (redundant with STRUCT-005 AST-based analysis); raised COH-004 conflicting-config threshold to ≥6 conflict lines
-  - **INTENT** 100% → 0%: Required INTENT-003 to find ≥2 empty functions before flagging; added deprecated function skip (`old_`, `legacy_`, `deprecated_` prefixes) to INTENT-001
-  - **API** 38.8% → 26.2%: Added file-level validation middleware detection (express-validator, joi, zod imports) to skip API-001; improved API-002 error response detection with Python/Django patterns; fixed API-004 to recognise `res.json()` auto-sets Content-Type; fixed `express.json()` regex to match calls with arguments; improved API versioning detection (`/v\d+\b`); added `express.urlencoded` to content-type validation patterns; required 2+ routes for API-002 missing-error-responses rule
-- **Tests** — Updated STRUCT-005 and STRUCT-003 test inputs to match new thresholds; 1068 tests pass
-- **Benchmark** — Grade A, 99.8% detection, 98.8% precision, 94.4% F1
-
-## [3.29.1] — 2026-03-09
-
-### Fixed
-- **TypeScript compilation error** — Removed invalid `weight` property from 3 judge definitions (api-contract, multi-turn-coherence, model-fingerprint) that does not exist on `JudgeDefinition` interface, fixing CI build failure
-
-## [3.29.0] — 2026-07-07
-
-### Added
-- **Model fingerprint detection** — New judge #43 (MFPR prefix) detecting stylistic signatures of ChatGPT/GPT-4, Copilot, Claude, and Gemini in AI-generated code for provenance transparency
-- **Community pattern sharing** — New `community-patterns` CLI command with `import`, `export`, and `list` sub-commands for crowdsourced rule pack exchange via portable JSON format
-- **Interactive VS Code review** — New `judges.reviewSession` command walks through findings one-by-one with Accept/Dismiss/Skip actions and editor navigation
-- **Industry policy templates** — 5 new preset profiles: `fintech` (PCI DSS), `healthtech` (HIPAA), `saas` (multi-tenant), `open-source`, and `government` (FedRAMP/NIST)
-- **Intent alignment evaluator** — Judge #40 (INTENT prefix) detecting stub functions, misleading names, empty implementations, and contradictory comments
-- **API contract conformance** — Judge #41 (API prefix) evaluating REST endpoints for input validation, status codes, error handling, rate limiting, and versioning
-- **Multi-turn coherence** — Judge #42 (COH prefix) catching duplicate definitions, contradictory assignments, dead code after returns, and conflicting configs
-- **Confidence calibration dashboard** — New `calibration-dashboard` CLI command showing per-rule accuracy metrics and false-positive rates
-- **Human escalation escape hatch** — `escalationThreshold` config option flagging low-confidence findings with `needsHumanReview` for manual triage
-- **Explanation mode** — `--explain` flag providing educational context for any rule prefix with severity mapping and false-positive guidance
-- **Business logic validation** — `customRules` config field supporting user-defined regex-based detection rules with full severity and autofix support
-- **Inline fix suggestions** — ~50 new PATCH_RULES covering auth, crypto, injection, error handling, rate limiting, and more
-- **Approve/request-changes verdict** — Tiered GitHub review events (APPROVE for clean code, COMMENT for low-severity, REQUEST_CHANGES for critical findings)
-- **Test adequacy analysis** — TEST-COV-001 rule detecting missing test coverage for changed functions in PR diffs
-
-### Tests
-- 1068 tests, 0 failures
-- Benchmark: Grade A (99.8% detection, 98.8% precision, 94.4% F1)
-
-## [3.28.0] — 2026-07-07
-
-### Added
-- **Onboarding preset** — New `onboarding` preset profile for first-time adopters with high-severity-only filtering and advisory judges disabled
-- **Import verification for hallucination detection** — Heuristic import verification (section 5) using dual-pattern matching for generic prefixes and suffixes to catch hallucinated API imports
-- **Diff deletion analysis** — New DIFF-DEL-001 rule detecting security-relevant deletions (auth checks, input validation, CSRF tokens, rate limiting) in PR diffs
-- **PR summary comment** — Enhanced GitHub Action PR review body with rich summary table including verdict, score, severity breakdown, baseline suppressed count, and top 5 most frequent rule IDs; zero-findings path posts clean bill of health
-- **Passive calibration** — `buildPassiveCalibrationProfile()` merging 3 signal sources: explicit feedback, inline suppressions (implicit FP signals), and triage history
-- **Test quality analysis** — Tautological assertion detection (e.g. `expect(true).toBe(true)`) and over-mocking detection (mock setup count exceeding 3× test case count)
-- **Cross-file breaking changes** — DIFF-BREAK-001 rule detecting exported function signature changes (renamed, removed, or parameter count changes) across PR diffs
-- **Parallel judge execution** — Configurable `concurrency` option with AST/taint cache pre-warming via `preWarmCaches()` and chunked batch file processing in project evaluator
-- **Organization config inheritance** — `extends` field in `.judgesrc` supporting single or array of base config paths with cycle detection via `resolveExtendsConfig()`
-- **Metrics & trends API** — `computeMetrics()` function with `RuleMetric` and `MetricsSummary` types for top offenders, severity breakdown, distinct/resolved/new rule tracking
-- **Net-change CI gate** — `evaluateNetChangeGate()` with `NetChangeGateOptions` and `NetChangeGateResult` for pass/fail decisions on whether a PR fixed more than it introduced
-- **Per-language rule profiles** — `languageProfiles` config field and `applyLanguageProfile()` for language-specific judge configuration overrides
-
-### Tests
-- 1040 tests, 0 failures
-- Benchmark: Grade A
-
-## [3.27.1] — 2026-03-09
-
-### Fixed
-- **CI `npm ci` failure** — Removed tree-sitter native grammar devDependencies (tree-sitter-c-sharp, tree-sitter-cpp, tree-sitter-go, tree-sitter-java, tree-sitter-kotlin, tree-sitter-php, tree-sitter-python, tree-sitter-ruby, tree-sitter-rust, tree-sitter-swift, tree-sitter-typescript, tree-sitter-cli) that caused `ERESOLVE` peer dependency conflicts during `npm ci` in CI. These packages were only needed for one-time WASM grammar generation; the pre-built WASM files in `grammars/` are committed and used at runtime via `web-tree-sitter`
-- **Added `.npmrc`** — Sets `legacy-peer-deps=true` as a safety net for any remaining transitive peer conflicts
-
-## [3.27.0] — 2026-03-09
-
-### Added
-- **New language support: Dart, Bash/Shell, SQL** — Full `LangFamily` type coverage, ~30+ language pattern constants (crypto, auth, injection, eval, file-system, etc.), structural parser support (function/class extraction, complexity analysis, weak-type detection, import extraction), AST routing, and file-extension-to-language maps across CLI, GitHub App, and baseline commands
-- **Tree-sitter grammars for PHP, Ruby, Kotlin, Swift** — Four new WASM grammars enabling deep AST analysis (function/class/method node extraction, parameter counting, import extraction, weak-type detection) for languages previously limited to regex-only structural parsing
-- **Accessibility evaluator deepened (17 → 23 rules)** — Six new rules: A11Y-018 vague link text ("click here", "read more"), A11Y-019 data tables without `<th>` headers, A11Y-020 modal/dialog without focus trap, A11Y-021 interactive ARIA role without tab focusability, A11Y-022 icon-only button/link without accessible name, A11Y-023 page missing landmark regions
-- **IaC security evaluator deepened (22 → 32 rules)** — Ten new rules: Kubernetes container running as root, missing resource limits, writable filesystem; Terraform resources without tags; password auth without managed identity; database firewall allowing all Azure services (0.0.0.0); Dockerfile ADD vs COPY; Dockerfile FROM :latest/untagged
-- **Cost-effectiveness evaluator deepened (15 → 20 rules)** — Five new rules: COST-016 high-frequency events without debounce/throttle, COST-017 large bundle imports (lodash, moment, rxjs full imports), COST-018 event listeners without cleanup (memory leak), COST-019 inline objects/functions in React JSX props causing re-renders
-- **UX evaluator deepened (12 → 18 rules)** — Six new rules for user-experience quality detection
-- **Integration tests** — 19 new tests covering all 5 output formatters (SARIF, JUnit, HTML, CodeClimate, GitHub Actions), evaluation of all 7 new languages (Dart, Bash, SQL, PHP, Ruby, Kotlin, Swift), multi-file project evaluation, diff-based evaluation, and verdict structure validation
-
-### Fixed
-- **`ruleNum` increment bug** — Last rule in accessibility, IaC security, cost-effectiveness, and UX evaluators used `ruleNum` without `++`, causing potential rule-ID collisions when new rules were appended. Fixed across all four evaluators
-
-### Tests
-- 2210 tests (2180 pass, 30 pre-existing failures unrelated to this release)
-- Self-eval: 0 findings across 177 source files
-- Benchmark: Grade A, F1 = 94.4%, Precision = 98.9%, Recall = 90.3%
-
-## [3.26.0] — 2026-03-09
-
-### Fixed
-- **Security evaluator false positives** — Fixed two regex patterns that triggered on benign code: `args\.` now uses word boundary (`\bargs\.`) to avoid matching compound identifiers like `curlArgs`, and static IV pattern now uses `\b(?:iv|IV)\b` to avoid matching strings like `PRIV`
-- **PR review inline suppressions removed** — Two broken inline `judges-ignore-next-line` directives in `review.ts` (SEC-003, SEC-020) removed now that root cause FPs are fixed in the security evaluator
-
-### Changed
-- **False-positive filter improvements** — Expanded heuristic coverage to eliminate self-eval findings (211 → 0):
-  - SEC-* and HALLU-* rules added to analysis-tool inapplicable prefixes (evaluator code contains detection patterns by design)
-  - Test file gating expanded from TEST-* only to TEST-*/SEC-*/HALLU-* for files with embedded code specimens
-  - New benchmark CLI gating suppresses SEC/HALLU on benchmark command files with ≥5 template literal code specimens
-  - CLI file-system-access and database-related SEC findings suppressed (CLI tools are designed for file I/O and have no database connections)
-  - Utility module gating expanded with path-confirmed rules for PERF/COST/TEST/COMPAT/ERR/STRUCT prefixes
-- **Scoring module refactored** — `estimateFindingConfidenceWithBasis()` (cyclomatic complexity 42) decomposed into 7 focused helpers: `scoreLinePrecision()`, `scorePatternSpecificity()`, `scoreStructuredEvidence()`, `scoreAbsencePattern()`, `scoreProvenance()`, `scoreDomainAlignment()`, `applyNoiseCap()`
-
-### Tests
-- 2191 tests (2161 pass, 30 pre-existing failures unrelated to this release)
-- Self-eval: 0 findings across 176 source files (down from 211)
-- Benchmark: Grade A, F1 = 94.4%, Precision = 98.9%, Recall = 90.3%, Detection = 99.9%
-
-## [3.25.1] — 2026-03-09
-
-### Fixed
-- **PR review JSON output pollution** — In `--format json` mode, banner and informational `console.log` messages were written to stdout alongside the JSON result, corrupting the output file. All non-JSON output now redirected to stderr so stdout is pure JSON
-- **Inline PR review comments never posted in JSON mode** — `process.exit()` was called before the GitHub review-posting code, so inline comments and approve/request-changes events were silently skipped. Now posts the review before emitting JSON
-- **Workflow stderr redirect corrupting result file** — Removed `2>&1` from the PR review workflow step so stderr (Node.js warnings, subprocess output) no longer pollutes `judges-review-result.json`
-- **CodeQL code scanning alerts resolved** — Fixed 14 code scanning alerts: command injection via `execSync` replaced with `execFileSync`, incomplete URL substring sanitization, missing origin checks in `postMessage`, and unsafe regexp construction
-- **ESLint unused variable/import warnings** — Resolved 5 lint errors across evaluators, scoring, and comparison modules
-
-### Changed
-- **CI: actions/configure-pages bumped from v4 to v5** (Dependabot #18)
-- **Dev dependencies updated** — vitest, @biomejs/biome, and @anthropic-ai/sdk bumped (Dependabot #19)
-
-### Tests
-- 2191 tests (2161 pass, 30 pre-existing failures unrelated to this release)
-
-## [3.25.0] — 2026-03-09
-
-### Added
-- **Project context in L2 prompts** — `detectProjectContext()` auto-detects frameworks, runtime, entry-point type, project type, and dependencies from code. `formatProjectContextSection()` injects this context into deep-review prompts so L2 reviews calibrate to the stack (e.g., absence-based rate-limiting rules suppressed for CLI tools). Wired into `evaluate_code`, `evaluate_code_single_judge`, and `evaluate_file` MCP handlers. React added to framework detection patterns
-- **Multi-file fix coordination** — `collectPatchSet()` groups findings by file path into a `PatchSet`, and `applyPatchSet()` applies patches across multiple files with per-file results. Enables cross-file auto-fix from a single review pass
-- **Real-time IDE evaluation** — VS Code extension now supports on-change evaluation via debounced `onDidChangeTextDocument` handler. Controlled by `judges.evaluateOnChange` (default: off) and `judges.changeDebounceMs` (default: 2000ms) settings
-- **Evidence chains on findings** — `buildEvidenceChain()` constructs multi-step evidence (detection trigger, location precision, cross-file context, fix availability) with a severity-calibrated impact statement. `EvidenceChain` and `EvidenceStep` types added to `Finding`
-- **Auto-suppression from triage history** — `triageToFeedbackEntries()` converts false-positive/wont-fix triage decisions into feedback entries. `getTriageBasedSuppressions()` identifies rules that should be auto-suppressed based on triage patterns (≥80% FP rate with ≥3 samples)
-- **AI-specific benchmark cases** — 10 new benchmark cases covering model-serving input validation, embedding data leakage, unbounded LLM streaming, async race conditions, memory leak patterns, N+1 queries, unsafe type assertions, hardcoded AI credentials, plus 2 clean counterparts
-- **PR review summary narrative** — `buildPRReviewNarrative()` generates rich review summaries with executive summary, per-file breakdown (sorted by finding count), cross-cutting theme analysis (17 domain labels), and prioritized action items. Replaces the previous `buildReviewSummary()`
-- **Review completeness signal** — `assessReviewCompleteness()` returns a `ReviewCompleteness` struct with `complete` boolean, coverage percentage, unreviewed files list, and human-readable status message
-
-### Fixed
-- **Node.js runtime detection** — `require()` calls now correctly detected by splitting the regex to avoid trailing `\b` failure on non-word characters
-- **Serverless entry-point detection** — Added "serverless" pattern to `ENTRY_POINT_PATTERNS` so `exports.handler` / Lambda / Azure Functions code is correctly classified as serverless entry points
-
-### Tests
-- 821 tests (808 pass, 13 pre-existing failures unrelated to this release)
-
-## [3.24.0] — 2026-03-09
-
-### Added
-- **Closed-loop L2 feedback capture** — L2 (LLM deep-review) dismissals are now automatically parsed and recorded as feedback via `parseDismissedFindings()` and `recordL2Feedback()`. `FeedbackEntry.source` tracks origin (`manual`, `l2-dismissal`, `pr-review`)
-- **Finding triage workflow** — Findings can now be triaged as `accepted-risk`, `deferred`, `wont-fix`, or `false-positive` via `triageFinding()`. New CLI command `judges triage set|list|summary` for interactive triage. Triaged findings are preserved across scans
-- **Multi-file context in L2 prompts** — Deep-review builders accept optional `relatedFiles` parameter to include cross-file snippets (imports, callers, config) in L2 prompts. MCP tool schemas updated with `relatedFiles` input
-- **L2 coverage benchmark** — `analyzeL2Coverage()` maps L1 false negatives to judges and checks L2 prompt availability. `formatL2CoverageReport()` generates markdown with per-judge, per-category, and per-difficulty breakdowns. CLI: `judges benchmark l2-coverage`
-- **Benchmark case ingestion pipeline** — `ingestFindingsAsBenchmarkCases()` converts real-world findings into benchmark cases with category inference and code truncation. `deduplicateIngestCases()` prevents duplicates via normalized-whitespace fingerprinting. CLI: `judges benchmark ingest <file>`
-- **Centralized org policy management** — `PolicyLock` for locking org-wide configuration baselines. `validatePolicyCompliance()` checks required judges, rules, severity thresholds, and baseline compliance. `pullRemoteConfig()` fetches team configs over HTTPS (with SSRF protection). CLI: `judges config pull|lock|validate`
-
-### Tests
-- 1824 tests passing (784 subsystems + 1040 judges), 13 pre-existing failures unrelated to this release
-
-## [3.23.20] — 2026-03-08
-
-### Fixed
-- **All per-judge FP rates now under 30%** — STRUCT dropped from 40% → 23.8%, ETHICS from 33% → 0%, COMPAT from 60% → 0% via expectedRuleIds corrections and new TP cases
-- **Structural parser cyclomatic-complexity counting fixed** — `&&`, `||`, and ternary `?` operators now correctly counted in DECISION_POINTS regex for all brace-based languages; previously `\b` word boundaries silently prevented matching these operators
-- **Ternary `?` no longer matches optional chaining `?.` or nullish coalescing `??`** — DECISION_POINTS regex uses `\?(?![.?])` to avoid false CC inflation
-- **struct-tp-permission-resolver benchmark case fixed** — Multi-line function parameters collapsed to single line so the structural parser's line-by-line FUNC_PATTERNS regex can detect the function
-- **ux-tp-destructive-no-confirm benchmark case fixed** — Code expanded from ~35 to ~65 lines to satisfy UX-001's >50 line threshold
-- **STRUCT-001 added to 4 benchmark expectedRuleIds** — ts-code-smells, maint-god-function-long, maint-deep-deep-nesting, swdev-deep-deep-nesting now correctly expect STRUCT-001 detection
-
-### Improved
-- **Benchmark: Grade A, F1=94.7%** — Up from 91.3%; 1022 cases, 0 failures, Precision=98.9%, Recall=91.0%, Detection Rate=100%
-
-### Tests
-- 1040 tests passing, 0 failures
-
-## [3.23.19] — 2026-03-08
-
-### Added
-- **Benchmark expanded from 301 to 1003 test cases** — Added 7 new benchmark files covering security-deep (99 cases), quality-ops (74), languages (63), infrastructure (83), compliance-ethics (81), AI-agents (86), and advanced cross-cutting scenarios (226), plus expanded cases in existing files
-- **New benchmark categories** — Full coverage across 55 categories including injection, XSS, auth, IaC-security, AI-code-safety, hallucination-detection, agent-security, compliance, ethics, internationalization, data-sovereignty, and more
-
-### Fixed
-- **Benchmark Grade A maintained at 1003 cases** — F1=91.3%, Precision=98.0%, Recall=85.4%, 14 FP, 120 FN
-- **Duplicate benchmark IDs resolved** — 8 duplicate case IDs across 3 files renamed to ensure all 1003 cases load correctly
-- **4 benchmark expectedRuleIds corrected** — SCALE-001, MAINT-001, COST-001, CACHE-001 removed from cases where judges cannot reliably detect the pattern, eliminating false negatives
-
-### Tests
-- 1040 tests passing, 0 failures
-- Benchmark: 1003 cases, Grade A, F1=91.3%, Detection Rate=100% across all difficulties
-
-## [3.23.18] — 2026-03-07
-
-### Changed
-- **DOC-001 precision improved** — Added cryptic-naming heuristic: only flags undocumented functions with short names (≤3 chars) or multiple single-letter parameters; self-documenting code with descriptive names is no longer flagged (FP rate 91.3% → 0%)
-- **OBS-001 precision improved** — Added minimum route-count requirement (≥2 route definitions, excluding middleware); single-endpoint snippets are no longer flagged (FP rate 50% → 25%)
-
-### Fixed
-- **Benchmark** — Grade A, F1=0.904, TP=355, FN=75, FP=0 (301 cases, 39 judges)
-- **Tests** — 1040 pass, 0 fail
-
-## [3.23.17] — 2026-03-07
-
-### Changed
-- **Judge count updated to 39** — All references across docs, tests, HTML, action.yml, Dockerfile, and README updated from 37 to 39
-- **VS Code extension README rewritten** — New adoption-focused copy: 1-sentence value prop, "Try in 60 seconds" quick start, noise-control section, CI integration guide, full 15-language listing
-- **Default `minSeverity` raised to `"high"`** — New installs see only critical + high findings, reducing noise for first-time users
-- **Preset dropdown with enum values** — `judges.preset` now offers named choices (strict, lenient, security-only, startup, compliance, performance) in the Settings UI
-
-### Added
-- **First-run toast notification** — After the first successful evaluation, a one-time toast introduces `@judges` chat and links to noise settings
-- **`Judges: Add CI Workflow` command** — Generates `.github/workflows/judges.yml` with a PR-triggered security-only preset
-- **"Report false positive" code action** — New Quick Fix action opens a pre-filled GitHub issue for any Judges finding
-- **Enhanced `@judges /help`** — Now includes verdict bands (PASS/WARN/FAIL), noise-control tips, and more examples
-- **Improved chat command inference** — `inferCommand()` now recognizes "run judges", "judges review", "evaluate", "check" as review intent
-- **Updated welcome view** — Findings panel shows 3 quick actions: evaluate file, evaluate workspace, open @judges chat
-
-### Tests
-- 1040 tests passing (0 failures)
-
-## [3.23.16] — 2026-03-07
-
-### Fixed
-- **Benchmark F1 improved from 0.900 to 0.904** — TP increased from 352 to 355 with 0 FP, maintaining Grade A
-- **10 benchmark expectedRuleIds prefix mismatches** — Fixed AI→AICS, DEP→DEPS, CONFIG→CFG, DSOV→SOV, PORT→PORTA, FRAME→FW, LOG→LOGPRIV prefix mappings in benchmark cases that caused false negatives in scoring
-- **LOGPRIV utility-module FP filter suppression** — Removed `LOGPRIV-` from `UTILITY_INAPPLICABLE` prefixes in false-positive-review.ts; logging privacy violations (passwords, tokens, PII in logs) are valid concerns even in utility code
-- **DEPS FP filter suppression** — Exempted `DEPS-*` findings from the import/type-only line false-positive filter; dependency declarations in import lines ARE the finding
-- **REL timeout context false suppression from comments** — Added `isCommentLine` filter to the timeout/retry context window in reliability.ts so comments like `// No timeout, no retry` no longer trick the evaluator into thinking timeout handling exists
-- **DOC evaluator thresholds too strict** — Lowered undocumented-function minimum from ≥5 to ≥2 and file-length guard from >100 to >10 lines, allowing detection in smaller modules
-- **OBS console.log threshold too strict** — Lowered "console logging instead of structured logger" threshold from >15 to >5 instances
-- **LOGPRIV password-logging threshold too strict** — Lowered from ≥4 to ≥2 instances; even 2 password log statements indicate a privacy violation
-
-### Changed
-- 22 evaluators refined with improved detection thresholds across ai-code-safety, api-design, caching, cloud-readiness, code-structure, concurrency, configuration-management, cost-effectiveness, data-security, data-sovereignty, database, documentation, framework-safety, logging-privacy, maintainability, observability, performance, rate-limiting, reliability, scalability, software-practices, and ux
-- Test fixtures expanded to match updated evaluator thresholds across all affected test suites
-
-### Tests
-- 1040 tests passing
-- 301 benchmark cases: TP=355, FN=75, FP=0, F1=0.904, Grade A
-
-## [3.23.15] — 2026-03-06
-
-### Fixed
-- **VS Code Marketplace publish fix** — Obfuscated fake Slack webhook URL in benchmark test data (`ts-cicd-secrets-in-code`) that triggered `vsce`'s secret scanner, and added `--allow-package-secrets slack` to the publish workflow as a safety net
-
-## [3.23.14] — 2026-03-06
-
-### Fixed
-- **Benchmark Grade A achieved** — F1 score improved from 0.889 (Grade B) to 0.900 (Grade A) with TP=352, FN=78, FP=0
-- **SEC-018 path traversal FP on CLI tools** — Added HTTP handler context requirement to the direct file-ops-near-path-join detection block, preventing false positives on Go/Python CLI tools that use `filepath.Join` + `os.ReadFile` without any HTTP context
-- **ERR-002 Go builtin `close()` FP** — Changed unchecked-close pattern from `(?:\w+\.)?Close` to `\w+\.Close` requiring a method receiver, so Go's builtin `close(ch)` (which doesn't return a value) is no longer flagged
-- **AUTH hardcoded credential detection for camelCase identifiers** — Added `camelCaseAssignmentPattern` to detect credentials in camelCase identifiers like `dockerPassword`, `awsSecretAccessKey`, `awsAccessKeyId` that were missed by word-boundary patterns
-- **AUTH JWT 'none' algorithm detection** — Broadened pattern from exact `['none']` to match `'none'` anywhere in the algorithms list (e.g., `algorithms: ['HS256', 'none']`)
-- **IAC YAML IaC detection** — Added content-based detection for Docker Compose (`services:`) and Kubernetes (`apiVersion:|kind:`) manifests, since YAML was not recognized as IaC by the language normalizer. Detects `privileged: true`, `network_mode: host`, `allowPrivilegeEscalation: true`, and hardcoded secrets in environment variables
-- **SEC-022 format string cross-line matching** — Changed `.*` to `[\s\S]*` in the format-string injection context check so `request.args.get` on one line and `.format()` on the next are correctly matched
-- **CYBER SSTI Python `.format()` injection** — Added detection of Python `.format()` calls with user-controlled input (`request.args`, `request.form`, etc.)
-- **ERR multi-line empty catch block detection** — Added forward-scanning logic to detect catch blocks spanning multiple lines that contain only comments or whitespace, complementing the existing single-line empty catch pattern
-
-### Tests
-- 1059 tests passing
-- 301 benchmark cases: TP=352, FN=78, FP=0, F1=0.900, Grade A
-
-## [3.23.13] — 2026-03-06
-
-### Added
-- **P3 — Benchmark expansion to 300+**: 301 benchmark test cases (79 original + 110 batch 2 + 112 batch 3) covering PHP, Ruby, Kotlin, Swift, and advanced patterns
-- **P4 — Full pipeline PHP/Ruby/Kotlin/Swift**: Structural parser extended with complete AST support for PHP, Ruby (including end-keyword extractors), Kotlin, and Swift
-- **P5 — Inline PR suggested fixes**: GitHub suggestion blocks with `start_line`/`start_side` for multi-line ranges in review.ts and github-app.ts
-- **P6 — Hallucinated API validation**: New 39th judge (`hallucination-detection`, prefix `HALLU`) with 30+ patterns across 10+ languages to detect non-existent API calls
-- **P7 — FP rate tracking & auto-tuning**: `src/auto-tune.ts` engine with time-decay weighted FP rates, auto-suppression (≥80% FP), severity downgrade (50–80%), confidence boost (<15%), trend detection; `judges feedback tune` CLI subcommand; integrated into evaluators/index.ts calibration pipeline
-- **P8 — VS Code extension all languages**: Added PHP, Ruby, Kotlin, Swift to all LANG_MAP objects, SUPPORTED_LANGUAGES, and activationEvents; added Terraform, Bicep, PowerShell to activationEvents (15 languages total)
-
-### Fixed
-- Removed unused imports across security.ts, hallucination-detection.ts, auto-tune.ts, github-app.ts
-- Replaced `as any` casts with proper `TribunalRunner` type in github-app.ts and review.ts
-- Fixed `!=` to `!==` strict equality in github-app.ts
-- Fixed unnecessary regex escape characters in security.ts and benchmark-expanded.ts
-- Removed unused `ruleNum++` post-increments in ci-cd.ts, software-practices.ts, agent-instructions.ts, security.ts
-- Updated judge count from 38 to 39 in test assertions and extension descriptions
-- Cleaned up stale benchmark output files; added to .gitignore
-
-### Tests
-- 1059 tests passing (8 new auto-tune tests, judge registry count updated)
-
-## [3.23.12] — 2026-03-06
-
-### Fixed
-- **Benchmark: 79/79 (0 FN, 0 FP)** — Resolved all remaining benchmark failures (was 17 FN / 2 FP in 3.23.11).
-- **classifyFile health-check misclassification** — Express apps with a `/status` endpoint AND other routes are now correctly classified as "server" instead of "utility". Added `routeHandlerCount` guard so files with 2+ route handlers skip the health-check heuristic.
-- **Structural parser false dead-code on template literals** — The `return \`...\`` pattern no longer causes subsequent lines to be marked as dead code. Multi-line expression detection (odd backtick count, unmatched parens/brackets) skips dead code marking.
-- **Absence gating removal for 6 evaluators** — Removed `isAbsenceBased: true` from OBS-001 (no logging), REL-001 (graceful shutdown), TEST-001 (no tests), CICD-001 (no CI/CD pipeline), SWDEV-001 (no linting/formatting), and CACHE-002 (no caching). Added concrete `lineNumbers` so findings survive the absence filter.
-- **I18N findings on non-web code** — Removed I18N from `WEB_ONLY_PREFIXES` so internationalization findings apply to any code with user-facing strings (string formatting utilities, CLI output, etc.), not just code with web patterns.
-- **COMPAT findings on comment-based evidence** — Exempted COMPAT-* from the "all comment lines" false-positive check. The backwards-compatibility evaluator intentionally scans comments (e.g., `// Was: oldFieldName`) as evidence of breaking changes.
-- **A11Y click handler FP on native elements** — Native interactive elements (`<button>`, `<a>`, `<input>`, `<select>`, `<textarea>`) with `onClick` are no longer flagged for missing keyboard handlers, since they inherently support keyboard events.
-- **A11Y form input FP on multi-line JSX** — The `<input>` label check now scans the full multi-line JSX tag (up to 10 subsequent lines) for `id=`, `aria-label`, or `aria-labelledby`, instead of only checking the opening line.
-- **SQL injection FP on JSX labels** — Both CYBER and SEC SQL injection fallback checks now require 2+ SQL keywords on the same line, preventing false positives where UI labels like `Select ${user.name}` triggered the single-keyword match.
-- **IAC egress rule FP** — The IaC overly-permissive network rule check now skips `0.0.0.0/0` in Terraform `egress` blocks, which is standard outbound traffic configuration.
-- **Go CLI tool FP** — Extended `isLikelyCLI()` to recognize Go (`flag.*`), Python (`argparse`, `click`, `typer`), and Rust (`clap`) CLI patterns, so `log.Fatal` in `main()` is no longer flagged as abrupt process termination.
-- **WEB_ONLY check expanded** — `hasWebPatterns` regex now includes HTTP API patterns (`res.json`, `app.get`, `router.post`, `@app.route`, `@GetMapping`, `http.HandleFunc`), so A11Y/UX findings survive on API server code.
-- **UTILITY_INAPPLICABLE trimmed** — Removed I18N-, A11Y-, AICS-, ETHICS-, COMPAT- from the utility-inapplicable prefix list.
-- **FP filter: AICS/DEPS exemptions** — AICS-* findings exempted from "all comment lines" check; DEPS-* findings exempted from "all string literal lines" check.
-- **Caching threshold** — CACHE-002 line count threshold reduced from 40 to 15 lines.
-- **Testing threshold** — TEST-001 line count threshold reduced from 50 to 20 lines.
-
-### Changed
-- **`isLikelyCLI()` scope** — Now detects CLI tool patterns across 5 ecosystems (Node.js, Go, Python, Rust, shell shebang) instead of only Node.js.
-
-### Tests
-- 1044 tests passing, 0 failures
-- 79/79 benchmark cases passing (66 vulnerability + 13 clean)
-
-## [3.23.11] — 2026-03-06
-
-### Added
-- **Security evaluator + judge** — New SEC-prefixed evaluator with 15 rules covering input validation, path traversal, uncontrolled file access, missing rate limiting, insecure randomness, information disclosure, and more. Registered as the 38th judge in the panel.
-- **AUTH: JWT decode-without-verify rule** — Detects `jwt.decode()` usage without corresponding `jwt.verify()`, catching the JWT "none algorithm" vulnerability. Severity: critical, confidence: 0.95.
-- **AUTH: Timing-unsafe comparison rule** — Detects `===`/`==` comparison of secrets, tokens, signatures, or hashes without `timingSafeEqual` or `constantTimeCompare`. Severity: high, confidence: 0.85.
-- **CONC: Go unsynchronized map detection** — Detects package-level `map` declarations accessed from HTTP handlers or goroutines without `sync.Mutex`/`sync.Map` protection. Severity: critical, confidence: 0.9.
-- **Auto-fix patches for Ruby, Rust, Kotlin, Swift, and Scala** — 40+ new patch rules covering command injection, SQL injection, path traversal, eval usage, deserialization, XSS, CSRF, and cryptographic weaknesses across five additional languages.
-- **Benchmark markdown report** — `formatBenchmarkMarkdown()` generates a publishable markdown report with grade badges, per-category breakdown, FP analysis, and missed-case details.
-- **Benchmark GitHub Actions workflow** — `.github/workflows/benchmark.yml` runs the benchmark suite on push/PR and publishes `benchmark-results.json` and `docs/benchmark-report.md` as artifacts.
-- **PR review: config and calibration support** — `judges review` now accepts `--config`, `--confidence`, and `--calibrate` flags. Loads `.judgesrc` cascading config, suppresses rules with high FP rates from feedback history, and applies feedback-driven confidence calibration.
-- **PR review: FP suppression tracking** — Review results now report `fpSuppressed` count for rules filtered by feedback-driven confidence thresholds.
-- **PR review workflow overhaul** — `.github/workflows/judges-pr-review.yml` upgraded to Node 22, adds build step, uses inline `judges review` command with `--approve`, `--calibrate`, and `--format json`, and posts structured summary comments.
-
-### Fixed
-- **AUTH hardcoded-secret false negatives** — URLs containing `example` (e.g., `api.example.com`) no longer trigger the non-production context suppression. URLs and domain names are stripped from context before the non-production pattern check.
-- **AUTH compound identifier matching** — Variables like `DB_PASSWORD`, `ADMIN_SECRET`, and `API_KEY` are now detected via a compound assignment pattern (`\w+[_-](password|secret|api_key|token|...)`).
-- **CYBER Java deserialization detection** — Broadened `UNSAFE_DESERIALIZATION.java` pattern to catch instance-style `ois.readObject()` calls and `new ObjectInputStream` construction, not just static `ObjectInputStream.readObject`.
-- **CYBER C# SQL injection detection** — SQL injection fallback now detects C# string interpolation (`$"SELECT ... {query} ..."`) in addition to JavaScript template literals.
-- **SEC input validation FP on Pydantic/Django** — `BaseModel`, `Field()`, `EmailStr`, `HttpUrl`, `Serializer`, `Form`, and `ModelForm` are now recognized as validation frameworks, preventing false positives on clean Python FastAPI code.
-- **SEC file access FP on compound identifiers** — Tightened user input matching from broad `/input|user/i` to require assignment/access operators (e.g., `input[`, `user.`), preventing false positives on config properties like `cfg.InputDir`.
-- **Cross-evaluator dedup prefix preservation** — Dedup now preserves up to 3 findings from unique non-winner prefixes per cluster, annotated with `_Primary finding: [winner ruleId]_`, ensuring diverse evaluator perspectives are retained.
-- **Tribunal "high findings" test** — Fixed test to check raw evaluations instead of capped output, since the 20-finding cap can exclude high-severity findings when many critical findings exist.
-
-### Changed
-- **Judge count** — Panel increased from 37 to 38 judges with the addition of the security judge.
-
-### Tests
-- 1044 tests passing
-
-### Benchmark
-- **P=97.8%, R=80.2%, F1=88.1%** (TP=89, FN=22, FP=2)
-
-## [3.23.10] — 2026-03-06
-
-### Fixed
-- **File classification ordering bug** — Path-based category checks (analysis-tool, CLI, VS Code extension) now run before content-based heuristics in `classifyFile()`. Previously, evaluator files were misclassified as "test" (due to `.test()` regex method calls) and command files as "server" (due to framework name mentions in string-literal data), causing ~550 false positive findings.
-- **Test detection false match on `.test()` regex calls** — The test-file heuristic no longer matches `.test()` regex method calls (e.g., `/pattern/.test(str)`). Uses a strip-and-recheck approach to exclude regex API usage from the test-framework signal.
-- **Server detection false match on string-literal framework names** — Files that reference Django, Spring, Express etc. inside template-literal code specimens or preset data are no longer misclassified as "server". Analysis-tool import checks now run before server signal detection.
-- **VS Code extension diagnostics provider** — Fixed diagnostic scope to avoid stale diagnostics on file close.
-- **ESLint warnings fixed** — Resolved useless-escape warnings in `taint-tracker.ts`, `structural-parser.ts`, `deep-review.ts`, `compliance.ts`, and `fix.ts`; fixed useless-assignment in `framework-safety.ts`.
-- **Duplicate string literals in errors.ts** — Extracted `"JUDGES_CONFIG_INVALID"`, `"JUDGES_EVALUATION_FAILED"`, and `"JUDGES_PARSE_FAILED"` into an `ErrorCode` constants object (MAINT-001).
-- **Missing `@returns` JSDoc tags** — Added `@returns` documentation to all exported functions in `cache.ts`, `disk-cache.ts`, and `fix-history.ts` (DOC-001/DOC-003).
-- **Long function refactoring** — Extracted `evictLru()` helper in `LRUCache`, and `loadIndexFile()`, `isEntryExpired()`, `readEntryFile()` standalone helpers in `DiskCache` to reduce average function length (MAINT-001).
-
-### Added
-- **`analysis-tool` file category** — New `FileCategory` for files in `src/evaluators/`, `src/commands/`, `scripts/`, `src/ast/`, and other analysis-tool directories. 28 inapplicable rule prefixes suppressed (SOV, CLOUD, A11Y, DB, etc.).
-- **`vscode-extension` file category** — New `FileCategory` for VS Code extension source. 19 inapplicable rule prefixes suppressed.
-- **Utility module FP heuristics** — Expanded utility-file suppression for rules that target deployed services (SCALE, CFG, COMPAT, PORTA, etc.) but not maintenance or documentation rules.
-- **Analysis-tool test specimen heuristic** — TEST-* rules suppressed on analysis-tool files when flagged patterns exist only inside template-literal code specimens (test fixtures).
-- **High-regex-count fallback** — Files with ≥20 regex literals automatically classified as analysis-tool (catches pattern-heavy files like `language-patterns.ts`).
-- **Self-evaluation build gate** — `npm run check` runs `tsc --noEmit && eslint && self-eval` ensuring zero judges findings across all 160 source files. `npm run self-eval` available standalone.
-- **`scripts/self-eval.ts`** — Walks `src/`, `vscode-extension/src/`, and `tests/`, runs `evaluateWithTribunal` on every `.ts` file, and exits non-zero if any findings remain.
-- **`scripts/debug-classify.ts`** — Diagnostic script to inspect file classification assignments.
-
-### Tests
-- 1037 tests passing
-
-## [3.23.9] — 2026-03-06
-
-### Changed
-- **Deep review is now the default** — `@judges`, `/review`, and `/deepreview` all run Layer 1 (pattern analysis) + Layer 2 (AI contextual review) by default.
-- **New `/shallowreview` command** — Added `/shallowreview` slash command for fast Layer 1 pattern-only analysis without the LLM deep review step.
-
-### Fixed
-- **Disk cache key includes `mustFixGate`** — The `evaluateWithTribunal` cache key now incorporates `mustFixGate` options, preventing stale cached results when toggling the must-fix gate on identical code. This caused CI failures when the must-fix gate test reused a cached result that lacked gate metadata.
-- **Added `.judges-cache/` to `.gitignore`** — Prevent disk cache artifacts from being committed.
-
-### Tests
-- All 2084 tests passing (1324 judges + 760 subsystems)
-
-## [3.23.8] — 2026-03-06
-
-### Added
-- **MCP batch parallelism** (`evaluateFilesBatch`) — Bounded-concurrency multi-file evaluation for MCP tool calls, processing files in parallel batches instead of sequentially.
-- **Disk-backed persistent cache** (`DiskCache`) — Content-addressable LRU cache with TTL and configurable max entries, persisted to `.judges-cache/` for cross-run performance. Cache keys now incorporate evaluation options (AST, confidence, severity, rules, weights) for correctness.
-- **Incremental `--changed-only` flag** — Evaluate only files changed since the last git commit, using `git diff --name-only` for fast CI feedback loops.
-- **GitHub Actions annotation formatter** (`--format github-actions`) — Emit `::error`, `::warning`, and `::notice` annotations for native GitHub Actions integration.
-- **Confidence explanations** (`estimateFindingConfidenceWithBasis`) — Each finding now includes an `evidenceBasis` string explaining why the confidence score was assigned (line-precise signal, AST match, pattern heuristic, etc.).
-- **Per-path config overrides** — `.judgesrc.json` `overrides` array supports glob-matched per-path `minSeverity`, `disabledRules`, and `disabledJudges` settings via `applyOverridesForFile()`.
-- **`failOnScoreBelow` config** — Set a minimum score threshold in config; CI exits non-zero when the overall score falls below.
-- **Weighted judge scoring** — `judgeWeights` config field allows per-judge influence weighting on the aggregate score.
-- **LSP server scaffold** (`judges lsp --stdio`) — JSON-RPC/LSP server for real-time diagnostics in editors, exposed via `runLsp()`.
-- **Score trend CLI command** (`judges trend`) — Track and display evaluation score trends over time.
-- **Migration guides** (`docs/migration-guides.md`) — Step-by-step guides for migrating from ESLint, SonarQube, Semgrep, and CodeQL.
-- **Block-level selective autofix** — `judges fix` now supports `--rule`, `--severity`, and `--lines` flags for targeted patching.
-- **MCP `evaluate_file` tool** — Single-file evaluation tool for MCP integrations via `register-evaluation.ts`.
-- **Plugin scaffolding** (`judges scaffold-plugin`) — Generate a starter plugin directory with evaluator template, test harness, and `package.json`.
-
-### Fixed
-- **Fix README patch count** — Updated from 53 to 114 to reflect actual patch coverage.
-
-### Tests
-- 300+ new test lines covering all P0–P2 features
-- All 2084 tests passing (1324 judges + 760 subsystems)
-
-## [3.23.7] — 2026-03-05
-
-### Added
-- **`judges review` command** — Post inline review comments on GitHub PRs directly from the CLI. Supports `--pr`, `--repo`, `--approve`, `--dry-run`, `--min-severity`, `--max-comments`, and `--format` flags. Authenticates via `GITHUB_TOKEN` env var or `gh` CLI.
-- **`judges tune` command** — Analyze a project directory and generate an optimal `.judgesrc.json` configuration. Detects frameworks, languages, and file structure to suggest presets, disabled rules, and severity overrides. Supports `--dir`, `--apply`, `--max-files`, and `--verbose` flags.
-- **Finding lifecycle tracking** (`src/finding-lifecycle.ts`) — Track individual findings across evaluation runs with fingerprinting, trend detection (improving/stable/degrading), and stats. Supports in-memory and file-backed (`.judges-findings.json`) stores.
-- **8 framework-aware presets** — `react`, `express`, `fastapi`, `django`, `spring-boot`, `rails`, `nextjs`, `terraform` — each disables irrelevant evaluators for that framework.
-- **~15 new autofix patches** — Python (`eval→ast.literal_eval`, `verify=False→True`, `shell=True→False`, `open` without encoding), Go (`log.Fatal→http.Error`, defer Close error check), Rust (`panic!→Result match`, `.clone()→borrow`), Java (`System.out.println→Logger`, `Statement→PreparedStatement`), C# (`ExecuteSqlRaw→ExecuteSqlInterpolated`, `Console.WriteLine→ILogger`).
-- **10 new clean-code FP benchmark cases** — FastAPI, Go handler, Rust handler, Java Spring, C# ASP.NET, TS utility lib, hardened Terraform, Python data script, Go CLI tool, React component.
-- **Enhanced diff mode** — `judges diff` now loads full file content from disk when the file path exists, improving patch context accuracy.
-
-### Tests
-- 38 new tests added (framework presets, finding lifecycle, new patches, review/tune CLI parsing)
-- All 2051 tests passing (1037 judges + 727 subsystems + 217 negative + 70 extension-logic)
-
-## [3.23.6] — 2026-03-05
-
-### Fixed — False Positive Reductions
-
-- **Analysis-code & CLI guards** — Added `isLikelyAnalysisCode()` and `isLikelyCLI()` heuristics to `shared.ts` and applied guards across 21+ evaluators. Files that contain analysis/evaluator logic (≥8 `.test()` calls, rule-definition patterns) or CLI scaffolding (argument-parser imports, `yargs`/`commander` patterns) are now suppressed from application-code rules that would otherwise misfire.
-- **IaC template guards (Bicep/Terraform)** — Added `isIaCTemplate` early returns to 5 evaluators (`cloud-readiness`, `data-security`, `database`, `portability`, `maintainability`) so application-code rules no longer fire on declarative infrastructure files. Raised `maintainability` file-length threshold from 300→600 for IaC templates and suppressed duplicate-string detection for IaC.
-- **IAC-001 hardcoded-secret refinement** — Added `looksLikeIaCSecretValue()` post-filter to `iac-security.ts` so boolean config values (`'true'`/`'false'`), PascalCase enum identifiers, and known IaC configuration constants are no longer flagged as hardcoded secrets.
-
-### Tests
-- 217 new negative tests added
-- All 1943 tests passing (1037 judges + 689 subsystems + 217 negative)
-
-## [3.23.5] — 2026-03-05
-
-### Security
-- **Dependabot: Update hono 4.12.3 → 4.12.5** — Resolves CVE-2026-29045 (arbitrary file access via serveStatic), CVE-2026-29085 (SSE control field injection via CR/LF), CVE-2026-29086 (cookie attribute injection via unsanitized domain/path). Transitive dependency of `@modelcontextprotocol/sdk`.
-- **Dependabot: Update @hono/node-server 1.19.9 → 1.19.11** — Resolves CVE-2026-29087 (authorization bypass for protected static paths via encoded slashes). Transitive dependency of `@modelcontextprotocol/sdk`.
-
-### Fixed
-- **CodeQL: Polynomial ReDoS in suppression/file-ignore regexes** (`src/evaluators/index.ts`) — Replaced `[\w*,\s-]+?` with `[\w*,-]+(?:\s+(?!--)[\w*,-]+)*` to eliminate whitespace overlap with subsequent `\s+` groups, preventing catastrophic backtracking on crafted input.
-- **CodeQL: Polynomial ReDoS in singletonRe** (`src/evaluators/project.ts`) — Replaced `[^=]*` with `[^=\s]+(?:\s+[^=\s]+)*` to prevent overlap between optional type annotation and `\s*=`.
-- **CodeQL: Polynomial ReDoS in prompt stripping** (`src/tools/prompts.ts`) — Replaced regex-based `.replace()` with `split/filter/join` string-based line removal, eliminating ReDoS risk entirely.
-- **CodeQL: Incomplete string escaping in globToRegex** (`src/cli.ts`) — Added `-` to the regex escape character class so literal hyphens in glob patterns are properly escaped.
-
-### Tests
-- All 1726 tests passing (1037 judges + 689 subsystems)
-
-## [3.23.4] — 2025-07-26
-
-### Fixed — Self-Review False Positive Reductions (3 root causes, batch 2)
-
-Continued self-review of all 43 evaluator files. Groups A–E (27 files) scored 100/100 with only DOC-001. Group F (3 orchestrator files: `index.ts`, `project.ts`, `v2.ts`) scored 97–99/100, revealing 3 new FP root causes:
-
-- **DATA-001: Compound identifiers ending in `iv` no longer flagged as hardcoded encryption IVs** — Added `\b` word boundaries around the short token `iv` (and `nonce`) in the `data-security.ts` encryption-key regex. Property names like `LOGPRIV: "Logging Privacy"` where `IV` appears at the end of a compound identifier previously matched `iv\s*[:=]\s*"..."`. Standalone `iv = "..."` assignments are still correctly flagged.
-- **DB-002: In-memory collection methods no longer trigger "mutations without transaction"** — Added a database-context signal check to `database.ts`. The `hasMutations` regex matches generic method names (`.delete()`, `.save()`, `.create()`) that are common on `Map`, `Set`, and other non-database objects. The rule now requires at least one database-related import or usage pattern (e.g., `pg`, `prisma`, `sequelize`, SQL query strings) before firing, preventing false positives on `stack.delete(node)` in DFS traversal code and `cache.delete(key)` in Map-based caches.
-- **SOV-001: Compound identifiers and multi-line import continuations no longer trigger "data export path"** — Enhanced `data-sovereignty.ts` export-keyword scanner with two new filters: (1) skip lines that are multi-line import continuations (bare identifiers like `UncertaintyReportV2,`), and (2) skip lines where trigger words (`report`, `export`, `download`, etc.) appear only embedded inside compound identifiers (e.g., `UncertaintyReportV2`, `DownloadManager`). Standalone usages like `export(data)` and `download(file)` are still correctly flagged.
-
-### Tests
-- 11 new tests covering all 3 FP root causes (positive and negative cases)
-- 1037 judges tests passing, 689 subsystems tests passing (1726 total)
-
-## [3.23.3] — 2025-07-26
-
-### Fixed — Self-Review False Positive Reductions (3 root causes)
-
-Ran judges against its own evaluator source code to identify and fix FP root causes:
-
-- **CONC-001: Local `let` declarations no longer flagged as shared mutable state** — Added indentation-based scope check in `concurrency.ts`. Only module-level (column 0) `let`/`var` declarations are now considered potentially shared mutable state. Variables declared inside function bodies (indented code) are local by definition and no longer trigger false positives when the file contains `async`/`await` keywords in strings or later code.
-- **CYBER-001: Auth keywords in analysis/evaluator code no longer trigger rate-limiting findings** — Added `isLikelyAnalysisCode` guard to `cybersecurity.ts` auth endpoint rate-limiting rule of file. Files with ≥8 `.test()` calls (indicating code-analysis or evaluator logic) are now suppressed, matching the existing pattern in `authentication.ts`.
-- **ERR-003: `throw` patterns inside regex literals and string values no longer flagged** — Enhanced `error-handling.ts` throw-string detection with multi-layer filtering: skips regex literal lines, string-literal-only lines, lines with regex method calls containing throw patterns, and lines where `throw` appears inside quoted string content (e.g., `suggestedFix: "Replace throw 'msg' with throw new Error('msg')"`).
-
-### Tests
-- 6 new tests covering all 3 FP root causes (positive and negative cases)
-- 1026 judges tests passing, 689 subsystems tests passing (1715 total)
-
-## [3.23.2] — 2026-03-04
-
-### Fixed — False Positive Reductions (9 categories)
-- **COST-001 / PERF-001: Sequential Python loops no longer flagged as nested** — Fixed indent-stack algorithm to pop loop scopes on all code lines (not just loop lines), so that `try/except`, `if`, and `with` blocks correctly close preceding loop scopes. Sequential loops inside try/except blocks are no longer misidentified as O(n²).
-- **SWDEV-001-post / MAINT-001-post: Nesting depth threshold raised to 5+ levels** — Changed deep-nesting threshold from 16 spaces (4 levels) to 20 spaces (5 levels), matching `structural-parser.ts`. Python patterns like `async def → try/except → for → if` naturally need 4 levels and should not be flagged.
-- **SWDEV-002-post: `except Exception:` no longer flagged as bare except** — Removed `except Exception:` from `GENERIC_CATCH.python` pattern. `except Exception:` correctly excludes `BaseException` subclasses (KeyboardInterrupt, SystemExit) and is the recommended Python pattern for facade layers.
-- **SOV-001: Docstring body lines no longer trigger sovereignty findings** — Added multi-line Python string tracking (`"""`/`'''`) to the data-sovereignty export keyword scanner. Keywords like "export", "report", "analytics" inside module docstrings are no longer mistaken for real data export paths.
-- **DOC-001: Multi-line Python function signatures now detected** — Extended docstring lookahead to walk past multi-line function signatures (parameters spanning multiple lines) before searching for body docstrings. Previously, functions with signatures spanning 5+ lines would be falsely flagged as undocumented.
-- **MAINT-002-post: Format template strings excluded from duplicate detection** — Duplicate string detection now skips strings containing format placeholders (`{}`, `%s`, `${}`), and strings that are purely whitespace. Template strings repeated in different contexts are no longer flagged.
-- **STRUCT-006: `TYPE_CHECKING` imports excluded from weak type detection** — `detectWeakTypes()` now skips lines containing `TYPE_CHECKING` and all lines inside `if TYPE_CHECKING:` blocks in Python. Static-analysis-only imports are no longer flagged as weak/dynamic types.
-
-### Tests
-- 14 new tests covering all 9 FP categories (both positive and negative cases)
-- 1020 judges tests passing, 689 subsystems tests passing (1709 total)
-
-## [3.23.1] — 2026-03-04
-
-### Fixed
-- **TypeScript type errors** — Fixed 5 compilation errors that caused CI failure on v3.23.0:
-  - `doctor.ts`: Referenced non-existent `judges` and `threshold` properties on `JudgesConfig`; now uses `disabledJudges` and `minSeverity`
-  - `rule-metrics.ts`: Imported `JudgeDefinition` from `evaluators/index.js` which didn't re-export it; now imports from `types.js`
-  - `snapshot.ts`: `Record<Severity, number>` missing `info` key; added `info: 0` initializer
-  - `dedup.ts`: Referenced non-existent `filePath` property on `Finding` type in `findingDiffKey()`
-- **Test fix** — Updated finding-diff test that relied on invalid `Finding.filePath` property to use the `diffFindings()` `filePath` parameter instead
-
-### Tests
-- 1006 judges tests passing, 689 subsystems tests passing (1695 total)
-
-## [3.23.0] — 2026-03-05
-
-### Added — P0: Trust & Accuracy Foundation
-- **Hard/subtle benchmark cases** — 13 new benchmark cases targeting subtle vulnerabilities (prototype pollution, timing attacks, ReDoS, SSRF through URL parsing, null-byte injection, etc.) with `DifficultyResult` interface and strict metrics; `--save` CLI flag for benchmark persistence
-- **Autofix patch expansion** — 33 new patch rules (71→104 total): 25 single-line rules covering CSRF, prototype pollution, ReDoS, path traversal, insecure cookies, etc; 8 multi-line patch rules for complex fixes; 27 new patch tests
-- **V2 baseline with fingerprinting** — Complete `baseline.ts` rewrite (142→~510 lines) with V2 format: per-file fingerprinted findings, `baselineVersion: 2`, `fingerprintBaseline()` with line-context hashing, `diffBaseline()` showing new/fixed/carried findings with severity summaries; 17 new tests
-
-### Added — P1: Developer Experience & Adoption
-- **Sample report generation** — `examples/generate-reports.ts` script producing Markdown, JSON, and SARIF reports; 3 sample reports in `reports/`
-- **PR comment dedup & Check Runs** — Enhanced `action.yml` with deterministic comment fingerprinting to prevent duplicate PR comments, Check Runs API integration via `@octokit/rest`; 6 new tests
-- **Plugin loading infrastructure** — `loadPluginJudges()`, `validatePluginSpecifiers()`, `isValidJudgeDefinition()` in config.ts; `JudgesConfig` expanded with `preset`, `failOnFindings`, `baseline`, `format`, `plugins` fields; `mergeConfigs()` and `resolveJudgeSet()` plugin-aware; 30 new tests
-- **Suppression audit trail** — Full suppression rewrite with `judges-ignore-block`/`judges-end-block` block scope, reason capture, `applyInlineSuppressionsWithAudit()` returning `SuppressionResult` with `SuppressionRecord[]` audit trail; 14 new tests
-- **Team feedback aggregation** — `contributor` field on `FeedbackEntry`, `TeamFeedbackStats`/`RuleTeamStats` interfaces, `mergeFeedbackStores()`, `computeTeamFeedbackStats()`, `formatTeamStatsOutput()`; 16 new tests
-
-### Added — P2: Depth & Precision
-- **Rule test assertion framework** — `RuleTestCase`/`RuleTestResult`/`RuleTestSuiteResult` types, `runRuleTests()`, `validateRuleTestSuite()`, `formatRuleTestResults()` in rule.ts; 13 new tests
-- **Calibration pipeline integration** — `calibrate?: boolean | CalibrationOptions` on `EvaluationOptions`, wired `loadCalibrationProfile()` and `calibrateFindings()` into `evaluateWithTribunal()`; 5 new tests
-- **Finding diff between runs** — `FindingDiff` interface, `findingDiffKey()`, `diffFindings()` (classifies new/fixed/recurring), `formatFindingDiff()` in dedup.ts; 11 new tests
-- **`judges doctor` command** — Full diagnostic healthcheck: 7 checks (Node version, config file, judges loaded, plugins, feedback store, baseline file, presets), `runDoctorChecks()` runner, `formatDoctorReport()` formatter, `--json` CLI support; 12 new tests
-
-### Added — P3: Ecosystem & Integration
-- **Language coverage report** — `detectFileLanguage()`, `computeLanguageCoverage()`, `formatCoverageReport()` in coverage.ts; covers 16 languages with judge availability mapping; 11 new tests
-- **Finding snapshot & trend tracking** — `SnapshotStore` with versioned persistence, `recordSnapshot()` from findings, `computeTrend()` with improving/stable/regressing detection (10% threshold comparing recent vs early runs), `formatTrendReport()` with delta history; 12 new tests
-- **Rule hit metrics** — `computeRuleHitMetrics()` tracking active/silent rules, severity breakdown per rule, noisy-rule ranking with percentages, `findJudgeForRule()` prefix matching, `formatRuleHitReport()`; 11 new tests
-- **Project auto-detection for init wizard** — `detectLanguages()`, `detectFrameworksFromFiles()` (package.json + requirements.txt + file indicators), `classifyProjectType()` (9 project types), `detectCI()`, `detectMonorepo()`, `recommendPreset()` with confidence scoring, `formatProjectSummary()`, `formatRecommendation()`; 22 new tests
-
-### Tests
-- 1982 tests passing (0 failures)
-- 689 subsystem tests (up from 610), 45 new tests this release
-- New test sections: Finding Diff (§27), Doctor Diagnostics (§28), Language Coverage (§29), Finding Snapshot & Trend (§30), Rule Hit Metrics (§31), Project Auto-Detection (§32)
-
-## [3.22.1] — 2026-03-04
-
-### Fixed
-- **JSON Schema test for preset composability** — Updated `judgesrc.schema.json` test to reflect intentional removal of preset `enum` constraint (now free-form string for comma-separated preset composition); fixes CI failure on Node 20 + 22 matrix
-
-### Tests
-- 1006 tests passing (0 failures)
-
-## [3.22.0] — 2026-03-04
-
-### Added — P0: Trust & Accuracy Foundation
-- **V2 prefix mapping completeness** — Added 4 missing rule prefix mappings (`RES`, `SEC`, `IAC`, `AIGEN`) to `mapSpecialty()` and `mapJudgeIdFromRule()` in v2.ts, ensuring all 37 judges route correctly in V2 policy profiles
-- **Cross-file deduplication** — New `crossFileDedup()` function in dedup.ts detects project-wide duplicate findings across files using topic patterns, severity matching, and configurable tightness; integrated into project.ts evaluation pipeline
-- **Benchmark expansion** — Expanded benchmark suite from 17 to ~47 test cases covering all major vulnerability categories with balanced true-positive / false-positive samples; version now auto-read from package.json
-- **Test coverage expansion** — 481 subsystem tests (up from ~400), covering scoring, dedup, config, CLI, presets, benchmark gate, cascading config, CSV formatter, and streaming API
-
-### Added — P1: Developer Experience & Adoption
-- **CLI `--exclude` / `--include` / `--maxFiles` flags** — File filtering via glob patterns and file-count limits; integrated into `action.yml` inputs and `.judgesrc` schema; `globToRegex()`, `matchesGlob()`, `collectFiles()` utilities
-- **Preset composability** — `composePresets()` merges multiple presets with intersection for disabledJudges, union for disabledRules, and most-permissive minSeverity; CLI accepts comma-separated `--preset security,quick`
-- **API reference & plugin guide** — New `docs/api-reference.md` (comprehensive API surface) and `docs/plugin-guide.md` (custom evaluator/formatter development guide)
-
-### Added — P2: Depth & Precision
-- **Confidence tuning** — Enhanced `estimateFindingConfidence` with provenance-based boosts (AST +0.15, taint-flow +0.18, regex +0.08), domain-severity alignment (+0.04 for security-critical), and 3-tier noise caps: Tier 1 subjective judges (COMP/ETHICS/SOV/COST/DOC → 0.82), Tier 2 context-dependent (API/CONC/DB/DEPS/LOGPRIV/OBS/PERF → 0.88), Tier 3 mechanical (CACHE/CFG/COMPAT/MAINT/SWDEV/TEST → 0.92)
-- **Dedup topic expansion** — Expanded `DEDUP_TOPIC_PATTERNS` from ~27 to ~52 patterns adding auth/session, concurrency, database, logging/privacy, config/infra, dependency, resource management, and error handling domains
-- **VS Code extension depth** — 4 new settings: `judges.exclude`, `judges.include`, `judges.maxFiles`, `judges.confidenceTier` (essential/important/supplementary); confidence tier filtering in diagnostics and workspace reviews; configurable workspace eval limits
-- **CI benchmark gate** — `--gate` CLI flag with `--min-f1`, `--min-precision`, `--min-recall`, `--min-detection-rate`, `--baseline` options; `benchmarkGate()` API function with regression detection (1% tolerance); `BenchmarkGateOptions` / `BenchmarkGateResult` types
-
-### Added — P3: Ecosystem & Integration
-- **Cascading config** — Directory-level `.judgesrc` override support: `discoverCascadingConfigs()` walks up from file to project root finding configs, `mergeConfigs()` unions arrays and deep-merges ruleOverrides, `loadCascadingConfig()` convenience wrapper; enables monorepo per-package configuration
-- **Streaming / async API** — `evaluateFilesStream()` async generator yields results per file for progress UIs; `evaluateFilesBatch()` with bounded concurrency (default 4 workers) and `onProgress` callback; new `FileInput` / `FileEvaluationResult` types
-- **MCP tool expansion** — 3 new MCP tools (13 → 16 total): `benchmark_gate` (run benchmark with quality thresholds), `compare_benchmarks` (diff two benchmark runs), `evaluate_batch` (evaluate multiple files in one call with per-file results table)
-- **CSV formatter** — New `src/formatters/csv.ts` with `verdictToCsvRows()`, `verdictsToCsv()`, `findingsToCsv()` for spreadsheet / data-pipeline ingestion; header: `file,ruleId,severity,confidence,title,lines,reference`
-
-### Changed
-- Benchmark report now reads version dynamically from package.json instead of hardcoded string
-- `evaluateWithTribunal` MCP tool handlers use correct call signature (`code, language, context?, options?`)
-
-### Tests
-- 481 subsystem tests passing (102 suites), covering all new features
-- 20 new tests for P3: cascading config merge (10), CSV formatter (5), streaming/batch API (5)
-
-## [3.21.0] — 2026-03-05
-
-### Added — P0: GitHub Action CI/CD
-- **PR inline review comments** — New `pr-review` input in `action.yml` posts findings as inline PR review comments with severity badges, auto-fix hints, and judge attribution
-- **Diff-only mode** — New `diff-only` input restricts analysis to changed files using `git diff`, dramatically reducing CI noise on large repos
-- **Baseline filtering** — New `baseline-file` input suppresses known findings via a baseline JSON, surfacing only new issues in PRs
-- **Improved step summary** — GitHub Actions summary now includes findings table, score badge, and must-fix gate status
-
-### Added — P1: Core Engine Enhancements
-- **AST context in more evaluators** — `AnalyzeContext` interface pipes tree-sitter AST data into cybersecurity (scope-aware taint), performance (async/complexity detection), and authentication (decorator/import awareness) evaluators
-- **`fix_code` MCP tool** — New tool evaluates code and auto-applies all available patches, returning fixed code + summary of remaining findings
-- **Multi-language framework evaluators** — Extended `framework-safety.ts` from JS/TS-only to 8 frameworks: Django (6 rules), Flask (4), FastAPI (1), Spring Boot (6), ASP.NET Core (6), Go/Gin/Echo/Fiber (5)
-
-### Added — P2: Depth & Tooling
-- **20+ new auto-fix patches** — Added patches for Python (7), Go (2), Java (5), C# (4), Rust (2) covering SQL injection, command injection, weak hashing, empty catch, and more
-- **VS Code findings panel** — TreeView-based panel with sort-by-severity/judge, filter controls, go-to-line navigation, and 7 new commands (`judges.showFindingsPanel`, `judges.sortBySeverity`, etc.)
-- **Cross-file type/state tracking** — Three new project-level detectors: `detectSharedMutableState()`, `detectTypeSafetyGaps()`, `detectScatteredEnvAccess()` in `project.ts`
-- **Taint tracker language depth** — Expanded from 5 to 9 language-specific pattern sets with `LanguagePatternSet` interface; each set defines sources, sinks, sanitizers, assign patterns, and guard conditions
-
-### Added — P3: Breadth & Polish
-- **PHP/Ruby/Kotlin/Swift language support** — Added 4 new languages to `LangFamily`, expanded all ~35 pattern constants in `language-patterns.ts`, added 4 complete taint tracker pattern sets (PHP: 7 sources/11 sinks/11 sanitizers, Ruby: 9/11/10, Kotlin: 9/8/8, Swift: 8/9/6)
-- **Performance & snapshot tests** — 3 new test suites: performance budgets (tribunal <5s, per-judge <500ms, evaluateDiff <3s, large-block <15s), rule coverage stability (≥30 judges, 100-600 findings, required families, severity distribution), multi-language pattern coverage (8 tests for PHP/Ruby/Kotlin/Swift)
-- **Framework version awareness** — `detectFrameworkVersions()` extracts versions from 14 manifest/config patterns; `getVersionConfidenceAdjustment()` applies version-specific confidence rules for Django 4+, Spring 3+, Next.js 13+/14+, Express 5+, Rails 6+/7+, Laravel 9+, ASP.NET 8+; integrated into `applyFrameworkAwareness()`
-- **MCP workspace & streaming tools** — 3 new MCP tools: `list_files` (recursive directory listing with skip-dirs), `read_file` (content reading with line-range slicing), `evaluate_with_progress` (progressive judge-by-judge reporting with count updates)
-
-### Changed
-- **MCP tool count** — 10 → 13 tools registered in `server.json`
-- **`applyFrameworkAwareness()` rewritten** — Now combines framework mitigation with version-aware confidence adjustments and stacked provenance notes
-- **`register.ts` modular architecture** — Now orchestrates 4 registration modules: evaluation, workflow, fix, workspace
-
-### Tests
-- 19 new performance/snapshot/multi-language tests in `judges.test.ts`
-- 19 new framework version awareness tests in `subsystems.test.ts`
-- 1006 tests in judges.test.ts, 392 tests in subsystems.test.ts — all passing
-
-## [3.20.14] — 2026-03-04
-
-### Added
-- **Three new FP heuristics (H33–H35)** — Expanded the false-positive filter from 32 to 35 deterministic heuristics:
-  - **H33: Destructuring variable extraction** — Suppresses hardcoded-credential findings when the security keyword is a destructured variable name (`const { password } = req.body`), recognizing the code extracts a named field from runtime data
-  - **H34: Dictionary/map key access** — Suppresses hardcoded-credential findings when the keyword is a dictionary key being accessed (`data["password"]`, `request.form.get("token")`), not a hardcoded value; excludes LOGPRIV and exposure-related findings
-  - **H35: CLI argument/option definitions** — Suppresses findings when the keyword defines a CLI parameter in argparse, click, commander.js, or yargs (`parser.add_argument("--password")`, `.option("--token")`)
-- **Expanded H6 keyword-in-identifier patterns** — Significantly broadened compound-identifier recognition for all five security keywords:
-  - `password`: ~25 new suffixes (manager, service, handler, helper, criteria, complexity, expiry, generator, mask, etc.) and ~16 new prefixes (set, get, save, store, update, change, manage, generate, etc.)
-  - `secret`: ~14 new suffixes (holder, service, handler, helper, resolver, loader, fetcher, etc.) and ~20 new prefixes (get, set, read, fetch, load, resolve, lookup, rotate, etc.)
-  - `token`: ~18 new suffixes (manager, service, handler, provider, factory, builder, cache, parser, etc.) and ~26 new prefixes (get, set, create, generate, fetch, store, validate, revoke, etc.)
-  - `delete`: Refined to add safe lifecycle prefixes (soft, hard, mark, pre, post, async, schedule) and safe naming suffixes (scheduled, pending, mark) while deliberately excluding operation-target suffixes (many, all, records) that represent actual data operations
-  - `exec`: ~13 new suffixes (command, args, timeout, callback, handler, etc.) and ~12 new prefixes (pre, post, async, remote, batch, parallel, etc.)
-- **Three new safe idiom patterns (H7)** — Added vault/secrets-manager SDK calls, hash/digest function calls, and UI label/placeholder strings as recognized safe contexts
-
-### Tests
-- Added 29 new FP heuristic tests covering all new and expanded heuristics with both FP-suppression and TP-retention validation
-- 1666 tests, 0 failures
-
-## [3.20.13] — 2026-03-04
-
-### Fixed
-- **Documentation accuracy audit** — Comprehensive review and correction of all documentation claims against the actual codebase:
-  - Updated test badge count (1557 → 1666)
-  - Updated judge dimension counts throughout (35 → 37) and architecture diagram heuristic count (33 → 36)
-  - Added missing judges (`iac-security`, `false-positive-review`) to Judge IDs list, Judge Panel table, and MCP Prompts table
-  - Updated evaluator and judge file counts (35 → 37)
-  - Added 4 missing package exports to exports table (`./diagnostics`, `./plugins`, `./fingerprint`, `./comparison`)
-  - Added 10 missing CLI commands to Scripts table (`feedback`, `benchmark`, `rule`, `pack`, `config`, `compare`, `list`)
-  - Expanded project structure with ~20 missing files and directories (AST files, formatters, patches, tools, tests, scripts)
-  - Fixed incorrect script filename (`analyze-report-findings.ts` → `debug-fp.ts`)
-- **VS Code extension README** — Replaced 3 hardcoded GPT-4o model references with vendor-neutral phrasing ("available language model" / "AI contextual review"), fixed "right-click a file" → "right-click in the editor", updated auto-fix patch count (47+ → 53)
-
-### Tests
-- 1666 tests, 0 failures
-
-## [3.20.12] — 2026-03-03
-
-### Changed
-- **VS Code extension — Layer 2 progress feedback** — Replaced silent full-response buffering with two-phase streaming and granular progress indicators so users see real-time status during the AI deep review instead of a blank screen for 30–60 seconds:
-  - **Chat participant (`/deepreview`)**: Added progress messages at each stage (preparing prompt, selecting model, sending request, AI analyzing, streaming results); LLM response now streams incrementally to the chat after the first 500 chars clear the content-policy refusal check — user sees text appearing in real-time instead of a single wall of text at the end
-  - **Command palette (`Judges: Deep Review`)**: `withProgress` notification now shows phase-specific messages via a new `onProgress` callback passed into `deepReview()` — Layer 1 analysis, model selection, request sending, AI analysis, retry status all reported in the notification area
-  - **Retry path**: Content-policy retry also uses two-phase streaming and granular progress instead of silent buffering
-
-### Tests
-- 1666 tests, 0 failures
-
-## [3.20.11] — 2026-03-03
-
-### Fixed
-- **False positive reduction — 5 new Bicep/IaC-specific heuristics (H28–H32)** — Eliminates 5 high-confidence false positive patterns specific to Infrastructure-as-Code templates (Bicep, ARM, Terraform):
-  - **H28 — IaC compile-time property resolution**: Suppresses REL null-check findings (e.g. "deep property access without null checks") on IaC templates where resource property references like `vnet.properties.subnets[0].id` are resolved at deploy time, not at runtime — null checks and optional chaining are inapplicable
-  - **H29 — IaC domain-convention numbers**: Suppresses MAINT magic-number findings for numeric values that are IaC domain conventions (NSG priorities 100–4096, port numbers, CIDR prefix lengths, retention periods like 365 days)
-  - **H30 — Schema-mandated nesting depth**: Suppresses MAINT deep-nesting findings on IaC templates where hierarchical depth (resource → properties → subnets[] → properties → addressPrefix) is mandated by the ARM/Terraform resource schema and cannot be flattened
-  - **H31 — IaC schema enum values**: Suppresses MAINT duplicate-string findings for schema-constrained enum values like `'Tcp'`, `'Allow'`, `'Deny'`, `'Inbound'`, `'Outbound'` that must be repeated per ARM/Terraform schema requirements
-  - **H32 — Azure Bastion documented-requirement**: Suppresses IAC Internet-HTTPS findings on Bastion NSG rules that require inbound HTTPS (443) from `'Internet'` per Microsoft documentation — only when a Bastion subnet is present AND compensating controls (Conditional Access, MFA, audit logging) are documented in comments
-
-### Tests
-- 9 new tests in `IaC/Bicep-specific FP heuristics` describe block: H28 REL-001 suppress + non-IaC keep, H29 MAINT-001 magic numbers, H30 MAINT-002 deep nesting on Bicep + Terraform, H31 MAINT-003 duplicate strings, H32 IAC-004 Bastion with/without compensating controls, MAINT on non-IaC keep
-- 1666 tests, 0 failures
-
-## [3.20.10] — 2026-03-03
-
-### Fixed
-- **Security — 6 polynomial-ReDoS vulnerabilities fixed (CodeQL `js/polynomial-redos`)** — All 6 open code-scanning alerts resolved:
-  - **`src/tools/prompts.ts`**: Bounded negated character classes in the rule-ID stripping regex with `\n` anchors (`[^"]*` → `[^"\n]*`, `[^)]*` → `[^)\n]*`) to prevent cross-line polynomial backtracking
-  - **`src/evaluators/false-positive-review.ts`** (5 alerts): Replaced `word1.*word2` regex patterns in `finding.title` checks with equivalent `.includes()` string method calls that eliminate polynomial backtracking entirely — affects heuristics for scalability/lock detection, resilience/retry detection, i18n hardcoded-string detection, performance nested-loop detection, and sovereignty data-egress detection. Identical matching semantics preserved.
-
-### Tests
-- 1657 tests, 0 failures
-
-## [3.20.9] — 2026-03-03
-
-### Changed
-- **Token usage optimisation — MCP full-tribunal prompt** — Refactored the `full-tribunal` MCP prompt to deduplicate shared behavioural directives (adversarial mandate, precision mandate) that were previously repeated 37× — once per judge. Shared directives are now stated once in a "Universal Evaluation Directives" preamble. Per-judge sections include only unique evaluation criteria, domain-specific rules, and FP-avoidance guidance. Boilerplate lines (persona introductions, rule-prefix assignment templates, score templates) are stripped by the new `getCondensedCriteria()` helper. **~40 000 chars (~10 000 tokens) saved per full-tribunal invocation — approximately 30% reduction — with zero impact on TP detection quality.** All evaluation criteria, domain-specific rules, and FP-avoidance sections are fully preserved.
-- **MCP per-judge prompts — evaluation criteria now included** — Per-judge MCP prompts previously sent only a generic "Please evaluate" message without the judge's evaluation criteria, making LLM-powered single-judge reviews less effective. Each per-judge prompt now includes the judge's full `systemPrompt` and precision mandate, significantly improving TP detection quality for single-judge deep reviews.
-- **New exported utility `getCondensedCriteria()`** — Extracts only the unique evaluation criteria from a judge's `systemPrompt`, stripping persona introductions, adversarial mandates, and boilerplate rule/score templates. Available via the public API for custom integrations that need token-efficient prompt construction.
-
-### Tests
-- 11 new tests in `getCondensedCriteria — Token Optimisation` describe block: persona intro stripping, adversarial mandate stripping, boilerplate rule/score line stripping, FP avoidance retention, real judge criteria retention (cybersecurity, data-sovereignty), measurable savings across all judges (>25% per-judge, ≥20% tribunal-level), non-empty output for every judge, persona stripping for all judges, adversarial mandate stripping for all judges, simulated tribunal prompt savings measurement
-- 1657 tests, 0 failures
-
-## [3.20.8] — 2026-03-03
-
-### Fixed
-- **False positive reduction — 3 new heuristics (H25–H27) + 1 new safe idiom entry + extended identifier patterns** — Continued proactive FP analysis targeting config/schema definitions, function call assignments, string comparison dispatch, and broadened env-var credential suppression:
-  - **H25**: Config/schema object keys with non-credential values — findings suppressed when security keywords (`password`, `secret`, `token`, `credential`) appear as object/dict keys followed by boolean (`true`/`false`), null (`null`/`undefined`/`None`), config keywords (`required`/`optional`), nested schema objects (`{ type: ... }`), or ORM field definitions (`Column(...)`, `Field(...)`, `models.CharField(...)`)
-  - **H26**: Assignment from function call / config lookup — findings about "hardcoded" or "plaintext" credentials suppressed when the value is assigned from a function call (`getConfig(...)`, `vault.read(...)`) or env-var access (`process.env`, `os.environ`), not from a literal string; excludes request/input object bracket access (`request.form[...]`)
-  - **H27**: String comparison / switch-case dispatch — findings suppressed when security keywords appear as string values in equality comparisons (`=== "password"`, `== "token"`), switch-case labels (`case "secret":`), inclusion checks (`.includes("password")`), or Python `in` operator (`in ["password", "secret"]`)
-  - **Extended SAFE_IDIOM_PATTERNS**: New entry broadening env-var access suppression from DB-001-only to all hardcoded credential findings (DATA-00x, AUTH-00x) when lines contain `process.env`, `os.environ`, `os.getenv()`, `System.getenv()`, `Environment.GetEnvironmentVariable()`, or `env::var()`
-  - **Extended KEYWORD_IDENTIFIER_PATTERNS**: Added password suffixes (`error`, `expired`, `required`, `schema`, `type`, `view`, `prompt`, `attempts`) and prefixes (`forgot`, `enter`, `missing`, `invalid`, `has`, `is`, `no`, `require`); token suffixes (`error`, `invalid`, `missing`, `source`, `response`, `config`, `schema`) and prefixes (`missing`, `invalid`, `expired`, `has`, `is`, `no`, `decode`, `parse`); secret suffixes (`error`, `invalid`, `missing`, `config`, `schema`, `type`, `provider`) and prefixes (`has`, `is`, `no`, `missing`, `invalid`, `create`, `generate`, `list`)
-
-### Tests
-- 19 new tests across 5 describe blocks: env-var safe idiom broadening (4), config/schema object keys (4), assignment from function call (4), string comparison/dispatch (4), extended identifier patterns (3)
-- 1646 tests, 0 failures
-
-## [3.20.7] — 2026-03-03
-
-### Fixed
-- **False positive reduction — 4 new heuristics (H2c, H22–H24) + extended identifier patterns + H20 bugfix** — Continued proactive FP analysis targeting typed declarations, error messages, regex patterns, and type-definition files:
-  - **H2c**: Type-definition file gating — absence-based findings suppressed on files classified as `"types"` by `classifyFile()` (`.d.ts` files, interface-only modules); type-definition files declaring shapes should not trigger missing-implementation findings
-  - **H22**: Typed parameter/property declarations — findings suppressed when security keywords (`password`, `secret`, `token`) appear as typed parameter names (`password: string`, `String secret`) rather than hardcoded credentials; excludes LOGPRIV findings that flag the parameter itself
-  - **H23**: Throw/raise error message strings — findings suppressed when keywords appear in static throw/raise error messages (`throw new Error("Invalid password")`, `raise ValueError("Bad token")`); extends H21 logging concept to error-throwing; excludes LOGPRIV/LOG-* findings
-  - **H24**: Regex pattern literal context — findings suppressed when keywords appear inside regex patterns (`/password|secret|token/`, `re.compile(r"...")`, `new RegExp(...)`, `Pattern.compile(...)`)
-  - **H20 bugfix**: Enum/union type definitions — fixed false match where bare assignments like `password = "admin123"` incorrectly matched the enum-member pattern; now requires `enum`, `type =`, or `class` declaration context in the file
-  - **Extended KEYWORD_IDENTIFIER_PATTERNS**: Changed separators from `\s*` to `[-_]?` across password, secret, token, delete, exec patterns to support snake_case/kebab-case identifiers while preventing space-separated English phrases from matching; added new suffixes (column, prop, param, check, verify, form, dialog, modal) and prefixes (confirm, verify, validate, check, reset, new, old, current, previous, hashed, encrypted) to password pattern; added client/app prefixes to secret; added verification/reset suffixes to token
-
-### Tests
-- 21 new tests across 5 describe blocks: keyword-in-identifier with underscore/hyphen separators (7), type-definition file gating (2), typed parameter/property declarations (4), throw/raise error messages (4), regex pattern literals (4)
-- 1627 tests, 0 failures
-
-## [3.20.6] — 2026-03-03
-
-### Fixed
-- **False positive reduction — 4 new heuristics (H18–H21) + 4 new pattern entries** — Proactive FP analysis adding heuristics and extending pattern arrays to reduce false positives across common code idioms:
-  - **H18**: Barrel/re-export file suppression — absence-based findings (ERR-001, OBS-001, etc.) suppressed on files where ≥80% of lines are re-exports, imports, comments, or blanks (index.ts, \_\_init\_\_.py, mod.rs barrel files)
-  - **H19**: Decorator/annotation security presence — AUTH absence findings suppressed when the file contains authentication decorators (`@login_required`, `[Authorize]`, `@PreAuthorize`, `@Secured`, `@RolesAllowed`, etc.)
-  - **H20**: Enum/union type definitions — keyword collision findings suppressed when all flagged lines are enum values or union type members containing security keywords as inert values (`Action.DELETE`, `type Method = "GET" | "DELETE"`)
-  - **H21**: Log/error message security keywords — findings triggered by `password`/`secret`/`token`/`credential` suppressed when all flagged lines are logging calls (`logger.error(...)`, `console.warn(...)`) describing the operation rather than leaking credentials; excludes LOGPRIV/LOG-* findings that flag the logging itself as the problem
-  - **Extended KEYWORD_IDENTIFIER_PATTERNS**: Added `key` pattern (matches `apiKeyHeader`, `primaryKey`, `foreignKey`, `keyVaultUrl` but NOT `apiKey` alone) and `hash` pattern (matches `contentHash`, `fileHash`, `checksumHash`, `hashCode`, `hashMap` — non-crypto contexts)
-  - **Extended SAFE_IDIOM_PATTERNS**: Added log/error message suppression for security keywords in logging calls (with LOGPRIV exclusion) and HTTP routing `app.delete()`/`router.delete()` suppression for data-deletion findings
-
-### Tests
-- 32 new tests covering all new heuristics and pattern entries: key/hash identifier collision (4), log/error message idiom (4), HTTP routing delete (3), barrel/re-export files (3), decorator security presence (4), enum/union type (4), log message keyword suppression (4), TP confidence edge cases (6)
-- 1606 tests, 0 failures
-
-## [3.20.5] — 2026-03-03
-
-### Fixed
-- **False positive reduction — 6 new heuristics + 4 extended patterns** — Added six new deterministic FP heuristics to `filterFalsePositiveHeuristics` and extended three existing pattern sets, addressing 12 high-confidence false positive categories identified in regulated-policy evaluations:
-  - **H12**: Distributed lock fallback — SCALE local-lock findings suppressed when Redlock/Redis/etcd/Consul/ZooKeeper distributed locking is present in the same module
-  - **H13**: Retry/backoff/fallback chain — SOV-001/REL resilience findings suppressed when retry with exponential backoff or multi-tier fallback (cache→online→bundled) is implemented
-  - **H14**: Constant definitions — I18N hardcoded-string findings suppressed when flagged lines are ALL_CAPS or `const` constant definitions (field-name keys, not user-facing text)
-  - **H15**: Bounded-dataset tree traversal — PERF/COST O(n²) findings suppressed when code traverses tree structures (chapters→sections→articles) or operates on documented bounded datasets
-  - **H16**: Read-only content fetch — SOV-002 cross-border findings suppressed when code fetches public/regulatory content with no personal data patterns
-  - **H17**: Cache-age/TTL context — COMP age-verification findings suppressed when "age" appears in cache/TTL context (cache_age, max_age, stale) with no user-age patterns (dob, minor, parental)
-  - **Extended WEB_ONLY_PREFIXES**: Added `I18N-` — i18n findings now gated to files with HTML/JSX/DOM patterns
-  - **Extended KEYWORD_IDENTIFIER_PATTERNS**: Broadened `age` regex to cover hyphenated/underscored cache-age, stale-age, fresh-age, and age-seconds/minutes/hours/days/ms/header patterns
-  - **Extended SAFE_IDIOM_PATTERNS**: Added 3 new entries — json.dumps/JSON.stringify for SOV-003 data-export findings, os.environ.get/process.env for DB-001 connection-string findings, and justified type:ignore/noqa/eslint-disable for SWDEV-001/CICD-003 suppression findings
-
-- **Judge system prompt anti-FP guidance** — Added `FALSE POSITIVE AVOIDANCE` sections to 9 judge system prompts, providing explicit instructions to avoid known false-positive patterns at the LLM generation layer:
-  - **performance.ts**: Tree traversal is O(n), not O(n²); bounded reference datasets; list comprehension flattening
-  - **scalability.ts**: Distributed lock with local fallback is correct graceful degradation; two-tier locking design
-  - **data-sovereignty.ts**: Retry/fallback ≡ circuit breaker; read-only reference data ≠ cross-border egress; internal serialization ≠ data export
-  - **compliance.ts**: Cache-age/TTL "age" ≠ user age verification
-  - **internationalization.ts**: Constant definitions ≠ user-facing strings; developer tools/MCP servers don't need i18n; sourced regulatory text
-  - **cost-effectiveness.ts**: Tree/hierarchy traversal; bounded reference datasets
-  - **database.ts**: Environment variable fallback defaults; in-memory/embedded database defaults
-  - **code-structure.ts**: Dict[str,Any] at JSON boundaries; large single-responsibility files; async nesting ≤4
-  - **software-practices.ts**: Justified suppression comments; minimum-viable async nesting; single-module cohesion
-
-### Tests
-- Added 17 new tests covering all 6 new FP heuristics (H12–H17), I18N web-only gating, safe idiom extensions (env var fallback, justified suppressions, json.dumps), with both positive (should suppress) and negative (should keep) test cases
-- All 1,574 tests pass (976 judges + 218 negative + 268 subsystems + 70 extension + 42 tool-routing)
-
-## [3.20.4] — 2026-03-03
-
-### Fixed
-- **Stale documentation counts** — Updated all references across README, docs, server.json, action.yml, package.json, Dockerfile, extension metadata, examples, and scripts from "35 judges" → "37 judges", "47 patches" → "53 patches", and test badge "1515" → "1557". Historical changelog entries left unchanged.
-
-### Tests
-- **Doc-claim verification tests** — Added 42 new tests covering: JUDGES array count assertion (exactly 37), judge schema validation (id, name, domain, description), unique judge ID enforcement, scoring penalty constants (critical=30, high=18, medium=10, low=5, info=2), confidence-weighted deductions, score floor/ceiling, positive signal bonuses (+3/+3/+3/+2/+2/+2/+2/+1/+1/+1 with cap at 15), verdict threshold logic (fail/warning/pass boundaries), and STRUCT threshold rules not previously covered: STRUCT-001 (CC>10), STRUCT-007 (file CC>40), STRUCT-008 (CC>20), STRUCT-010 (>150 lines).
-- All 1,557 tests pass (976 judges + 218 negative + 251 subsystems + 70 extension + 42 tool-routing)
-
-## [3.20.3] — 2026-03-03
-
-### Fixed
-- **Azure resource ID false positive** — Layer 2 deep review no longer flags Azure resource identifiers (policy definition IDs, role definition IDs, tenant IDs, subscription GUIDs) as "invalid GUIDs" when they contain characters outside the hex range. All three deep-review builders (single-judge, tribunal, simplified) now include explicit guidance that Azure resource IDs are opaque platform constants and must not be validated for strict UUID compliance.
-
-## [3.20.2] — 2026-03-03
-
-### Fixed
-- **"Auto" model fallback** — When the Copilot Chat model selector is set to "auto", `request.model` returns a pseudo-model with no real endpoint. Layer 2 now catches the `sendRequest` failure and falls back to `selectChatModels()` to find a working model. Applied to both `chat-participant.ts` (deep review) and `diagnostics.ts` (deep review + refinement).
-
-## [3.20.1] — 2026-03-03
-
-### Fixed
-- **Layer 2 now uses user-selected model** — The `/deepreview` deep review and diagnostics Layer 2 no longer hardcode `gpt-4o`. In chat, it uses `request.model` (the model the user picked in the Copilot Chat model selector). In diagnostics, it uses `selectChatModels()` without a family filter, respecting whatever models are available.
-
-## [3.20.0] — 2026-03-06
-
-### Added
-- **PowerShell language support** — Full PowerShell analysis across all 37 judges. Includes language patterns (cmdlet-verb conventions, `Invoke-Expression` detection, `$using:` scope, credential handling, `ConvertTo-SecureString`, pipeline best practices), AST structural parsing (function/class extraction, comment association, nesting depth, dead-code detection after `throw`/`return`), taint tracking, and cross-file taint analysis. PowerShell is now recognized in all LANG_MAP entries, the structural parser, the tree-sitter AST layer, and the VS Code extension tool routing.
-
-### Fixed
-- **Deep review content-policy refusal (enhanced)** — The v3.19.6 fix (switching from `systemPrompt` to `description`) was necessary but insufficient for GDPR/IaC files where the aggregate of 37 security-related judge descriptions still triggered GPT-4o content filters. Added a three-layer defence: (1) `DEFENSIVE_PREAMBLE` framing the request as an authorised voluntary code review, (2) `isContentPolicyRefusal()` detection with automatic retry using a simplified prompt that groups judges into 7 quality dimensions instead of listing all 37, (3) alternative model family fallback when the primary model refuses. Also fixed `buildSingleJudgeDeepReviewSection` which still used `judge.systemPrompt` instead of `judge.description`.
-- **Bicep/Terraform missing from LM tool LANG_MAP** — The VS Code extension's `lm-tool.ts` language map now includes `bicep` and `terraform` for parity with `chat-participant.ts` and `diagnostics.ts`.
-
-### Tests
-- All 1,472 tests pass (976 judges + 217 negative + 209 subsystems + 70 extension)
-
-## [3.19.6] — 2026-03-03
-
-### Fixed
-- **Deep review content-policy refusal** — The `/deepreview` Layer 2 prompt concatenated all 37 judges' full `systemPrompt` text — including adversarial mandates like "hunt for exploits" and "think like an attacker" — into a single User message. LLM safety filters interpreted this as requesting help with security exploitation and refused with "Sorry, I can't assist with that." Fixed by using condensed `judge.description` (1-line summary) instead of full `systemPrompt` in tribunal mode, adding professional code-review framing, and prepending an Assistant context message to establish legitimate tool identity.
-
-### Tests
-- All 1,460 tests pass (964 judges + 217 negative + 209 subsystems + 70 extension)
-
-## [3.19.5] — 2026-03-05
-
-### Fixed
-- **Cross-judge dedup: same-topic bridging** — Findings from different evaluators about the same known topic (e.g., API versioning, deep nesting, abrupt termination) are now deduped even when they reference different line numbers. Previously, two evaluators flagging "API endpoints without versioning" on different lines escaped dedup because the union-find only clustered same-line findings. Added known-topic bridging logic and 3 new topic patterns (`api-versioning`, `pagination`, `abrupt-termination`).
-- **DOC-001: Python validators no longer flagged as undocumented** — Pydantic `@validator`, `@field_validator`, `@root_validator`, and `@property`-decorated methods are now recognized as framework internals and skipped from the exported-function-without-docs check.
-- **DOC-001: Java getters/setters no longer flagged** — Trivial one-line getters/setters (`getName()`, `setName()`) are skipped from the exported-function documentation check.
-- **DOC-001: Route wiring lines no longer flagged** — Method-chained route registrations (`.route(`, `.get(`, `.HandleFunc(`) are no longer flagged as API endpoints missing documentation. Only handler definitions need docs.
-- **DOC-001: `main()` no longer flagged as long function** — Application entry-point `main()` functions are excluded from the long-function-with-insufficient-comments check.
-- **STRUCT-005: Closures and lambdas no longer cause dead code FPs** — Go `return func(...) {` closures and C++ `return std::all_of(..., [](char c) {` lambdas are no longer treated as terminal statements that make subsequent code unreachable.
-- **STRUCT-005: Braceless `if` statements no longer cause dead code FPs** — C# single-line `if (cond) return;` without braces no longer marks the next line as dead code.
-- **UX-001: Server-side error responses no longer flagged as "generic error messages"** — JSON error keys (`"error"`), structured logging calls (`.Error()`, `logger.Error()`), and HTTP response builders (`HttpResponse::`, `http.Error()`) are filtered from the generic-error-message check.
-- **I18N-001: Framework metadata no longer flagged as hardcoded strings** — FastAPI/Flask/OpenAPI initialization lines (`FastAPI(title="...")`) are excluded from the hardcoded-user-facing-string check.
-- **MAINT: C/C++ type declarations now skip magic number check** — `int port = 8080` and similar C/C++ typed variable declarations are recognized as named assignments, not magic numbers.
-- **MAINT: Unused imports no longer cross-line match** — The ES module import regex no longer accidentally matches Python's `from X import Y` syntax across line boundaries.
-- **Compliance: Tighter regulated-operation detection** — Removed `sign` (matches `signIn`, `signal`) and `authorize` (matches `[Authorize]` attribute) from the regulated-operations regex. Attribute/annotation lines are now skipped.
-
-### Changed
-- **Absence promotion** — `TEST-001` ("No tests detected"), `COMP-001` ("Data model lacks classification markers"), and `REL-001` ("No retry logic") are now marked `isAbsenceBased: true` and suppressed in single-file mode alongside other absence findings.
-
-### Tests
-- 1 new dedup test (same-known-topic bridging), 1 updated test (topic bridging replaces separate-lines-no-dedup)
-- All 1,460 tests pass (964 judges + 217 negative + 209 subsystems + 70 extension)
-
-### Metrics
-- Cross-language FP sweep: 134 → 122 evaluator-level findings (−12, −9.0%)
-- Pipeline-level (after dedup + absence filtering): 56 → 24 findings (−32, −57.1%)
-- Cumulative since v3.18.3: 170 → 122 evaluator-level (−48, −28.2%)
-
-## [3.19.4] — 2026-03-04
-
-### Changed
-- **Absence gating via `projectMode` flag** — Absence-based findings (e.g., "no rate limiting detected", "no health check endpoint") are now suppressed in single-file evaluation and only surface during project-level analysis (`evaluateProject`). This eliminates ~78 per-file false positives that belong at the project level, not on individual source files. The `EvaluationOptions` type gains an optional `projectMode?: boolean` field; `evaluateProject()` sets it automatically.
-- **Consolidated absence filtering** — Removed duplicate absence filters from `filterFalsePositiveHeuristics` (rules 12 and 13); absence gating is now handled in a single location upstream in `evaluateWithJudge`.
-
-### Fixed
-- **Go `interface{}`/`any` no longer flagged as weak type** — The WEAK_TYPE pattern for Go now only flags `unsafe.Pointer`, not idiomatic Go empty interfaces. Changed in `language-patterns.ts`, `tree-sitter-ast.ts`, and `structural-parser.ts`. Eliminates 4 FPs in the cross-language sweep.
-- **Java wildcard imports no longer flagged** — `dependency-health.ts` skips wildcard import detection for Java, where `import java.util.*` is idiomatic. Eliminates 1 FP.
-- **Go `os.ReadFile` no longer flagged as portability issue** — `portability.ts` skips file I/O detection for Go, where `os.ReadFile` is the standard stdlib API with no portability concern.
-- **Error message prose no longer triggers DATA-001** — `looksLikeRealCredentialValue()` in `shared.ts` now checks word count; strings with 3+ words are recognized as prose/error messages rather than credential values.
-- **C# async with middleware error handling no longer triggers ERR** — `error-handling.ts` detects `UseExceptionHandler`, `ExceptionFilter`, and similar ASP.NET middleware patterns and suppresses redundant async error-handling findings.
-- **STRUCT-005 dead code no longer false-fires across scope boundaries** — `detectDeadCode()` in `structural-parser.ts` resets unreachable tracking at `else`/`elif`/`case`/`default`/`catch`/`finally`/`except` boundaries. Confidence reduced from 0.85 to 0.7.
-
-### Tests
-- 10 new negative regression tests covering all FP fixes above
-- All 1,449 tests pass (963 judges + 217 negative + 209 subsystems + 70 extension)
-
-### Metrics
-- Cross-language FP sweep: 139 → 134 findings (−5, ~3.6% reduction at evaluator level)
-- ~78 additional absence-based findings suppressed at pipeline level in single-file mode
-- Cumulative since v3.18.3: 170 → 134 findings (−36, ~21.2% reduction)
-
-## [3.19.3] — 2026-03-03
-
-### Fixed
-- **MCP tool description improvements to prevent LLM misrouting** — User prompts mentioning sovereignty, IaC, or deployment configuration were incorrectly routed to `analyze_dependencies` instead of `evaluate_code_single_judge`. Root cause: (1) `evaluate_code` and `evaluate_code_single_judge` descriptions didn't mention infrastructure-as-code file types; (2) `analyze_dependencies` description contained "supply-chain risks" which overlapped with sovereignty judge's supply chain pillar; (3) "deployment configuration" matched manifest file concepts. Fixed all three tool descriptions: evaluation tools now explicitly list Bicep/Terraform/ARM/CloudFormation support and key judge domains; `analyze_dependencies` now clarifies it only accepts package manager manifests (package.json, requirements.txt, etc.) and explicitly excludes IaC files.
-
-### Added
-- **Tool routing test suite** (`tests/tool-routing.test.ts`) — 43 automated tests using a TF-IDF scoring engine that simulates LLM tool selection against MCP tool descriptions. Includes 30 positive tests (prompt routes to correct tool across all 9 tools), 11 negative tests (IaC/sovereignty prompts must NOT route to `analyze_dependencies`, package manager prompts must NOT route to evaluation tools), and 2 regression tests reproducing the exact misrouting bug.
-
-### Tests
-- 43 new tool routing tests
-- All 1,422 tests pass (963 judges + 43 routing + 207 negative + 209 subsystems)
-
-## [3.19.2] — 2026-03-03
-
-### Fixed
-- **IaC security FP — resource-name parameters no longer flagged for `@secure()`** — Bicep parameters like `param keyVaultName string` were incorrectly flagged because the regex matched "key" inside compound names. Added post-match exclusion: if the parameter name ends with a resource-identifier suffix (`Name`, `Uri`, `Url`, `Endpoint`, `Id`, `ResourceGroup`, `Location`, `Sku`, `Region`, `Type`), it is recognized as a resource reference rather than a secret and skipped.
-- **MCP server version now dynamically read from `package.json`** — The `McpServer` constructor was hardcoded to version `3.6.0` since initial creation. MCP clients may cache tool definitions keyed by server version; a stale version prevents clients from refreshing their cached tool lists. Now reads version from `package.json` at startup.
-
-### CI
-- **npm propagation wait in publish workflow** — Added a polling step (up to 10 × 15s = 150s) that verifies the npm package is visible before proceeding to MCP Registry publish, preventing the race condition that caused the v3.19.1 publish to fail on first attempt.
-
-### Tests
-- 3 new negative tests for IaC security resource-name exclusion
-- All 1,379 tests pass (963 judges + 207 negative + 209 subsystems)
-
-## [3.19.1] — 2026-03-03
-
-### Fixed
-- **CI/CD absence gating on application source files** — CI/CD absence rules (no test infrastructure, no linting, no build script) now skip files classified as server or utility code. These project-level concerns belong in config/manifest files, not individual application source files. Eliminates ~8 FPs across the 6-language sweep.
-- **Framework-aware auth pattern expansion** — `hasAuthMiddleware` regex expanded from 14 to 24 alternatives, adding language-specific patterns: Python (`jwt.decode`, `OAuth2PasswordBearer`, `get_current_user`), Go (`jwt.Parse`, `jwt.ParseWithClaims`), Rust (`DecodingKey`, `auth_middleware`), C# (`[Authorize]`), and generic (`verify_token`, `check_auth`, `getCurrentUser`).
-- **Magic number detection tuning** — Three new exclusions reduce false positives: (1) numbers inside string literals (e.g., `":8080"`), (2) named constant declarations (`const PORT = 8080`), (3) keyword arguments (`pool_recycle=3600`).
-
-### Tests
-- 11 new negative tests covering all three FP reduction changes
-- All 1,376 tests pass (963 judges + 204 negative + 209 subsystems)
-
-### Metrics
-- Cross-language FP sweep: 152 → 139 findings (−13, ~8.6% reduction)
-- Cumulative since v3.18.3: 170 → 139 findings (−31, ~18.2% reduction)
-
-## [3.19.0] — 2026-03-04
-
-### Added
-- **Strategy 1 — Comment-stripping before pattern matching** — New `testCode(code, pattern)` utility replaces raw `pattern.test(code)` calls across 31 evaluators (184 conversions). Strips `//`, `/* */`, `#`, and Python `"""`/`'''` docstrings before testing, so patterns mentioned only in comments no longer trigger false positives. String literals are preserved so import paths, require() arguments, and route strings remain matchable.
-- **Strategy 2 — Multi-line context windows** — New `getContextWindow(lines, lineNum, radius)` utility enables post-match filters to check adjacent lines. Applied to 5 high-value evaluators:
-  - **cloud-readiness** — Hardcoded host/port fallback (`??`, `||`, `getenv`) detected across ±2 lines
-  - **portability** — Same fallback pattern for localhost/IP addresses
-  - **data-security** — JWT `algorithms=` parameter detected on adjacent lines in multi-line Python calls
-  - **scalability** — `await` on blocking calls detected ±1 line
-  - **ai-code-safety** — Auth-check patterns detected ±2 lines from wildcard permissions
-- **Strategy 3 — Project-mode absence resolution** — New `scanProjectWideSecurityPatterns()` scans all project files for security patterns regardless of import relationships. `applyProjectWideAbsenceResolution()` reduces confidence of absence-based findings when the security category exists anywhere in the project (halved reduction vs direct-import). 5 new security categories added: health-check, graceful-shutdown, CORS, secrets-management, environment-config (total: 12).
-
-### Tests
-- 22 new tests covering all three FP reduction strategies (15 subsystem unit tests + 7 negative integration tests)
-- All 1,365 tests pass (963 judges + 193 negative + 209 subsystems)
-
-## [3.18.3] — 2026-03-03
-
-### Fixed
-- **FP reduction round 5 — cross-language sweep** — Ran all 36 evaluators against clean idiomatic code in 6 languages (Python/FastAPI, Rust/Actix-web, C#/ASP.NET Core, Java/Spring Boot, Go/stdlib, C++/REST), eliminating 21 false positives across 10 source files:
-  - **CLOUD-001 / PORTA-001** — Configurable defaults (`unwrap_or_else`, `os.Getenv`, `??`, `||`, `environ.get`) no longer flagged as hardcoded hosts
-  - **AICS-013** — Auth-check post-filter excludes `hasRole`, `@PreAuthorize`, `[Authorize]`, `claims.role`, CORS headers
-  - **AICS-016** — `ActionResult` (C#) no longer matched as unsafe action usage; requires explicit `_` or `.` separator
-  - **A11Y** — `spring` no longer matched inside words (e.g. `springframework`); form-error rule uses specific HTML element list instead of broad regex
-  - **DATA-001** — Python `jwt.decode` with `algorithms=` parameter (verified decode) no longer flagged
-  - **SWDEV-002** — Go `if err != nil` no longer flagged as bare exception catch
-  - **CONC-001** — Go graceful-shutdown goroutines (`signal.Notify`, `Shutdown`, `SIGTERM`) recognized as managed workers
-  - **CFG-001** — Go multi-line `os.Getenv` + `== ""` validation detection
-  - **DOC-001** — Backward-walk now recognizes Go `//` comments, Rust `///` with `#[attr]` traversal, C# `///` with `[Attr]` traversal, Python body docstrings
-
-### Bug Fixes
-- **Undefined `lines` variable in 4 evaluators** — `cloud-readiness.ts`, `portability.ts`, `ai-code-safety.ts`, and `data-security.ts` referenced `lines[ln - 1]` where `lines` was either undefined, scoped inside an if-block, or was a line-number array instead of text lines. Post-filter logic silently failed, producing incorrect results. Each file now defines a properly scoped `code.split("\n")` variable.
-
-### Tests
-- 30+ new negative FP regression tests with true-positive preservation checks
-- All 1,343 tests pass (963 judges + 186 negative + 194 subsystems)
-
-## [3.18.2] — 2026-03-03
-
-### Fixed
-- **FP reduction round 4 — IaC gates + cross-language fixes** — 11 rules across 7 evaluators fixed to eliminate false positives on Infrastructure-as-Code files (Bicep, Terraform) and cross-language patterns:
-  - **SOV-001** catch-all and data-portability rules no longer fire on IaC templates
-  - **COST-001** caching and connection-pooling rules no longer fire on IaC templates
-  - **DOC-002** block-comment rule gated on IaC + expanded regex to recognize Bicep `@description`, `targetScope`, `metadata`, and non-JSDoc block comments
-  - **DOC-001** magic-numbers rule no longer flags Bicep numeric configuration values (SKU sizes, byte limits, retention days)
-  - **CACHE-002** no-cache-headers rule gated on IaC
-  - **SCALE-006** rate-limiting and **SCALE-010** circuit-breaker rules gated on IaC
-  - **CLOUD-001** resource-cleanup rule gated on IaC
-  - **AICS-010** input-validation rule now recognizes Java Bean Validation annotations (`@Valid`, `@NotNull`, `@NotBlank`, `@NotEmpty`, `javax.validation`, `jakarta.validation`)
-
-### Tests
-- 25 new negative tests with true-positive preservation checks covering all fixed rules
-- Comprehensive empirical sweep against Bicep, Terraform, Python, Rust, Java, and Go templates
-- All 1,320 tests pass (963 judges + 194 subsystems + 163 negative)
-
-## [3.18.1] — 2026-03-03
-
-### Fixed
-- **Python nested-loop false positives** — Generator expressions (`all(x for x in items)`), list comprehensions, and `x in string` substring checks were incorrectly flagged as nested O(n²) loops by both the cost-effectiveness and performance evaluators. Two root causes fixed:
-  - Loop regex matched `for` mid-line inside comprehensions/generators — now requires `for`/`while` at line start
-  - Loop depth tracked via `}` brace counting, which never decrements in Python — now uses indentation-stack scoping so sequential non-nested loops are correctly recognized as siblings
-- **CI lint warnings treated as errors** — Resolved 12 pre-existing ESLint warnings (`no-useless-escape`, `no-unused-vars`) across 5 files that caused CI to exit with code 1
-- **Restored intentional `moment` import** — `lint-staged` had silently removed the deliberately-vulnerable `import moment from "moment"` in `sample-vulnerable-api.ts`, breaking DEPS evaluator tests. Restored with `eslint-disable-line` guard
-
-### Removed
-- Internal dev-only scripts (`cross-project-analysis.ts`, `analyze-report-findings.ts`) — not needed for production releases
-
-### Tests
-- 3 new tests: Python nested loops (TP), generator expressions (FP prevention), sequential non-nested loops (FP prevention)
-- All 963 tests pass (960 judges + 3 new)
-
-## [3.18.0] — 2025-07-09
-
-### Improved
-- **Third round false positive reduction** — Cross-project findings 11,011 → 7,898 (−28.3%, −3,113 findings) across 30 projects / 1,149 files through 7 complementary strategies:
-  - **Cross-judge semantic dedup** — 8 new topic patterns in `crossEvaluatorDedup()`: `deep-nesting`, `missing-tests`, `type-safety`, `missing-healthcheck`, `missing-linting`, `missing-build-script`, `missing-documentation`, `missing-error-tracking`. Eliminates duplicate findings from different judges flagging the same conceptual issue.
-  - **5 new `isAbsenceBased` flags** — Added explicit absence markers to internationalization (encoding detection), agent-instructions (AGENT-001), dependency-health (DEPS-001), cybersecurity (security headers), and rate-limiting (no 429 handling). Triggers severity cap to medium + confidence cap to 0.6.
-  - **Per-file finding cap** — New `applyPerFileFindingCap()` function with default limit of 20 findings per evaluation. Prioritizes by severity → confidence → actionability (suggestedFix presence) → description length. Configurable via `maxFindingsPerFile` option (0 to disable).
-  - **CI/CD project-level gating** (FP rule #12) — Suppresses all absence-based `CICD-*` findings, which are inherently project-level concerns that cannot be meaningfully assessed from individual file analysis.
-  - **SOV relevance gating** (FP rule #13) — Suppresses absence-based `SOV-*` findings on files that contain no data operation patterns (SQL, fetch, axios, database access, ORM methods, store operations).
-  - **DOC-001 severity adjustment** — Documentation findings handled by existing absence pipeline for appropriate severity/confidence calibration.
-  - **Confidence-based progressive disclosure** — New `confidenceTier` field on `Finding` type: `"essential"` (≥0.8), `"important"` (≥0.6), `"supplementary"` (<0.6). Enables UI consumers to implement progressive disclosure of findings by confidence level.
-- **Cross-project breakdown**: { essential: 3,677, important: 4,010, supplementary: 211 } | { critical: 222, high: 1,342, medium: 4,195, low: 1,865, info: 274 } | absence-based: 1,722
-- All 1,358 tests pass (960 judges + 134 negative + 194 subsystems + 70 extension-logic)
-
-## [3.17.0] — 2025-07-08
-
-### Improved
-- **Second round false positive reduction** — Cross-project findings 11,158 → 11,011 (−1.3%) from deterministic rules; additional reductions in LLM-assisted paths via precision mandates:
-  - **35 `isAbsenceBased` flags** across 11 evaluators (authentication ×8, observability ×4, caching ×2, cloud-readiness ×4, configuration-management ×4, api-design ×3, reliability ×1, scalability ×2, agent-instructions ×4, accessibility ×1, data-sovereignty ×1) — triggers severity cap to medium + confidence cap to 0.6 for absence-patterned findings
-  - **Project-level absence dedup** in `evaluateProject()` — groups duplicate absence findings by title, keeps only the highest-confidence instance
-  - **Precision mandates injected** into LLM-facing assembly points (`prompts.ts` full-tribunal, `deep-review.ts` single-judge and tribunal paths) — overrides adversarial stance with "cite specific code evidence, do not flag absence speculatively, prefer fewer high-confidence findings"
-  - **35 judge systemPrompts softened** — removed "false positives are preferred over missed [X]" and "do not give the benefit of the doubt" language from all judge files; replaced with evidence-based framing
-  - **4 new FP heuristic rules** in `false-positive-review.ts`:
-    - Rule 8 strengthened: absence confidence threshold raised from 0.35 → 0.45
-    - Rule 9: Web-only rules (A11Y-, UX-) suppressed on non-web code (no HTML/JSX/DOM patterns)
-    - Rule 10: Findings targeting empty/whitespace-only lines removed
-    - Rule 11: Absence-based findings on trivially small files (<10 substantive lines) removed
-- All 1,154 tests pass (960 judges + 194 subsystems)
-
-## [3.16.0] — 2025-07-06
-
-### Improved
-- **20% false positive reduction** — Comprehensive cross-project analysis (13,981 findings across 30 projects / 1,149 files) identified and fixed 5 root cause gaps in the FP filtering pipeline, reducing findings to 11,158:
-  - **Config file gating** — YAML/JSON/TOML/INI/ENV files now classified as "config" by `classifyFile()`, suppressing 30 code-only rule prefixes. YAML file findings: 891 → 0 (100% elimination)
-  - **Test file suppression** — Extended `PROD_ONLY_RULE_PREFIXES` from 4 to 22 prefixes (added AGENT/AICS/PERF/PORTA/UX/I18N/A11Y/LOGPRIV/CACHE/DATA/API/SOV/DOC/MAINT/COMP/CICD/COST/SWDEV). Test file findings: 1,500 → 306 (80% reduction)
-  - **Absence-based gating** — Extended `ABSENCE_GATED_PREFIXES` with 7 new prefixes (SOV/DOC/MAINT/SWDEV/COST/COMP/TEST); removed counterproductive `projectLevelKeywords` exclusion that prevented CI/CD, pipeline, and infrastructure findings from being gated on non-server files
-  - **Evaluator `isAbsenceBased` flags** — Added explicit flags to 12 findings across 5 evaluators (ci-cd ×6, data-sovereignty ×1, documentation ×1, software-practices ×1, cost-effectiveness ×3)
-  - **PII geo-partitioning precision** — Added line-number collection to PII storage finding in data-sovereignty evaluator, making it presence-based (specific DB operation lines) rather than falsely gated as absence-based
-- **11 new subsystem tests** covering all FP improvements (194 total, was 183)
-- All 1,154 tests pass (960 judges + 194 subsystems)
-
-## [3.15.1] — 2025-07-06
-
-### Fixed
-- **ReDoS (catastrophic backtracking) in 8 evaluator/AST files** — Comprehensive audit and fix of regex patterns that could cause exponential or polynomial backtracking on adversarial or large inputs:
-  - `observability.ts` — String-stripping regex `(["'\`])(?:\\.|(?!\1).)*\1` replaced with safe per-quote-type pattern
-  - `ethics-bias.ts` — Same string-stripping regex fix
-  - `portability.ts` — `pathSepPattern` restructured: trailing `[^...]*` moved outside the repeated `{2,}`/`{3,}` groups to eliminate NFA ambiguity between iterations
-  - `cross-file-taint.ts` — `.*SOURCE.*` dynamic regex replaced with `[^\n]*SOURCE[^\n]*` to avoid O(n²) between adjacent wildcards (2 instances)
-  - `software-practices.ts` — `(?:.*,\s*)?` in boolean-param detection replaced with `(?:[^,)]*,\s*)*` to eliminate `.*`/`,` overlap
-  - `cybersecurity.ts` — Same `(?:.*,\s*)?` fix in mass-assignment detection
-  - `scalability.ts` — `\(.*(?:length|size|count).*\)` replaced with `\([^)]*...[^)]*\)` to prevent O(n²) between adjacent wildcards
-  - `ai-code-safety.ts` — Triple `.*` in f-string prompt injection pattern replaced with `[^{]*` and `[^}]*` to prevent O(n³) backtracking
-- All 1143 tests pass (960 judges + 183 subsystems)
-
-## [3.15.0] — 2026-03-02
-
-### Reverted
-- **Removed LLM-based false positive filter (v3.14.0)** — The external-API approach was architecturally wrong. Judges are agent prompts meant to leverage the calling model (Copilot, ChatGPT, etc.) via their `systemPrompt` fields — they should not call a separate LLM API with a separate API key. All v3.14.0 changes have been fully reverted:
-  - Deleted `src/llm-fp-filter.ts`
-  - Reverted `register-evaluation.ts`, `register-workflow.ts`, `deep-review.ts`, `api.ts`
-  - Removed 15 LLM filter tests from `subsystems.test.ts`
-
-### Added
-- **False-Positive Review meta-judge** (`false-positive-review`) — A new 37th judge dedicated to FP detection, following the correct hybrid architecture:
-  - **Agentic side** (`systemPrompt`): Comprehensive FP-expert persona covering a 10-category taxonomy — string literal context, comment context, test context, identifier-keyword collision, IaC gating, stdlib idiom, adjacent mitigation, import/type-only, serialization vs export, absence-based in partial code. The calling model uses this prompt in the deep review section to contextually review findings for false positives.
-  - **Deterministic side** (`src/evaluators/false-positive-review.ts`): Pipeline post-processing step in `evaluateWithTribunal` that removes findings matching known FP patterns:
-    - App-only rules (CYBER, AUTH, PERF, etc.) suppressed on IaC templates
-    - Prod-only rules (RATE, SCALE, OBS, CLOUD) suppressed on test files
-    - Findings where all target lines are comments or string literals
-    - Findings targeting import/type declarations only
-    - Keyword-in-identifier collisions (e.g. "age" in `maxAge`, "password" in `passwordField`)
-    - Safe stdlib idioms (dict.get, JSON.stringify, path.join with literals)
-    - Absence-based findings with very low confidence (<35%)
-  - **15 new tests** covering all heuristic categories
-
-## [3.14.0] — 2026-03-02 [REVERTED]
-
-_This release has been fully reverted in v3.15.0. See above for details._
-
-## [3.13.10] — 2026-03-02
-
-### Fixed
-- **5 evaluator false-positive fixes** from ninth round of real-world Copilot feedback (`data_loader.py` Python GDPR text loader/indexer, persisted across 3 remediation iterations):
-  - **COMP-001** (compliance) — Age-verification rule now checks ±3 line context window for cache/TTL keywords (`cache`, `ttl`, `max_age`, `stale`, `freshness`, `expir`). The word "age" in cache-age/TTL logging contexts is no longer flagged as age-related user data.
-  - **SOV-001** (data-sovereignty) — Region-policy rule now suppresses Python `global` scope declarations (`global my_var`), `GLOBAL_CONFIG`-style variable names, and `global_cache`/`_global` identifiers. Suppression is bypassed when the line also contains real geographic patterns (`us-`, `asia-`, `ap-`, etc.).
-  - **SOV-002** (data-sovereignty) — Cross-border egress rule now requires personal/sensitive data context (`user`, `customer`, `email`, `payment`, `pii`, etc.) before flagging HTTP calls. Modules that only fetch read-only reference content (regulation text, documentation) are no longer flagged.
-  - **SOV-003** (data-sovereignty) — Export-path rule now suppresses standard serialization library calls (`json.dumps`, `json.dump`, `pickle.dump`, `yaml.dump`, `csv.dump`, `msgpack`, `marshal`, `toml.dump`, `pprint`). In-memory or local-file serialization is not cross-border data export.
-  - **PERF-001** (performance) — Duplicate-fetch rule now validates that `get()` calls are actual HTTP client methods (`requests.get`, `axios.get`, `http.get`, `fetch`) or use URL-like arguments (`http://`/`https://`). Python `dict.get("key")`, `config.get("name")`, and `os.environ.get("VAR")` are no longer counted as network fetches.
-
-### Added
-- **13 new regression tests** (1326 total) covering all 5 FP fixes: cache-age suppression (positive + negative), Python global keyword suppression (scope declaration, variable names, geographic passthrough), read-only content fetch (reference loader vs personal data exporter), serialization dump (json/yaml/pickle + real export passthrough), dict.get vs HTTP get (dict.get, fetch, requests.get).
-
-## [3.13.9] — 2026-03-02
-
-### Fixed
-- **Broad IaC awareness sweep** — 11 additional rules across 7 evaluators now suppress false positives on Bicep, Terraform, and ARM templates:
-  - **SOV-001** (data-sovereignty) — Region-without-policy rule gated with `!isIaCTemplate`. Bicep `@allowed` location params are policy-compliant by design.
-  - **SOV-003** (data-sovereignty) — Replication/backup localization rule gated. IaC GRS/geo-redundant config is declarative infrastructure.
-  - **SOV-007** (data-sovereignty) — Telemetry sovereignty rule gated. App Insights resource declarations are not telemetry data flows.
-  - **SOV-009** (data-sovereignty) — Region-without-enforcement rule gated. Bicep location parameters enforce region declaratively.
-  - **SOV-011** (data-sovereignty) — KMS/key sovereignty rule gated. KeyVault resource definitions are infrastructure.
-  - **COMP-002** (compliance) — Tracking/analytics without consent rule gated. IaC monitoring resources are not user-tracking code.
-  - **CYBER** (cybersecurity) — Auth rate-limiting rule gated. `@secure()` password/token params are not auth endpoints.
-  - **AICS-008** (ai-code-safety) — Hardcoded URL rule gated. Container image references and endpoint configs in IaC are declarative.
-  - **CFG-**** (configuration-management) — Full evaluator early-return for IaC templates. All CFG rules are designed for imperative code.
-  - **CLOUD** (cloud-readiness) — Connection string detection gated. ARM/Bicep `connectionStrings` blocks are infrastructure wiring.
-  - **CLOUD** (cloud-readiness) — Config-without-env-vars rule gated. IaC `appSettings` are declarative configuration.
-
-### Improved
-- **Extracted `isIaCTemplate` to `shared.ts`** — Centralized IaC content-detection regex (previously duplicated in 3 evaluators) into a single shared function. Detects Bicep, Terraform, and ARM template patterns.
-
-### Added
-- **11 new regression tests** (1313 total) covering all newly guarded IaC FP rules with targeted Bicep, Terraform, and ARM template fixtures, plus positive tests validating imperative app code is still flagged.
-
-## [3.13.8] — 2026-03-02
-
-### Fixed
-- **4 evaluator false-positive fixes** from eighth round of real-world Copilot feedback (`gdpr_aks.bicep` IaC template, persisted across 3 remediation iterations):
-  - **SOV-001** (data-sovereignty) — Export-path rule now gated on `!isIaCTemplate`. Bicep/Terraform/ARM templates are declarative infrastructure definitions with no data-export code paths.
-  - **SOV-002** (data-sovereignty) — Jurisdiction enforcement rule now gated on `!isIaCTemplate`. Bicep enforces jurisdiction via declarative `@allowed` parameter constraints, not imperative `deny`/`throw` branches.
-  - **COMP-001** (compliance) — Age-verification rule now gated on `!isIaCTemplate`. Infrastructure templates contain no age-related user data or input fields (e.g., AKS `maxAge` is a node pool setting).
-  - **COST-001** (cost-effectiveness) — Nested-loop detection now gated on `!isIaCTemplate`. Declarative IaC has no imperative loop constructs.
-
-### Added
-- **8 new regression tests** (1302 total) covering all 4 IaC FP fixes with both negative (Bicep template suppressed) and positive (imperative application code still detected) cases.
-- `isIaCTemplate` detection regex for Bicep (`param`, `resource`, `@allowed`, `targetScope`), Terraform (`resource`, `variable`, `provider`, `terraform {`), and ARM (`$schema...deploymentTemplate`) across 3 evaluators.
-
-## [3.13.7] — 2026-03-02
-
-### Fixed
-- **4 evaluator false-positive fixes** from seventh round of real-world Copilot feedback (`public/app.js` browser-side JavaScript, score 91→94):
-  - **DB-001** (database) — N+1 query rule now gated on `hasDatabaseContext` (DB imports, SQL statements, connection patterns). Browser-side `fetch()`, `Array.find()`, DOM `.select()` in loops are not N+1 database access.
-  - **COMP-001** (compliance) — Age-related regex now uses `\bage(?![a-z])` word boundary to prevent matching `age` embedded in common words (`package`, `page`, `image`, `storage`, `manage`, `voltage`, etc.). Also word-bounded `child`, `minor`, `dob`, `coppa`.
-  - **SOV-002** (data-sovereignty) — Export path rule now gated on `!isFrontendCode`. Browser code with `document.`, `window.`, `addEventListener`, `querySelector`, React/Vue/Angular/jQuery signals is UI rendering, not data export.
-  - **TEST-001** (testing) — `hasTestStructure` now requires ≥2 of (`describe`, `it`, `test`) for JS/TS instead of any single match. A lone `it(` in browser code (common iterator variable) no longer triggers test evaluator.
-
-### Added
-- **8 new regression tests** (1294 total) covering all 4 FP fixes with both negative (browser code suppressed) and positive (real server/test code still detected) cases.
-
-## [3.13.6] — 2026-03-02
-
-### Fixed
-- **5 evaluator false-positive fixes** from sixth round of real-world Copilot feedback (`public/index.html` static HTML page, score 98→99):
-  - **COMP-001** (compliance) — Age-verification rule now skipped for HTML/markup files. Privacy policy text mentioning “COPPA”, “children”, “under 13” is legal disclosure, not an age-input data flow.
-  - **SOV-001** (data-sovereignty) — Jurisdiction enforcement rule now gated on `!isMarkupFile`. Legal/privacy text mentioning “jurisdiction” in static HTML is not code that needs enforcement branches.
-  - **PORTA-001** (portability) — Path separator rule short-circuits for markup files. Forward slashes in HTML `href`/`src` attributes are valid URL paths, not OS file-path separator misuse.
-  - **CICD-001** (ci-cd) — “No test infrastructure” rule now checks `!isMarkupFile`. HTML `class=` attributes matching the `class` keyword no longer trigger source-code detection.
-  - **COST-001** (cost-effectiveness) — `hasDataFetchOrServe` gated on `!isMarkupFile`. Text content mentioning “fetch” in static HTML does not need in-code caching.
-
-### Added
-- **10 new regression tests** (1286 total) covering all 5 FP fixes with both negative (HTML suppressed) and positive (real source code still detected) cases.
-
-## [3.13.5] — 2026-03-02
-
-### Fixed
-- **7 evaluator false-positive fixes** from fifth round of real-world Copilot feedback (`src/utils.js` post-split barrel module, score 99):
-  - **SOV-001** (data-sovereignty) — "Data export path without sovereignty-aware controls" now skips ES module re-export barrels (`export { ... } from '...'`). Re-export aggregation files do not perform actual data export.
-  - **TEST-001** (testing) — `hasTestStructure` regex now uses `\b` word boundaries for `describe`, `it`, `test` to prevent false matches inside `emit()`, `submit()`, `split()`, `transmit()`, `exit()`. Also expanded `isConfigOrUtility` with `util|utils|helper|helpers|lib|shared|common` patterns, and restricted to file header (first 5 lines) to avoid matching incidental code-body mentions.
-  - **CLOUD-001/002/003** (cloud-readiness) — Health check, graceful shutdown, and feature flag rules now gated on `hasServerCode` (requires `app.listen`, `createServer`, `express()`, Flask, Django, etc.). Utility/helper modules above the line threshold are no longer flagged.
-  - **I18N-001** (internationalization) — `isDirOrModuleLoader` extended with ESM re-export barrel pattern (`export { ... } from`) to suppress "No text encoding specification" on barrel modules.
-  - **COST-001** (cost-effectiveness) — "No caching strategy detected" now gated on `hasDataFetchOrServe` requiring evidence of I/O, data-fetching, or server operations (`fetch()`, `axios`, `.query()`, `db.`, `app.listen`, etc.). Pure utility modules no longer flagged.
-
-### Added
-- **10 new regression tests** (1276 total) covering all 7 FP fixes with both negative (FP suppressed) and positive (real issues still detected) cases.
-
-## [3.13.4] — 2026-03-02
-
-### Fixed
-- **2 evaluator false-positive fixes** from fourth round of real-world Copilot feedback:
-  - **I18N-001** (internationalization) — "No text encoding specification" rule now suppressed for directory/module-loader files that use `readdir`, `readdirSync`, `opendir`, `scandir`, `glob`, `import()`, `require()`, `require.resolve`, `__dirname`, or `path.join`/`path.resolve`. These files perform filesystem navigation, not text-content I/O.
-  - **UX-001** (ux) — "List rendering without empty state" rule now requires UI rendering context (JSX/HTML tags, DOM manipulation, React/Vue/Angular/Svelte imports) before firing. Backend modules using `.map()`/`.forEach()` for data processing are no longer flagged.
-
-### Added
-- **4 new regression tests** (1267 total) covering both FP fixes with negative (FP suppressed) and positive (real issues still detected) cases.
-
-## [3.13.3] — 2026-03-02
-
-### Fixed
-- **12 evaluator false-positive fixes** from third round of real-world Copilot delta feedback (score improved 97→99, high findings 7→1):
-  - **SOV-001** (data-sovereignty) — region patterns inside regex `.test()` / `.match()` calls are now excluded (analysis code referencing region patterns, not actual region usage). Broadened `hasRegionPolicy` with `regionConfig`, `deploymentRegion`, `regionConstraint`, `regionAllowlist`, `regionDenylist`, `dataLocality`, `geoFence`, `geoRestrict`.
-  - **AUTH-001** (authentication) — credential keywords inside regex pattern lines are now skipped (code analysis tools defining credential-detection patterns).
-  - **AUTH-002** (authentication) — route detection now filters out regex `.test()` pattern references and regex-escaped route strings. Files with ≥8 `.test()` calls (code-analysis modules) are excluded as they are evaluator/analysis code, not actual unprotected endpoints.
-  - **DB-001** (database) — SQL injection patterns inside regex `.test()` / `.match()` calls are now excluded (analysis code, not real SQL queries).
-  - **TEST-001** (testing) — "No tests detected" rule now suppresses for code-analysis modules (≥8 regex `.test()` calls), which are analysis/evaluator modules, not undertested production code.
-  - **A11Y-001** (accessibility) — files constructing ARIA helpers or accessibility utilities (`createAccessible`, `ariaHelper`, `buildAria`, `a11yProps`, `makeAccessible`, etc.) are now recognized as building accessible infrastructure and excluded from the "image missing alt" rule. Regex pattern lines also excluded.
-  - **PORTA-002** (portability) — path separator detection now excludes route/API path definitions (`app.get('/api/v1/...')`, `@Get()` annotations), path/route/endpoint variable assignments, and URL-like path strings (`/api/`, `/v1/`, `/auth/`, etc.).
-  - **SWDEV-003** (software-practices) — magic number detection now excludes `.length` threshold comparisons (`.length > 50`, `.length < 3`) and named constant declarations with uppercase identifiers (`const MAX_RETRIES = 5`).
-  - **COMP-001** (compliance) — age-verification finding now downgrades to `low` severity (from `medium`) when age-consent middleware patterns are detected (`ageConsentMiddleware`, `parentalConsentMiddleware`, `coppaMiddleware`, `minorDataRestrict`, `childProtectionGuard`, etc.).
-  - **UX-001** (ux) — inline event handler detection now suppresses entirely for React/JSX files (imports React, uses hooks, JSX/TSX). React's synthetic event props like `onClick` are standard, not inline handlers.
-  - **UX-002** (ux) — form detection tightened to require actual HTML form elements (`<form>`, `<button>`, `onSubmit=`, `handleSubmit`, `formik`, `useForm`) rather than generic keyword mentions of "form" or "submit".
-  - **TEST-002** (testing) — no-test-detection for production code now excluded for analysis modules with heavy regex usage.
-
-### Added
-- **17 new regression tests** (1263 total) covering all 12 false-positive fixes, including both negative cases (FP suppressed) and positive cases (real issues still detected).
-
-## [3.14.0] — 2026-03-02
-
-### Added
-- **Combined Layer 1 + Layer 2 deep review** — new `@judges /deepreview` chat sub-command and `Judges: Deep Review (Layer 1 + Layer 2)` VS Code command. Runs all 35 deterministic evaluators (L1), then sends findings + source code to GPT-4o with the full tribunal deep-review prompt (L2) for contextual AI analysis — all in a single user action.
-- **`/deepreview` chat sub-command** — streams L1 findings grouped by severity with fix buttons, then streams the L2 LLM deep-review response directly in Copilot Chat. Gracefully degrades to L1-only when no LLM is available.
-- **`judges.deepReview` command** — accessible from command palette and editor context menu (🚀 icon). Runs L1 + L2 and opens the full report as a new markdown tab.
-- **Deep-review prompt builders exported from public API** — `buildSingleJudgeDeepReviewSection` and `buildTribunalDeepReviewSection` are now available via `@kevinrabun/judges/api`.
-- **10 new tests** (1220 total): deep-review intent detection (3), L1→L2 prompt construction (3), tribunal section validation (2), JUDGES array contract (1), API export accessibility (1).
-
-## [3.13.2] — 2026-03-02
-
-### Fixed
-- **5 evaluator false-positive fixes** from second round of real-world Copilot review feedback:
-  - **REL-001** (reliability) — empty catch blocks now suppressed when the file contains resilience infrastructure (circuit-breaker, retry wrappers, abort-signal helpers) indicating errors are intentionally handled at a higher abstraction layer.
-  - **SOV-001** (data-sovereignty) — broadened `hasRegionPolicy` detection to recognize `approvedJurisdictions`, `allowedJurisdictions`, `jurisdictionPolicy`, `exportPolicy`, `egressPolicy`, and `jurisdictionGuard` patterns.
-  - **SOV-003/telemetry** (data-sovereignty) — relaxed telemetry kill-switch regex: `ALLOW_EXTERNAL_TELEMETRY` is now a standalone match (no longer requires `throw|false|disabled` on the same line). Added `SovereigntyError.*telemetry` and `policy.?gate.*telemetry` patterns.
-  - **SCALE-003** (scalability) — removed generic `.sleep()` from blocking-call detection (matched async sleep helpers in retry/backoff code). Now only matches language-specific blocking sleeps (`Thread.sleep`, `time.sleep`). Lines containing `await` are also excluded.
-  - **COMP-001** (compliance) — PII-without-encryption rule now suppressed when the file has compliance infrastructure (`verifyAgeCompliance`, `requireParentalConsent`, `restrictDataCollection`, etc.). Age-verification regex also expanded to recognize `verifyAge`, `ageCompliance`, `requireParentalConsent`, `restrictDataCollection`.
-
-### Added
-- **11 new regression tests** (1246 total) covering all 5 false-positive fixes, including both negative cases (FP suppressed) and positive cases (real issues still detected).
-
-## [3.13.1] — 2026-03-02
-
-### Fixed
-- **10 evaluator false-positive fixes** from real-world Copilot review feedback:
-  - **REL-002** (reliability) — expanded timeout context window from 5 lines to ±15 lines; added file-level `AbortController`/`AbortSignal`/`signal` scan so files with centralized timeout handling are not flagged.
-  - **SOV-002** (data-sovereignty) — added egress gate detection (`assertAllowedEgress`, `egressPolicy`, `jurisdictionCheck`, etc.) to suppress cross-border findings when a guard function exists.
-  - **SOV-004** (data-sovereignty) — added centralized sovereignty response handler detection (`finalizeSovereignResponse`, `sovereigntyMiddleware`, etc.) to suppress export-path findings.
-  - **SOV-007** (data-sovereignty) — added telemetry kill-switch detection; files that throw on external telemetry enable are no longer flagged.
-  - **SOV-008** (data-sovereignty) — tightened PII partition rule to require concrete DB mutation evidence (SQL DML in query context or ORM method calls) instead of matching generic verbs like `create`/`save`.
-  - **DOC-001** (documentation) — undocumented-function rule now only flags exported/public functions. Internal helpers, private utilities, and language-specific private patterns (`_`-prefixed in Python, non-`pub` in Rust) are skipped.
-  - **A11Y form error** (accessibility) — form error ARIA rule now gated on HTML/JSX rendering evidence; pure backend files generating validation schemas are no longer flagged.
-  - **SCALE-003** (scalability) — replaced generic `*Sync(` regex with an explicit list of 30+ known Node.js synchronous blocking APIs. Custom functions like `ensureModelSync()` or `performDataSync()` are no longer flagged.
-  - **AUTH-002** (authentication) — added public endpoint marker detection (`isPublic`, `@PermitAll`, `noAuth`, `AllowAnonymous`, etc.) and health-check-only route file suppression.
-  - **DB-006** (database) — tightened mutation detection to require SQL DML in `query()`/`execute()` context or ORM method calls; function names containing `create`/`update`/`delete` no longer trigger false positives.
-
-### Added
-- **15 new regression tests** (1235 total) covering all 10 false-positive fixes, including both negative cases (FP suppressed) and positive cases (real issues still detected) for DOC-001, A11Y, SCALE-003, AUTH-002, and DB-006.
-
-## [3.13.0] — 2026-03-02
-
-### Added
-- **AI-assisted false-positive refinement** — new `Judges: Refine Findings with AI` VS Code command (context menu + command palette). Uses GPT-4o to review pattern-matched findings against source code and filter out false positives. Reports how many findings were dismissed vs confirmed.
-- **Deep-review false-positive instructions** — both single-judge and tribunal deep-review prompt builders now include a "False Positive Review" section instructing the LLM to identify and dismiss pattern findings that match string literals, function-scoped variables, nearby mitigation code, or test/example code. Dismissed findings are listed in a dedicated section and excluded from the verdict.
-- **`isStringLiteralLine()` helper** — new helper in `shared.ts` that detects lines whose content is purely a string literal value (object properties, descriptions, examples). Used by `getLineNumbers` / `getLangLineNumbers` to auto-skip string-literal lines by default, preventing false positives from example text in strings.
-- **String literal skipping in `getLineNumbers` / `getLangLineNumbers`** — both functions now skip string-literal-only lines by default (opt out with `{ skipStringLiterals: false }`). IaC languages (ARM/Terraform/Bicep) automatically opt out since their content is structured data where quoted values are meaningful.
-- **34 new tests** (1210 total across 4 test files):
-  - Deep-review single-judge prompt (8 tests) and tribunal prompt (7 tests).
-  - `isStringLiteralLine` helper (7 tests).
-  - `getLineNumbers` / `getLangLineNumbers` string literal skipping (4 tests).
-  - String literal false-positive regressions for logging-privacy and performance evaluators (2 tests).
-  - `refineWithAI` contract verification (6 tests): prompt building, index filtering, JSON array parsing.
-
-### Fixed
-- **7 evaluator false-positive fixes**:
-  - **logging-privacy** — SQL regex no longer matches `SELECT` inside string literal values.
-  - **data-sovereignty** — audit trail window scoped to function bodies instead of matching globally.
-  - **performance** — unbounded collection scope limited to actual code context; event handler and pagination checks now skip string literal lines.
-  - **internationalization** — currency regex anchored to avoid matching partial identifiers.
-  - **scalability** — global mutable state scoping improved (function-local `let`/`var` no longer flagged).
-- **IaC evaluator preserves detection in ARM templates** — `getLangLineNumbers` auto-disables string literal skipping for IaC languages so JSON key-value pairs aren't incorrectly filtered.
-
-### Changed
-- **README** — test badge updated from 925 to 1210; documented AI refinement capability.
-- **VS Code extension README** — added `Judges: Refine Findings with AI` to commands table and features list.
-
-## [3.12.0] — 2026-03-01
-
-### Added
-- **Technological sovereignty rules** — 3 new evaluator rules:
-  - **SOV-011**: Vendor-managed encryption without key sovereignty (BYOK/CMK/HSM).
-  - **SOV-012**: Proprietary AI/ML model dependency without abstraction layer.
-  - **SOV-013**: Single identity provider coupling without OIDC/SAML federation.
-- **Operational sovereignty rules** — 3 new evaluator rules:
-  - **SOV-014**: External API calls without circuit breaker / resilience patterns.
-  - **SOV-015**: Administrative operations without structured audit trail.
-  - **SOV-016**: Data storage without export / portability mechanism.
-- **3-pillar sovereignty systemPrompt** — judge definition expanded with 20 evaluation criteria across Data, Technological & Operational sovereignty pillars.
-- **13 new tests** for technological and operational sovereignty rules including comment-skipping regression (925 total tests, 190 suites).
-
-### Changed
-- **Judge name** — "Judge Data Sovereignty" → "Judge Sovereignty".
-- **Judge domain** — "Data Sovereignty & Jurisdictional Controls" → "Data, Technological & Operational Sovereignty".
-- **README** — test badge 912 → 925; Data Sovereignty row and MCP prompt expanded.
-
-## [3.11.4] — 2026-03-01
-
-### Fixed
-- **Zero lint errors** — resolved all remaining PROBLEMS across `daily-popular-repo-autofix.ts` (unused `RepoTimeoutError` class), `judges.test.ts` (9 unused imports), and `iac-security.ts` (unused post-increment value).
-- **9 new comment-skipping regression tests** — authentication, API design, dependency health, compliance, observability, testing, internationalization, documentation, and ethics-bias evaluators now have dedicated false-positive regression tests (912 total tests, 188 suites).
-
-### Changed
-- **CHANGELOG** — added missing entries for v3.8.5 through v3.11.3 with link references.
-- **README** — test badge updated from 842 to 912.
-- **CONTRIBUTING** — test count updated from 700+ to 900+.
-- **SECURITY** — supported versions table updated to reflect 3.11.x as current.
-
-## [3.11.3] — 2026-03-01
-
-### Fixed
-- **Systemic comment-skipping across all evaluators** — added `isCommentLine()` helper to `shared.ts` with `COMMENT_LINE_RE` regex. `getLineNumbers()` and `getLangLineNumbers()` now skip comment lines by default. Added 123 individual `isCommentLine` guards to `forEach`/`for` loops across 20 evaluators. 9 intentional comment checks (TODO/FIXME, linter-disable, etc.) opted out with `{ skipComments: false }`.
-- Added 10 regression tests for comment-skipping false positives (903 total tests, 188 suites).
-
-## [3.11.2] — 2026-03-01
-
-### Fixed
-- **Recursion detector** limited body scan to actual function boundaries — previously could false-positive on identically named functions elsewhere in the file.
-- **`var` in comments** no longer triggers maintainability or software-practices findings (`var oldConfig = {}` in a comment is not a code issue).
-
-## [3.11.1] — 2026-03-01
-
-### Fixed
-- **Testing evaluator** — `describe`/`it` labels and word boundaries for `HttpClient` no longer produce false positives.
-- **Data-sovereignty evaluator** — `export` embedded in identifiers and env vars no longer triggers; added word boundaries to `dr` and `replica` checks.
-- **Documentation evaluator** — walks backwards through comment body for long JSDoc blocks to avoid false-positive "missing documentation" findings.
-
-## [3.11.0] — 2026-03-01
-
-### Fixed
-- **N+1 query check** now scans actual loop bodies instead of the entire file — eliminates false positives when queries exist outside loops.
-- **Retry detection** recognizes `p-retry` and `backoff` libraries.
-- **Cost-effectiveness** skips comment lines in loop detection.
-- **Accessibility** skips comment and declaration lines.
-- **Data-sovereignty** skips comment lines.
-- **External dependency** detection skips comment lines.
-- **API doc check** no longer false-positives on large JSDoc blocks.
-
-## [3.10.1] — 2026-03-01
-
-### Fixed
-- **Auto-fix button** no longer falsely reports code changed when no patches were applied.
-
-## [3.10.0] — 2026-03-01
-
-### Added
-- **IaC Security judge** (`IAC-*` rules) — Infrastructure-as-Code analysis for Terraform (`.tf`), Bicep (`.bicep`), and ARM templates (`.json`). Checks for overly permissive network rules, missing encryption, public access, hardcoded secrets in IaC definitions, and 15 other IaC-specific anti-patterns.
-
-## [3.9.3] — 2026-03-01
-
-### Improved
-- **VS Code extension** — "Re-Evaluate" is now a chat followup that streams updated findings into chat (previously showed only a toast). Context-aware followups for `/security` and workspace reviews. Post-fix followup after `/fix`.
-- **Auto-fix clarity** — each finding tagged with 🔧 (auto-fixable) or 📝 (manual review). Fixability summary in header. Dynamic button label ("Auto-Fix N of M Findings"). Button hidden when no findings are auto-fixable.
-
-## [3.9.2] — 2026-03-01
-
-### Fixed
-- **VS Code extension** — populated findings cache directly from chat review results; fixed Auto-Fix All and Re-Evaluate buttons not working after chat review.
-
-## [3.9.1] — 2026-03-01
-
-### Added
-- **Workspace-wide review** — `@judges /review` in Copilot Chat can now evaluate all supported files in the workspace with progress reporting.
-
-### Fixed
-- **Tree-sitter AST** — made `tree-sitter-ast.ts` work in both ESM and CJS bundles.
-- Added missing `toolReferenceName` to `languageModelTools` manifest.
-
-## [3.9.0] — 2026-03-01
-
-### Added
-- **`@judges` chat participant** — type `@judges` in Copilot Chat to review, security-check, or auto-fix files. Slash commands: `/review`, `/security`, `/fix`, `/help`.
-- **`judges_evaluate` Language Model tool** — registered via `vscode.lm.registerTool` so Copilot auto-discovers and invokes Judges evaluation.
-- Disambiguation routing: Copilot auto-routes "judges panel review", "judges evaluation" queries.
-- Domain-focused reviews and action buttons in chat responses.
-
-## [3.8.7] — 2026-03-01
-
-### Fixed
-- Daily popular-repo autofix timeout and performance improvements.
-
-## [3.8.6] — 2026-03-01
-
-### Fixed
-- Added `onChatParticipant` activation event for `@judges` in VS Code extension.
-
-## [3.8.5] — 2026-03-01
-
-### Security
-- Replaced ReDoS-prone regex with `indexOf` in `project.ts` (CodeQL alert 35).
-
-## [3.8.4] — 2026-03-01
-
-### Security
-- Fixed 8 polynomial-ReDoS vulnerabilities flagged by CodeQL code scanning:
-  - `structural-parser.ts`: PYTHON_CLASS regex — merged competing `\s*` quantifiers around optional base-list group.
-  - `taint-tracker.ts`: GUARD_PATTERNS — eliminated `[ \t]*!?[ \t]*` overlap that caused polynomial backtracking.
-  - `shared.ts`: health-check pattern — bounded `[^\n]*` to `{0,200}`; catch-block signal — replaced whole-file regex with line-by-line scan.
-  - `dependencies.ts`: requirements.txt parser — replaced `[>=<~!]+` character class with explicit pip-operator alternation.
-  - `project.ts`: import-path extractor — bounded `[^'"]` quantifier to `{1,500}`; normalise helper — replaced chained regex with `lastIndexOf` calls.
-- Dismissed 6 false-positive / intentional alerts:
-  - 2 intentional vulnerabilities in `examples/sample-vulnerable-api.ts` (demo file).
-  - 4 URL-substring-sanitization false positives in test assertions.
-
-## [3.8.3] — 2026-03-01
-
-### Changed
-- Extension README: rewrote to lead with auto-configured MCP, added Marketplace install instructions, added missing commands to table, updated Layer 2 section to emphasize it is enabled automatically.
-- Extension `package.json` description updated to mention auto-configured MCP.
-- Root README: rewrote “Connect to Your Editor” section — VS Code extension is now the recommended zero-config path; manual MCP configs updated to use `npx` instead of absolute paths; added Cursor and generic MCP client examples.
-
-## [3.8.2] — 2026-03-01
-
-### Fixed
-- Added `workflow_dispatch` trigger to publish workflow for manual re-runs.
-- Fixed tag-push not triggering CI when pushed alongside branch updates.
-
-## [3.8.1] — 2026-03-01
-
-### Fixed
-- Aligned VS Code engine constraint (`^1.109.0`) with `@types/vscode` to fix vsce publish validation.
-
-## [3.8.0] — 2026-03-01
-
-### Added
-- **MCP server auto-configuration** — VS Code extension now registers the Judges MCP server automatically via `McpServerDefinitionProvider`. Users install the extension and Layer 2 (35 expert-persona LLM prompts) is immediately available to Copilot — zero manual setup.
-- **`Judges: Configure MCP Server` command** — writes the MCP server definition to `.vscode/mcp.json` for users who prefer explicit workspace config.
-- Extension engine bumped to VS Code `^1.99.0` for MCP API support.
-
-## [3.7.3] — 2026-03-01
-
-### Fixed
-- Fixed CI workflow race condition: extension install failed because `@kevinrabun/judges@^3.7.2` wasn't propagated on npm yet.
-- Workflow now uses local tarball (`npm pack`) for the extension build instead of relying on npm registry propagation.
-- Removed dependency version sync from the extension publish step; `^3.7.1` semver range covers all 3.x patches.
-
-## [3.7.2] — 2026-03-01
-
-### Fixed
-- Resolved all 168 lint warnings across 45 source files (0 errors, 0 warnings).
-- Fixed unused `lang` parameter in 25 evaluators (`lang` → `_lang`).
-- Fixed last `ruleNum++` assignment (value never read) in 34 evaluators.
-- Removed unused imports from `data-security.ts`, `evaluators/index.ts`, `negative.test.ts`, `subsystems.test.ts`.
-- Prefixed unused variables with `_` in `ai-code-safety.ts`, `v2.ts`, `patches/index.ts`, `cross-file-taint.ts`, `structural-parser.ts`, `taint-tracker.ts`.
-- Fixed unnecessary escape characters in `structural-parser.ts`, `ai-code-safety.ts`, `documentation.ts`, `shared.ts`, `software-practices.ts`.
-- Removed dead `else { ruleNum++; }` branch in `ai-code-safety.ts`.
-- All 1039 tests passing (842 + 28 + 169).
-
----
-
-## [3.7.1] — 2026-03-01
-
-### Fixed
-- Added root `LICENSE` file (MIT) — was referenced in `package.json` `files` but missing from tarball.
-- Added `CHANGELOG.md` to npm `files` array so it ships in the published package.
-- Fixed CHANGELOG date and test count accuracy.
-- VS Code extension: switched to `bundler` module resolution, fixed ESM/CJS import errors.
-- VS Code extension: added `.vscodeignore` tuning, `galleryBanner` metadata, esbuild bundling.
-
----
-
-## [3.7.0] — 2026-03-01
-
-### Added
-- **`judges --version` command** — display installed version with update check.
-- **`--fix` flag on eval** — evaluate and auto-fix in one step: `judges eval --fix src/app.ts`.
-- **Glob / multi-file eval** — evaluate directories and patterns: `judges eval src/**/*.ts`.
-- **Progress indicators** — `[1/12] src/app.ts…` progress during multi-file evaluation.
-- **VS Code extension** — diagnostics, code actions, and quick-fix integration (`vscode-extension/`).
-- **README terminal mockup** — SVG-based visual showing evaluation output.
-- **`.judgesrc.example.json`** — annotated example configuration file.
-- **GitHub Marketplace metadata** — enhanced `action.yml` for Marketplace discovery.
-
-### Changed
-- `server.json` version synced to `3.7.0`.
-- README test badge updated to **842**.
-- Total test count: **842**.
-
----
-
-## [3.6.0] — 2026-03-07
-
-### Added
-- **Plugin system** (`--plugin`) — load custom evaluator plugins from npm packages or local files.
-- **Finding fingerprints** — stable content-hash IDs for tracking findings across runs.
-- **Calibration mode** (`judges calibrate`) — tune judge thresholds against known-good codebases.
-- **Diagnostics format** (`--format diagnostics`) — LSP-compatible diagnostic output for editor integration.
-- **Comparison command** (`judges compare`) — side-by-side feature matrix vs ESLint, SonarQube, Semgrep, CodeQL.
-- **Language packs** (`judges pack`) — manage language-specific rule extensions.
-- **Config sharing** (`judges config export/import`) — export and import team configurations.
-- **Custom rules** (`judges rule create`) — define and manage custom evaluation rules.
-- **Fix history** — track applied patches with undo support.
-- **Smart output** — auto-detect terminal width and format output accordingly.
-- **Feedback command** (`judges feedback`) — submit false-positive feedback for rule tuning.
-- **Benchmark command** (`judges benchmark`) — run detection accuracy benchmarks against test suites.
-- **14 new subsystem tests** for plugins, fingerprinting, calibration, and diagnostics.
-
-### Changed
-- CLI expanded from 14 to 22 commands.
-- Output formats expanded from 7 to 8 (added `diagnostics`).
-- Total test count: **819** (up from 754).
-
----
-
-### Added
-- **`judges diff` command** — evaluate only changed lines from unified diff / git diff output. Pipe `git diff` directly or pass a patch file.
-- **`judges deps` command** — analyze project dependencies for supply-chain risks across 11 manifest types (package.json, requirements.txt, Cargo.toml, go.mod, pom.xml, etc.).
-- **`judges baseline create` command** — create a baseline JSON file from current findings for future suppression.
-- **`judges completions` command** — generate shell completion scripts for bash, zsh, fish, and PowerShell.
-- **`judges docs` command** — generate per-judge rule documentation in Markdown format, with `--output` for file output.
-- **JUnit XML formatter** (`--format junit`) — CI/CD compatible output for Jenkins, Azure DevOps, GitHub Actions, GitLab CI.
-- **CodeClimate JSON formatter** (`--format codeclimate`) — GitLab Code Quality widget compatible output with MD5 fingerprints.
-- **Named presets** (`--preset`) — 6 built-in profiles: `strict`, `lenient`, `security-only`, `startup`, `compliance`, `performance`.
-- **Config file support** (`--config`) — auto-discovers `.judgesrc` / `.judgesrc.json` in project root with full JSON Schema validation support.
-- **`judgesrc.schema.json`** — JSON Schema for `.judgesrc` files with IDE autocomplete and validation.
-- **`--min-score` flag** — exit non-zero when overall score falls below threshold (e.g. `--min-score 80`).
-- **`--verbose` flag** — timing statistics and file-level detail in output.
-- **`--quiet` flag** — suppress informational output, only show findings.
-- **`--no-color` flag** — disable ANSI color codes for piped output.
-- **CI Templates** — `judges ci-templates github` generates GitHub Actions workflow YAML.
-- **24 new tests** covering all new formatters, commands, presets, and JSON Schema validation.
-
-### Changed
-- CLI expanded from 8 to 14 commands.
-- Output formats expanded from 5 to 7 (added `junit`, `codeclimate`).
-- Total test count: **754** (up from 730).
-
----
-
-## [3.4.0] — 2026-03-04
-
-### Added
-- **Init wizard** (`judges init`) — interactive project setup generating `.judgesrc` config.
-- **Fix command** (`judges fix`) — auto-apply suggested patches from findings with `--apply` flag.
-- **Watch mode** (`judges watch`) — file-system watcher for continuous evaluation during development.
-- **Report command** (`judges report`) — full project analysis with HTML/JSON/Markdown output.
-- **Hook command** (`judges hook`) — git pre-commit hook installation.
-- **HTML formatter** — interactive browser-based report with severity filters and per-judge sections.
-- **Baseline suppression** — suppress known findings from previous runs.
-- **CI template generator** — `judges ci-templates` for GitLab CI, Azure Pipelines, Bitbucket Pipelines.
-
-### Changed
-- Total test count: **730**.
-
----
-
-## [3.3.0] — 2026-03-02
-
-### Changed
-- **Unified tree-sitter AST** — consolidated `typescript-ast.ts` into `tree-sitter-ast.ts`, single parser for all 8 languages.
-- Removed legacy TypeScript Compiler API dependency.
-
----
-
-## [3.2.0] — 2026-02-29
-
-### Added
-- **Tree-sitter WASM integration** — structural AST analysis for 8 languages (TypeScript, JavaScript, Python, Go, Rust, Java, C#, C++).
-- Language-specific structural patterns for each grammar.
-
----
-
-## [3.1.1] — 2026-02-28
-
-### Added
-- **GitHub Action** (`action.yml`) — composite action for CI/CD with SARIF upload, fail-on-findings, and job summary.
-- **Dockerfile** — multi-stage Node 20 Alpine build with non-root user for containerized usage.
-- **GitHub Pages dashboard** (`docs/index.html`) — dark-themed dashboard showing project analysis results and judge directory.
-- **Real-world evidence document** (`docs/real-world-evidence.md`) — Express.js, Flask, FastAPI analysis + before/after showcase.
-- **Pages deployment workflow** (`.github/workflows/pages.yml`).
-
----
-
-## [3.1.0] — 2026-02-28
-
-### Added
-- **CLI evaluation mode** — `npx @kevinrabun/judges eval --file app.ts` runs the full tribunal from the command line, no MCP setup required. Supports `--language`, `--format`, `--judge`, and stdin piping.
-- **Enhanced Python AST** — class-aware method extraction (`ClassName.method_name`), decorator detection, async function detection, self/cls parameter filtering, multi-line import handling.
-- **Framework-aware analysis** — detects 14 frameworks (Express, React, Django, Flask, Spring, FastAPI, etc.) and reduces confidence on framework-idiomatic findings to cut false positives.
-- **Content-hash LRU caching** — caches AST structure, taint flow, and tribunal results by content hash for faster re-evaluation of unchanged files.
-- **SARIF 2.1.0 structural validator** — `validateSarifLog()` checks all mandatory SARIF properties before output.
-- **Multi-line auto-fix patches** — 5 structural patch rules for Express helmet, CORS, rate limiting, error handlers, and health endpoints.
-- **Confidence-weighted scoring** — findings now carry estimated confidence; low-confidence findings have reduced score impact.
-- **Finding provenance** — every finding includes `provenance` field with rule ID and evidence trail for auditability.
-- **Absence-based finding demotion** — findings flagging *missing* patterns are demoted from critical/high to medium to reduce false positives.
-- **28 negative tests** for false positive prevention.
-- **169 subsystem unit tests** (scoring, dedup, config, patches, suppression, SARIF, Python parser).
-- **Quickstart example** (`examples/quickstart.ts`) using the package API.
-- **CHANGELOG.md** with full version history.
-
-### Fixed
-- `server.json` version now stays in sync with `package.json`.
-- MCP server version string updated from `2.0.0` to `3.1.0`.
-- Demo example includes guidance for both in-repo and package-installed usage.
-
-### Changed
-- Total test count: **899** (702 integration + 28 negative + 169 subsystem).
-- Python structural parser fully rewritten with two-pass class boundary detection.
-- Class name extraction added for all supported languages (Python, Java, C#, Rust, Go).
-
----
-
-## [3.0.3] — 2026-02-27
-
-### Fixed
-- Resolved all 14 CodeQL ReDoS alerts via atomic character classes and possessive-style patterns.
-- Suppressed 4 intentional vulnerability alerts in `examples/sample-vulnerable-api.ts` (test fixture).
-- Resolved Dependabot `hono` IP spoofing alert via `overrides`.
-- GitHub Releases now auto-created on tag push (`publish-mcp.yml`).
-
----
-
-## [3.0.2] — 2026-02-26
-
-### Fixed
-- Publish workflow repaired (npm provenance, correct trigger).
-- Removed dead code from build artifacts.
-
----
-
-## [3.0.1] — 2026-02-26
-
-### Fixed
-- Dropped Node 18 from CI matrix (ESLint 10 requires Node >= 20).
-- Added adversarial mandate to code-structure and framework-safety judges.
-- Fixed `FW-` rule prefix in README documentation.
-
----
-
-## [3.0.0] — 2026-02-25
-
-### Added
-- **Monolith decomposition**: 35 specialized judges split from single evaluator file.
-- **Built-in AST analysis** via TypeScript Compiler API — no separate parser needed.
-- **App Builder Workflow** (3-step): release decision, plain-language risk summaries, prioritized remediation tasks.
-- **V2 context-aware evaluation** with policy profiles, evidence calibration, specialty feedback, confidence scoring.
-- **Public repository URL reporting** — clone any public repo and generate a full tribunal report.
-- **Project-level analysis** with cross-file architectural detection (duplication, dependency cycles, god modules).
-- **Diff evaluation** — analyze only changed lines for PR reviews.
-- **Dependency analysis** — supply-chain manifest scanning.
-- **SARIF output** for GitHub Code Scanning integration.
-- **Inline suppression** via `judges-disable` comments.
-- CI/CD infrastructure with GitHub Actions (CI, publish, PR review, daily automation).
-
----
-
-## [2.3.0] — 2026-02-24
-
-### Added
-- AI Code Safety judge with 12 AICS rules.
-- Full `suggestedFix` and `confidence` coverage across all 427 findings.
-- Multi-language detection via language pattern system.
-
----
-
-[3.11.4]: https://github.com/KevinRabun/judges/compare/v3.11.3...v3.11.4
-[3.11.3]: https://github.com/KevinRabun/judges/compare/v3.11.2...v3.11.3
-[3.11.2]: https://github.com/KevinRabun/judges/compare/v3.11.1...v3.11.2
-[3.11.1]: https://github.com/KevinRabun/judges/compare/v3.11.0...v3.11.1
-[3.11.0]: https://github.com/KevinRabun/judges/compare/v3.10.1...v3.11.0
-[3.10.1]: https://github.com/KevinRabun/judges/compare/v3.10.0...v3.10.1
-[3.10.0]: https://github.com/KevinRabun/judges/compare/v3.9.3...v3.10.0
-[3.9.3]: https://github.com/KevinRabun/judges/compare/v3.9.2...v3.9.3
-[3.9.2]: https://github.com/KevinRabun/judges/compare/v3.9.1...v3.9.2
-[3.9.1]: https://github.com/KevinRabun/judges/compare/v3.9.0...v3.9.1
-[3.9.0]: https://github.com/KevinRabun/judges/compare/v3.8.7...v3.9.0
-[3.8.7]: https://github.com/KevinRabun/judges/compare/v3.8.6...v3.8.7
-[3.8.6]: https://github.com/KevinRabun/judges/compare/v3.8.5...v3.8.6
-[3.8.5]: https://github.com/KevinRabun/judges/compare/v3.8.4...v3.8.5
-[3.8.4]: https://github.com/KevinRabun/judges/compare/v3.8.3...v3.8.4
-[3.8.3]: https://github.com/KevinRabun/judges/compare/v3.8.2...v3.8.3
-[3.8.2]: https://github.com/KevinRabun/judges/compare/v3.8.1...v3.8.2
-[3.8.1]: https://github.com/KevinRabun/judges/compare/v3.8.0...v3.8.1
-[3.8.0]: https://github.com/KevinRabun/judges/compare/v3.7.3...v3.8.0
-[3.7.3]: https://github.com/KevinRabun/judges/compare/v3.7.2...v3.7.3
-[3.7.2]: https://github.com/KevinRabun/judges/compare/v3.7.1...v3.7.2
-[3.7.1]: https://github.com/KevinRabun/judges/compare/v3.7.0...v3.7.1
-[3.7.0]: https://github.com/KevinRabun/judges/compare/v3.6.0...v3.7.0
-[3.6.0]: https://github.com/KevinRabun/judges/compare/v3.5.0...v3.6.0
-[3.5.0]: https://github.com/KevinRabun/judges/compare/v3.4.0...v3.5.0
-[3.4.0]: https://github.com/KevinRabun/judges/compare/v3.3.0...v3.4.0
-[3.3.0]: https://github.com/KevinRabun/judges/compare/v3.2.0...v3.3.0
-[3.2.0]: https://github.com/KevinRabun/judges/compare/v3.1.1...v3.2.0
-[3.1.1]: https://github.com/KevinRabun/judges/compare/v3.1.0...v3.1.1
-[3.1.0]: https://github.com/KevinRabun/judges/compare/v3.0.3...v3.1.0
-[3.0.3]: https://github.com/KevinRabun/judges/compare/v3.0.2...v3.0.3
-[3.0.2]: https://github.com/KevinRabun/judges/compare/v3.0.1...v3.0.2
-[3.0.1]: https://github.com/KevinRabun/judges/compare/v3.0.0...v3.0.1
-[3.0.0]: https://github.com/KevinRabun/judges/compare/v2.3.0...v3.0.0
-[2.3.0]: https://github.com/KevinRabun/judges/releases/tag/v2.3.0