feat(vscode): ship Compass 0.1.9 architecture flow and CLI onboarding - #81
Merged
Conversation
…ph-resolution # Conflicts: # .github/workflows/compass-ci.yml # crates/compass-output/assets/viewer/graph.js # crates/compass-output/assets/viewer/manifest.json # crates/compass-output/assets/viewer/viewer.css # docs/superpowers/plans/2026-07-27-compass-code-graph-v1.md # docs/superpowers/specs/2026-07-27-compass-code-graph-v1-design.md # editors/vscode/CHANGELOG.md # editors/vscode/package.json # editors/vscode/src/cli/processManager.test.ts # editors/vscode/src/cli/processManager.ts # packages/compass-viewer/package.json # packages/compass-viewer/src/index.ts # scripts/install.ps1
forhappy
marked this pull request as ready for review
July 30, 2026 14:46
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
compass.viewer.callflow/1schema with no runtime legacy normalization or/2acceptanceWhy
Large repositories could exceed the shared 8 MiB stdout limit, while sending an equally large payload directly into the webview would make the UI sluggish. The prior aggregate relationship presentation also hid individual caller/callee evidence and produced a difficult-to-read architecture graph. Contract drift between schema v1 and v2 could prevent the extension from opening the flow entirely.
This change gives architecture export its own bounded capture ceiling, keeps the complete model in the extension host, and sends only searchable, paged projections to the webview. The map prioritizes important routes for a comfortable overview without removing access to the complete architecture. It also establishes one strict v1 contract across capability negotiation, export, validation, and rendering.
User impact
Validation