Ship CodeClone 2.0.0b5 with coverage-aware metrics and baseline-honest review surfaces#21
Merged
Ship CodeClone 2.0.0b5 with coverage-aware metrics and baseline-honest review surfaces#21
Conversation
- add compact MCP interpretation fields for health_scope, focus, and new_by_source_kind across summary, production triage, and changed-scope projections - make the VS Code extension explain repository-wide health, production focus, outside-focus debt, and new-finding source-kind attribution more clearly without widening the review flow - bump the preview VS Code extension to 0.2.2 and record the UX clarification pass in its changelog
- add compact MCP interpretation fields for health_scope, focus, and new_by_source_kind across summary, production triage, and changed-scope projections - make the VS Code extension explain repository-wide health, production focus, outside-focus debt, and new-finding source-kind attribution more clearly without widening the review flow - bump the preview VS Code extension to 0.2.2 and record the UX clarification pass in its changelog
…cal, and align CI policy
…ema-aware storage
- join external Cobertura coverage.xml into current-run metrics using stdlib XML parsing - surface coverage join facts consistently in CLI, reports, MCP, SARIF, and HTML - distinguish measured coverage hotspots from coverage scope gaps in canonical findings - add project-level golden_fixture_paths policy and carry excluded clone groups as suppressed report facts - surface suppressed golden fixtures in Clones UI/CLI without affecting health or gates - fix cached segment projection branch behavior and benchmark/cache regressions - preserve cached public API parameter order and keep warm/cold API diffs stable - bump canonical report schema and refresh docs, MCP contracts, and regression tests
… metrics - remove typing_coverage/docstring_coverage toggles from CLI, pyproject config, runtime plumbing, and docs - always collect adoption facts in metrics mode and keep unified metrics baselines writing adoption snapshots - surface Coverage Join facts in the VS Code overview and gate the optional coverage help topic by server version - harden the VS Code Coverage Join path against null metrics payloads and add formatter regression coverage - sync Claude Desktop and Codex plugin guidance with canonical coverage/adoption/API MCP surfaces - refresh HTML quality/clones/dead-code/dependencies presentation with shared stat-card summaries - update repo pyproject and contract/docs/tests to match the simplified metrics model
- neutralize repo quality gates in benchmark runs - resolve pyproject baseline paths from the analysis root - treat --api-surface as a metrics-mode request - refresh CLI regressions and targeted coverage tests - document relative baseline path resolution
…badges - make cache analysis-profile compatibility aware of api-surface collection - bump cache schema to 2.5 and propagate collect_api_surface through CLI and MCP cache setup - add regressions for warm-cache api-surface runs and profile mismatch handling - unify provenance modal chips under one badge UI and remove mixed status/bool badge styles - polish report cards, typography, mobile wrapping, and hover treatment - add Findings intro banner and fix dead-code suppressed summary count - sync cache contract docs, AGENTS version table, changelog, and HTML tests
- include threshold_context in empty complexity, coupling, and cohesion check payloads - report measured_units and highest_below_threshold from canonical metric families - distinguish run finding thresholds from explicit requested_min filters - document the compact MCP response hint for agent-oriented triage - cover empty-check and requested-min cases with focused MCP tests
🔬 CodeClone Report
Findings🤖 Generated by CodeClone |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ship
2.0.0b5as the nextv2beta milestone.This release expands the canonical report with adoption, API-surface, and coverage-join layers, tightens cache and baseline-aware runtime behavior, and brings the MCP/HTML/client surfaces into closer agreement with the core contracts.
Highlights
coverage_adoption,api_surface, andcoverage_joinmetrics/report layersgolden_fixture_pathsto exclude intentional fixture clone groups from health/gates while preserving them as suppressed factsCache 2.5) and keep warm/cold API behavior honestValidation
uv run pytest --cov=codeclone --cov-report=term-missing --cov-fail-under=99 -quv run pre-commit run --all-filesuv run --with mkdocs --with mkdocs-material mkdocs build --strict.vsixpackaging.mcpbbuildNotes
coverage_joinremains a current-run external signal, not baseline truthgolden_fixture_pathsaffects health/gates only for fully matching fixture clone groups; suppressed facts remain visible in the canonical report