Repository navigation
feat: inventory VS Code project scope without client execution - #337
Merged
Merged
Conversation
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.
mcpm scopepreviously covered Claude Code only. Add an explicit--client vscodeprofile that inventories four fixed VS Code/Copilot sources and instruction metadata, while preserving the default Claude Code result.The inventory keeps source origins and JSON/JSONC/bare-map formats separate, reports duplicate names without choosing a winner, and exposes incomplete inputs without commands, values, instruction contents, client execution or writes. Completion choices and the public usage skill are updated. This is the bounded VS Code slice of backlog #141; broader host/profile/workspace coverage remains open.
Validation:
The hosted candidate matrix twice reached its 120-second outer deadline after 131 and 135 passing cases, leaving eight and four cases unrun. Preserve both as failed/incomplete attempts; increase only that outer budget to 180 seconds for the 139-case suite. The existing launcher regression still requires timeout exit 124, SIGKILL, container kill before evidence export and cleanup; per-case deadlines and assertions are unchanged.
Astra independently reviewed the implementation and evidence. Confirmed malformed-neighbor parsing and receipt identity/diagnostic-causality issues were reproduced, fixed and regression checked. Relevant docs, public skill and Obsidian are updated.
Native proof covers the Linux default-profile path and editor syntax only. Selected profile, forwarding, MCP activation and enforcement remain unknown; macOS/Windows native behavior, provider/model calls and real profiles were not tested. The native editor uses
--no-sandboxand disabled Workspace Trust inside the outer container, so this does not establish those native security controls. The pinned Tart tool failed its startup/signature check; no VM or security bypass was used.Maintenance PRs #329/#330 were reviewed separately and remain open. #331 is untouched. No merge or release is included.
All nine checks passed on final reviewed head
bd8aaf3bcf920872b0e06d43da9b6bcbb8650d9d(CI run). The fresh local matrix also passed all 139 comparisons after the budget fix, with independent runtime/lock/harness readback and 104 retained captures replayed.