DavidBakerEffendi · Oct 9, 2026 · Oct 9, 2026
diff --git a/README.md b/README.md
@@ -6,7 +6,7 @@ standalone Bifrost language server. It contains the independent Rust
 the extension and its release workflows. The extension remains published as
 `brokk/bifrost-vscode` on Open VSX.
 
-The current published extension release from this repository is `0.12.0`.
+The current extension version from this repository is `0.12.1`.
 Extension versions, standalone server versions,
 and compatible Bifrost engine versions are intentionally independent. Release
 qualification injects the server version and SHA-256 hashes into the VSIX.

diff --git a/RELEASING.md b/RELEASING.md
@@ -8,9 +8,8 @@
 - `bifrost.engineCompatibility`: documented engine protocol compatibility; it
   does not select a release artifact.
 
-The first extension release here is 0.12.0 because 0.11.4 is already published.
-This preserves continuity without making the unsupported stability claim implied
-by 1.0.0.
+The first extension release here was 0.12.0. This preserves continuity without
+making the unsupported stability claim implied by 1.0.0.
 
 ## Release tag
 
@@ -23,7 +22,7 @@ vscode-v<extension>__server-v<server>__min-v<minimum>
 ```
 
 For example, the current manifest would use
-`vscode-v0.12.0__server-v0.1.1__min-v0.1.1`. Each field must be a complete
+`vscode-v0.12.1__server-v0.1.1__min-v0.1.1`. Each field must be a complete
 semantic version. The workflow checks out the tag and rejects it unless all
 three values exactly match the committed manifest. Do not create a tag until
 the corresponding standalone `v<server>` GitHub release contains every
@@ -83,7 +82,7 @@ an enforcing extension release.
 ## Server build and release
 
 The standalone server version is `0.1.1`, independent of the extension version
-`0.12.0` and the linked Bifrost engine `0.13.0`. All Bifrost dependencies are
+`0.12.1` and the linked Bifrost engine `0.13.0`. All Bifrost dependencies are
 exact public crates.io pins. Default builds must use the committed registry
 lockfile without `.cargo/local-engine.toml` or a sibling engine checkout.
 
@@ -123,7 +122,7 @@ Release in this order:
 2. Create an annotated `v0.1.1` server tag at the qualified commit and run the
    server release workflow. Verify all five assets and checksum sidecars exist.
 3. Create the extension tag
-   `vscode-v0.12.0__server-v0.1.1__min-v0.1.1`. Its workflow injects hashes from
+   `vscode-v0.12.1__server-v0.1.1__min-v0.1.1`. Its workflow injects hashes from
    the server release into the qualified VSIX before publication.
 4. Verify both marketplace copies against the qualified VSIX, then install in
    a clean editor profile and smoke the managed download, LSP initialize,

diff --git a/docs/lsp.md b/docs/lsp.md
@@ -21,7 +21,7 @@ language server is a separate program named `bifrost-lsp`. It comes from the
 `bifrost-lsp` server gives you two working options:
 
 - In VS Code or Cursor, use the extension's managed `bifrost-lsp` v0.1.1
-  download when using extension version 0.12.0. See [VS Code LSP](./vscode.md).
+  download when using extension version 0.12.1. See [VS Code LSP](./vscode.md).
 - In another editor, start the `bifrost-lsp` v0.1.1 binary with
   `bifrost-lsp --root <workspace-root>`.
 
@@ -93,7 +93,7 @@ Three version numbers are independent of each other:
 
 | Version | Where it comes from | Current value in the bifrost-lsp source |
 | --- | --- | --- |
-| Extension version | The VS Code extension's `version` | `0.12.0` |
+| Extension version | The VS Code extension's `version` | `0.12.1` |
 | Server version | The `bifrost-lsp` release tag, `v<server>` | Preferred `0.1.1`, minimum `0.1.1` |
 | Engine version | The Bifrost analysis engine built into `bifrost-lsp` | The extension accepts `>=0.13.0 <0.14.0` |
 

diff --git a/docs/rql-vscode.md b/docs/rql-vscode.md
@@ -10,7 +10,7 @@ language for structural `query_code` searches.
 > [!CAUTION]
 > **Most RQL features need the language server**
 > Bifrost built after release 0.12.0 does not serve LSP, and the new `bifrost-lsp`
-> server v0.1.1 is released. Extension version 0.12.0 downloads and runs it.
+> server v0.1.1 is released. Extension version 0.12.1 downloads and runs it.
 > See [LSP Server](./lsp.md) and
 > [VS Code LSP](./vscode.md).
 

diff --git a/docs/vscode.md b/docs/vscode.md
@@ -6,7 +6,7 @@ Install the Bifrost VS Code extension, and look up its launch modes, settings, c
 > **The language server moved to bifrost-lsp**
 > Bifrost built after release 0.12.0 does not serve LSP: `bifrost --lsp` exits with an
 > error. The separate `bifrost-lsp` v0.1.1 server is released. Extension
-> version 0.12.0 downloads and manages that server. See
+> version 0.12.1 downloads and manages that server. See
 > [LSP Server](./lsp.md) for the full status.
 
 ## Install
@@ -17,10 +17,10 @@ from the
 or [Open VSX](https://open-vsx.org/extension/brokk/bifrost-vscode). The
 extension needs VS Code 1.90 or newer.
 
-The current published extension version is 0.12.0. It uses standalone server
-version 0.1.1. The rest of this page describes version 0.12.0.
+The current extension version is 0.12.1. It uses standalone server
+version 0.1.1. The rest of this page describes version 0.12.1.
 
-Version 0.12.0 also checks the server's identity after it starts. The server
+Version 0.12.1 also checks the server's identity after it starts. The server
 must report LSP protocol `1` and a Bifrost engine version from `0.13.0` up to,
 but not including, `0.14.0`. Otherwise the extension stops the server. See
 [LSP Server](./lsp.md) for the check and the release files.
@@ -47,7 +47,7 @@ A local development build is `target/debug/bifrost-lsp` or
 extension's own folder. The extension uses the newer of the two. This applies
 only when you run the extension from a source checkout.
 
-In version 0.12.0, the manifest default for `bifrost.serverPath` is
+In version 0.12.1, the manifest default for `bifrost.serverPath` is
 `bifrost-lsp`. `auto` mode also treats the legacy `bifrost` value as a default
 command name and selects the standalone server. In `path` mode, the extension
 uses the configured value verbatim, so set `bifrost.serverPath` to the absolute
@@ -171,7 +171,7 @@ the features that need a running server.
 
 ## Workspace .gitignore
 
-In version 0.12.0, the extension checks the workspace `.gitignore` for a line
+In version 0.12.1, the extension checks the workspace `.gitignore` for a line
 that ignores all of `.bifrost`. If it finds one, it offers to replace that line
 with `.bifrost/cache/`, so that project files under `.bifrost/` can be
 committed. You can choose **Replace**, **Ask Again Later**, or **Don't Ask

diff --git a/editors/vscode/CHANGELOG.md b/editors/vscode/CHANGELOG.md
@@ -0,0 +1,8 @@
+# Changelog
+
+## 0.12.1
+
+- Added RQL highlighting for `local-value` and `local_value` role and wrapper forms (#12).
+- Added RQL `anchor` highlighting with exact wrapper token boundaries and near-miss coverage (#14).
+- Fixed marketplace smoke downloads by decoding compressed HTTP responses before hashing or unzipping (#13).
+- Migrated the LSP and editor documentation and added an unpublished, unsupported Zed development scaffold (#15).
diff --git a/editors/vscode/package-lock.json b/editors/vscode/package-lock.json
diff --git a/editors/vscode/package.json b/editors/vscode/package.json
@@ -2,7 +2,7 @@
   "name": "bifrost-vscode",
   "displayName": "Bifrost: Multi-Language LSP & MCP Server",
   "description": "Tree-sitter-backed code intelligence for definitions, references, symbols, hierarchy, rename, diagnostics, and MCP workflows.",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "bifrost": {
     "serverVersion": "0.1.1",
     "minimumServerVersion": "0.1.1",