release: cut v3.8.5 (dual-audience output)

Author: flamehaven01

CHANGELOG.md

@@ -11,6 +11,33 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [3.8.5] - 2026-06-07 — Dual-Audience Output (Plain for Humans, Actionable for Machines)
+
+### Changed
+
+- **Human summary hides internal algorithm names.** The Project Summary
+  coherence row no longer leaks `vr_structural (exact MST)`; it now reads
+  `Structure Coherence: 85% (Higher is more cohesive)` with a plain coverage
+  note (`full` / `sampled (large project)`) across the rich, text, and markdown
+  renderers. Centralized in `renderer_glossary.coherence_display()` (OSOT).
+
+### Added
+
+- **Machine output is now patch-complete (AI-agent friendly).** Project-level
+  JSON / agent route / MCP output gains two additive keys:
+  - `next_steps` — the same deterministic, prioritized action plan humans see
+    (top concern, recommended sweep command, file to start with).
+  - `metric_guide` — per-metric `value` / healthy `direction` / plain `means`,
+    so an agent reading JSON gets the same semantics as a human reader.
+
+### Notes
+
+- The JSON `coherence_level` value (`vr_structural` / `vr_structural_approx`)
+  is unchanged — only the human-facing label was translated. New keys are
+  additive and backward-compatible; no existing key was renamed or removed.
+
+---
+
 ## [3.8.4] - 2026-06-07 — Plain-Language Documentation Entry Point
 
 ### Changed

README.md

@@ -23,10 +23,10 @@ Catches what a normal linter passes over: empty functions with real-looking bodi
 </p>
 
 **Release track**
-- Stable tag: `v3.8.4`
-- Previous stable tag: `v3.8.3`
-- `v3.8.3` adds human-friendly metric output (value / healthy direction / what it means + deficit bands), deterministic Next Steps, and the VS Code webview surfaces; fixes dead-code semantics, adaptive-init config preservation, and `unused-deps` stdlib / dev-tool false positives.
+- Stable tag: `v3.8.5`
+- Previous stable tag: `v3.8.4`
 - `v3.8.4` rewrites the documentation entry point in plain language (benefit-first README, "Why Not Just Use a Linter?" / "When NOT to Use This" sections, an acronym glossary in HOW_IT_WORKS, plain-meaning comments in CONFIGURATION) without changing any code or contracts.
+- `v3.8.5` makes output dual-audience: the human summary hides internal algorithm names (no more `vr_structural (exact MST)`), while the JSON / agent / MCP output gains `next_steps` and `metric_guide` so AI agents receive the same actionable plan and metric semantics. JSON `coherence_level` is unchanged; new keys are additive.
 
 ---
 

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ai-slop-detector"
-version = "3.8.4"
+version = "3.8.5"
 description = "Evidence-based static analyzer for detecting AI-generated code quality issues with context-aware validation"
 authors = [
     {name = "Flamehaven Labs", email = "info@flamehaven.space"}

src/slop_detector/__init__.py

@@ -2,7 +2,7 @@
 
 from typing import Any
 
-__version__ = "3.8.4"
+__version__ = "3.8.5"
 __author__ = "Flamehaven Labs"
 __email__ = "info@flamehaven.space"
 

vscode-extension/package.json

@@ -2,7 +2,7 @@
   "name": "vscode-slop-detector",
   "displayName": "AI SLOP Detector",
   "description": "Real-time AI-generated code quality analysis for VS Code",
-  "version": "3.8.4",
+  "version": "3.8.5",
   "publisher": "Flamehaven",
   "engines": {
     "vscode": "^1.80.0"