docbridge 0.4.1 → 0.5.0

package/CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.0] - 2026-07-05
+
+### Added
+
+- VS Code-compatible extension packaging and manual publishing support:
+  release VSIX generation, VSIX verification, Marketplace/Open VSX publish
+  commands, Swift/Dart document activation, and bundled `docbridge lsp`
+  startup from the extension package.
+
+### Fixed
+
+- The release publish workflow now restores executable bits on downloaded
+  Swift and Dart scanner artifacts before packing the npm tarball, and
+  smoke-tests the installed tarball before publishing.
+
+### Changed
+
+- Clarified the current editor delivery state in the English and Japanese
+  READMEs, including local VSIX installation and the remaining first-publication
+  work for VS Code Marketplace and Open VSX.
+
 ## [0.4.1] - 2026-06-21
 
 ### Added
@@ -149,7 +170,8 @@ Initial release of the SpecLink CLI.
 - `speclink check` command with `--root`, `--json`, and `--audit` options.
 - `speclink --version` (alias `-v`) and `speclink --help` (alias `-h`).
 
-[Unreleased]: https://github.com/salan70/docbridge/compare/v0.4.1...HEAD
+[Unreleased]: https://github.com/salan70/docbridge/compare/v0.5.0...HEAD
+[0.5.0]: https://github.com/salan70/docbridge/releases/tag/v0.5.0
 [0.4.1]: https://github.com/salan70/docbridge/releases/tag/v0.4.1
 [0.4.0]: https://github.com/salan70/docbridge/releases/tag/v0.4.0
 [0.3.0]: https://github.com/salan70/docbridge/releases/tag/v0.3.0

package/README.md

@@ -21,8 +21,8 @@ bunx docbridge check
 ```
 
 The current release is
-[v0.4.0](https://github.com/salan70/docbridge/releases/tag/v0.4.0), published
-as `docbridge@0.4.0` on npm.
+[v0.5.0](https://github.com/salan70/docbridge/releases/tag/v0.5.0), published
+as `docbridge@0.5.0` on npm.
 
 The npm package is Bun-only; Node.js runtime compatibility is not part of the
 initial distribution. The package includes prebuilt Swift and Dart scanner
@@ -300,9 +300,25 @@ Definition, and References across linked code and Markdown. It takes no
 options; the project root comes from the editor's `initialize` request.
 `docbridge check` is unchanged.
 
-A minimal VS Code-compatible client lives in [editors/vscode](editors/vscode);
-see its README to install it into VS Code or Cursor for local testing. Full
-behavior is specified in [docs/specs/lsp.md](docs/specs/lsp.md).
+A VS Code-compatible extension lives in [editors/vscode](editors/vscode). It
+packages the language server into a VSIX for VS Code and Cursor. The extension
+has not yet been published to VS Code Marketplace or Open VSX. Until the first
+registry publication, stage the supported `dist/bin/darwin-arm64` and
+`dist/bin/linux-x64` scanner artifacts, then build and install the VSIX
+locally:
+
+```sh
+just package-vsix
+just verify-vsix
+```
+
+Install the generated file from `editors/vscode/.tmp/out/` with **Extensions:
+Install from VSIX...** in VS Code or Cursor. The first Marketplace and Open VSX
+publication is intentionally manual; the repository provides publish commands
+for that release process. Zed integration is tracked separately and is not yet
+implemented. MCP delivery is out of scope until a concrete consumer requires a
+long-lived tool server. Full LSP behavior is specified in
+[docs/specs/lsp.md](docs/specs/lsp.md).
 
 ## Diagnostics
 
@@ -453,14 +469,15 @@ inside their worker packages.
 
 ## Roadmap
 
-Completed v0.1–v0.4 capabilities are documented above and in
-[CHANGELOG.md](CHANGELOG.md). The current roadmap tracks upcoming work only.
+Completed v0.1–v0.5 capabilities are documented above and in
+[CHANGELOG.md](CHANGELOG.md).
 
-v0.5:
+Remaining editor delivery work:
 
-- MCP server exposing the link graph and `docbridge context` output as tools
-- Editor and agent delivery channels built on it (Claude Code, Cursor, Zed,
-  Codex)
+- Publish the first verified VSIX to VS Code Marketplace and Open VSX
+- Follow-up automation for GitHub Release VSIX attachment and registry
+  publishing after the manual flow is proven
+- Add a separate Zed integration path
 
 ## Vision
 

package/dist/bin/darwin-arm64/SHA256SUMS

@@ -1,2 +1,2 @@
-a2ec141fe5b365958bf3d7cceb5938b4b0e0acf0227791dce08a627a1b17e541  speclink-swift-scanner
-459d9e21cd1479c3604c9567ba38c1a59959e70578d52e853f7a591e666428a6  speclink_dart_scanner
+399b29c29ad2878ca2a2c44b8a3b0685340bfd491b47ae9dcda7fda441e27ef4  speclink-swift-scanner
+a93886519edfd9a7f9aa83d627cc62a6141cd57675bbd554c41e567ce7105d11  speclink_dart_scanner

package/dist/bin/linux-x64/SHA256SUMS

@@ -1,2 +1,2 @@
-14b5284afd5387b0734832b35585f6b72945b6eef0642075bb68e1343fb1965d  speclink-swift-scanner
+a0994f4ffe305736e5c7263c3220fa23d2f5b74b7288a965f5e69d5d763c2381  speclink-swift-scanner
 2145eac2afd09696ced849e0196a2557d6f7041224f13da1d5ef21c552ecf7bc  speclink_dart_scanner

package/dist/index.js

@@ -168760,7 +168760,7 @@ import { resolve as resolve4 } from "path";
 // package.json
 var package_default = {
   name: "docbridge",
-  version: "0.4.1",
+  version: "0.5.0",
   description: "A Bun CLI that links Markdown specifications and code declarations.",
   license: "MIT",
   type: "module",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docbridge",
-  "version": "0.4.1",
+  "version": "0.5.0",
   "description": "A Bun CLI that links Markdown specifications and code declarations.",
   "license": "MIT",
   "type": "module",