Ship CodeClone 2.0.0b4 with first-class MCP, VS Code, Claude, and Codex surfaces#19
Merged
Ship CodeClone 2.0.0b4 with first-class MCP, VS Code, Claude, and Codex surfaces#19
Conversation
…d UX semantics - add canonical `metrics.families.god_modules` as a report-only layer and surface it in JSON, CLI, HTML, and MCP without affecting health, gates, or findings - tighten findings vs suggestions semantics for low-signal structural hints and keep action guidance inline where separate suggestions add no real value - align CLI and HTML scope/inventory presentation with canonical report semantics and polish overview/God Modules rhythm - add dedicated Health Score documentation, clarify phased health-model expansion, and document unified metrics-baseline behavior - refresh MCP guidance/help wording and GitHub issue templates for the current b4 surface
…ument it as a first-class surface - add a native VS Code client over codeclone-mcp with baseline-aware, triage-first structural review and guided source-first drill-down - stabilize extension lifecycle and setup UX with local launcher verification, fallback connection handling, review-focused hotspots, and human-readable command surfaces - add CodeClone-native branding and marketplace-ready packaging assets, including a proper extension icon and validated .vsix packaging - document the new VS Code interface across README, docs, contracts book, changelog, and issue-routing guidance - update AGENTS.md to reflect the VS Code extension as a public surface and align validation/module-routing rules with the current codebase
…lass contract - mature the preview VS Code extension into a safer, enterprise-grade MCP client with limited Restricted Mode, source-first review flow, persisted focus state, bounded transport handling, and a safer local HTML bridge - add extension-side regression coverage with Node unit tests, local extension-host smoke, and validated preview VSIX packaging - document the extension consistently across README, docs, the contracts book, changelog, and AGENTS with its current capabilities, design decisions, trust model, and limits
…uncher/runtime handling, and tested review workflows
… the VS Code surface
…de extension lifecycle - add conservative, deeper-review, and custom analysis profiles to the VS Code extension and pass them through to CodeClone MCP - improve review UX with clearer analysis-depth affordances, conservative-first guidance, and profile-aware overview/session state - harden extension lifecycle and resource handling with safer shutdown, single-flight MCP connection reuse, and cleanup of workspace/session state - expand extension-side regression coverage and refresh VS Code extension docs to match the current behavior
…d tighten MCP guidance - implement the audit-driven cleanup across baseline/cache/report/html internals with shared JSON IO, safer normalization and path handling, and cleaner structural rendering boundaries - remove safe non-golden structural and clone noise surfaced by stricter analysis passes without touching golden fixture debt - strengthen MCP semantics with conservative-first threshold guidance, the new analysis_profile help topic, and tighter workflow/help wording - refresh core docs and contract tests for baseline, report, MCP, and stricter analysis behavior
…nline stub and update baseline
…de bundle startup flow
…r b4 - make MCP initialize metadata report the CodeClone package version so clients can enforce runtime compatibility correctly - harden the VS Code extension with a minimum supported CodeClone gate, uv-based setup guidance, moved-view icons, titled quick picks, and leaner editor actions aligned with current VS Code UX guidance - improve the Claude Desktop bundle startup path and launcher handling, with refreshed tests and packaging flow - refresh README, MCP/client docs, changelog, and related CI-facing metadata around the current VS Code, Claude, and Codex surfaces
…d marketplace readiness - make unsupported CodeClone runtime errors explain which launcher the extension resolved and whether it came from the workspace, explicit settings, PATH, or repo-local uv fallback - document that auto launcher resolution prefers the current workspace virtualenv before falling back to PATH - fix source reveal for clone review by hydrating canonical finding detail when summary locations are range-truncated, so block and segment findings reveal the full span instead of only the first line - bump the preview VS Code extension to 0.2.1, refresh packaged metadata, and add the live Marketplace listing across the repo and extension docs
🔬 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
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
This PR releases
2.0.0b4.Compared with
2.0.0b3, this beta adds report-onlyOverloaded Modules, makes MCP more guided and cheaper for agents, and ships first-class client surfaces for VS Code, Claude Desktop, and Codex.Included
overloaded_modulesacross report formats, MCP, and the VS Code extensionhelp(topic=...)and explicit conservative-firstanalysis_profileguidanceinitialize.serverInfo.versionso clients see the real CodeClone version.mcpbbundle over the same localcodeclone-mcpserver