Skip to content

release: v3.0.0 — VS Code extension + full editor integration#79

Merged
corvid-agent merged 4 commits intomainfrom
feat/vscode-extension-mvp
Mar 31, 2026
Merged

release: v3.0.0 — VS Code extension + full editor integration#79
corvid-agent merged 4 commits intomainfrom
feat/vscode-extension-mvp

Conversation

@corvid-agent
Copy link
Copy Markdown
Collaborator

Summary

  • VS Code extension v1.0.0 — first-class editor integration with inline diagnostics, CodeLens quality scores, coverage/scoring webviews, status bar indicator, and validate-on-save
  • CLI bumped to v3.0.0 — major version to reflect the extension as a new surface area
  • Docs updated — README gains a full VS Code Extension section, CHANGELOG has detailed v3.0.0 notes, SCOPE.md updated to v3, GitHub Action refs bumped to @V3

What's in the extension

Feature Description
Inline diagnostics Errors/warnings from specsync check --json mapped to spec files
CodeLens scores Quality scores (0–100 with letter grades) inline above specs
Coverage webview Rich HTML report with file + LOC coverage
Scoring webview Per-spec quality breakdown with suggestions
Status bar Persistent pass/fail/error/syncing indicator
Validate-on-save 500ms debounced automatic validation
5 commands Check, Coverage, Score, Generate, Init via Command Palette

Verification

  • ✅ 74 integration tests passing
  • ✅ Clippy clean (zero warnings)
  • ✅ Extension typechecks clean (tsc --noEmit)
  • ✅ Extension bundles successfully (17kb output)

Test plan

  • Install extension in VS Code and verify activation on workspace with specsync.json
  • Run each of the 5 commands from Command Palette
  • Verify diagnostics appear on spec files after save
  • Verify CodeLens scores display on .spec.md files
  • Test coverage and scoring webview reports render correctly
  • Verify status bar shows correct state after check runs
  • Test with specsync.binaryPath pointed to a custom location

🤖 Generated with Claude Code

corvid-agent and others added 3 commits March 30, 2026 16:46
- CLI JSON errors now include spec path prefix (e.g. "specs/foo.spec.md: error")
  so diagnostics map to the correct file in the Problems panel
- Score cache invalidates on check (was stale until restart)
- init command no longer gets spurious --json flag
- Icon converted from SVG to PNG (required for vsce packaging)
- parseDiagnostic regex now handles any *.spec.md path prefix

All 193 tests pass (119 unit + 74 integration).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Bump CLI to 3.0.0, extension to 1.0.0. Add VS Code extension section
to README, update CHANGELOG with full v3.0.0 notes, update SCOPE.md
to v3, and bump GitHub Action refs from @v2 to @V3.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add dedicated docs/vscode-extension.md page (nav_order 5) with full
  feature docs, commands, settings, troubleshooting
- Bump nav_order on github-action, ai-agents, architecture pages
- Add CLI binary detection at extension startup — shows actionable error
  with "Install Instructions" and "Open Settings" buttons when specsync
  binary is not found (ENOENT)
- Add ENOENT handling in runSpecsyncRaw for clear error messages
- Add PHP and Ruby multi-language integration tests (76 total, was 74)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@corvid-agent corvid-agent force-pushed the feat/vscode-extension-mvp branch from 021196b to b9c61dc Compare March 30, 2026 23:46
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@corvid-agent corvid-agent merged commit f70cf09 into main Mar 31, 2026
9 checks passed
@corvid-agent corvid-agent deleted the feat/vscode-extension-mvp branch March 31, 2026 00:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant