chore: release core 0.7.45, vscode 0.2.3, nvim 0.2.3

core 0.7.45 ships the #1114 fix (a stale hover prefetch no longer degrades
a click to a full page load) plus the new webjs:navigation-fallback event.

The two editor plugins were missed by my first audit and are added here.
I had dismissed them with "intellisense is unchanged, so neither plugin
owes a republish", which is the wrong test: the question is whether the
PLUGIN's own shipped bundle changed since the PLUGIN's last release, not
since intellisense's. Both did.

The VS Code extension is the sharper case. Its shipped "open documentation"
command still points at docs.webjs.dev, which moved onto the main domain in
#1101. That is user-visible behaviour in a published artifact, and it is the
same class of stale-host fix that core 0.7.44 was released on its own to
ship. webjs.nvim carries a refreshed committed intellisense bundle.

Both changelogs keep npm: false, so release.yml cuts GitHub Releases for
them and publishes neither to the registry. The actual distribution is still
manual: the nvim subtree split, and a vsce publish by the owner.

Author: vivek7405

changelog/core/0.7.45.md

@@ -16,4 +16,4 @@ commit_count: 1
 
 - **client-router degradations are now observable in production** ([#1115](https://github.com/webjsdev/webjs/pull/1115)) [`f34fa5c9`](https://github.com/webjsdev/webjs/commit/f34fa5c9)
 
-  When a soft navigation is not safely possible the router degrades to a full page load, which is correct but was previously reported only by a development-mode console warning, leaving deployed apps with no signal at all. Every such path now dispatches a `webjs:navigation-fallback` event on `document` in all environments, with detail `{ cause, href, willReload }`. `willReload` distinguishes a click that became a document load from a background operation that was merely dropped. The event is not cancelable, and a listener that throws cannot affect the navigation.
+  When a soft navigation is not safely possible the router degrades to a full page load, which is correct but was previously reported only by a development-mode console warning, leaving deployed apps with no signal at all. Every such path now dispatches a `webjs:navigation-fallback` event on `document` in all environments, with detail `{ cause, href, willReload }`. `willReload` is true only when a document load actually follows, so a listener can count real full loads without also counting the degradations that resolve in place (a dropped background revalidation, or a suppressed cross-deploy reload that proceeds on the stale importmap). The event is not cancelable, and a listener that throws cannot affect the navigation.

changelog/nvim/0.2.3.md

@@ -0,0 +1,12 @@
+---
+package: "webjs.nvim"
+version: 0.2.3
+date: 2026-07-26T17:55:00.000Z
+commit_count: 1
+npm: false
+---
+## Fixes
+
+- **refreshed the vendored intellisense bundle** ([#855](https://github.com/webjsdev/webjs/pull/855)) [`f41d105b`](https://github.com/webjsdev/webjs/commit/f41d105b)
+
+  The plugin ships a committed copy of `@webjsdev/intellisense`, and that copy has changed since 0.2.2. This version bump publishes the refreshed bundle to the standalone mirror; there is no change to the plugin's own Lua surface.

changelog/vscode/0.2.3.md

@@ -0,0 +1,16 @@
+---
+package: "webjs (VS Code extension)"
+version: 0.2.3
+date: 2026-07-26T17:55:00.000Z
+commit_count: 2
+npm: false
+---
+## Fixes
+
+- **the "open documentation" command points at the current docs host** ([#1101](https://github.com/webjsdev/webjs/pull/1101)) [`e07ea3a1`](https://github.com/webjsdev/webjs/commit/e07ea3a1)
+
+  The documentation moved from `docs.webjs.dev` onto the main domain, and the command shipped in the extension still opened the old host. This is the extension-side counterpart of the same fix released in `@webjsdev/core` 0.7.44.
+
+- **brand casing corrected in extension-facing prose** ([#855](https://github.com/webjsdev/webjs/pull/855)) [`f41d105b`](https://github.com/webjsdev/webjs/commit/f41d105b)
+
+  Prose in the extension source now writes `WebJs` consistently, matching the repo-wide rule.

packages/editors/nvim/package.json

@@ -1,6 +1,6 @@
 {
   "name": "webjs.nvim",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "private": true,
   "description": "Neovim editor support for webjs apps (html/css/svg template highlighting + in-template intelligence via the bundled @webjsdev/intellisense). NOT an npm package: ships to the webjsdev/webjs.nvim git repo via subtree split, installed by lazy.nvim. This manifest exists only as the version source for the unified changelog (changelog/nvim/<version>.md); see PUBLISHING.md."
 }

packages/editors/vscode/package.json

@@ -1,7 +1,7 @@
 {
   "name": "webjs",
   "displayName": "webjs",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "All-in-one webjs support: html/css template highlighting, language-service intelligence, snippets, and commands. No Lit extension required.",
   "publisher": "webjsdev",
   "private": true,