Desktop: enable the openknowledge.ai update proxy for the stable…

.changeset/desktop-enable-stable-update-proxy.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+Desktop: enable the openknowledge.ai update proxy for the stable (`latest`) channel too. Stable builds now fetch updates through `openknowledge.ai/updates/stable`, which 302s to the byte-identical GitHub asset (preserving the manifest sha512 and the macOS signature) so stable updates are counted per version. This follows the verified end-to-end beta update (beta.13 to beta.14) through the proxy. The stable path resolves via GitHub's authoritative `releases/latest` alias, and a feed failure still reverts to the GitHub provider for the session, so auto-update reliability never drops below GitHub-direct.

.changeset/file-menu-project-switcher-parity.md

@@ -0,0 +1,6 @@
+---
+"@inkeep/open-knowledge-desktop": patch
+"@inkeep/open-knowledge-app": patch
+---
+
+Align the macOS File menu with the in-app project switcher. The File menu's project actions now sit together directly under "New from template…" and read in the same order as the bottom-left switcher: Recent project, New project, Switch project, Open folder. "Create new project…" is renamed "New project…" and the recents submenu is renamed "Recent project" to match the switcher's labels. The switcher's own action order is updated to the same sequence (New project, Switch project, Open folder) so both surfaces are consistent. Wiring, accelerators, and behavior are unchanged.

.changeset/fix-dead-links-fresh-doc-false-positive.md

@@ -0,0 +1,6 @@
+---
+"@inkeep/open-knowledge-server": patch
+"@inkeep/open-knowledge": patch
+---
+
+Fix `links({ kind: "dead" })` falsely reporting freshly-written docs as dead. The dead-link check decided a target existed only from the file-watcher's file index, which lags behind in-session writes, so a doc the link graph had just registered a backlink for could still be flagged dead until a server restart. Dead-link resolution now also treats any doc the graph already holds as a live node (its body has been indexed) as a valid target, so a newly-written doc is a valid link target immediately — without changing how genuinely-missing targets are reported.

.changeset/pre.json

@@ -2,14 +2,14 @@
   "mode": "pre",
   "tag": "beta",
   "initialVersions": {
-    "@inkeep/open-knowledge-docs": "0.0.3",
-    "@inkeep/open-knowledge-app": "0.19.2",
-    "@inkeep/open-knowledge": "0.19.2",
-    "@inkeep/open-knowledge-core": "0.19.2",
-    "@inkeep/open-knowledge-desktop": "0.19.2",
-    "@inkeep/md-conformance": "0.0.11",
+    "@inkeep/open-knowledge-docs": "0.0.4",
+    "@inkeep/open-knowledge-app": "0.20.0",
+    "@inkeep/open-knowledge": "0.20.0",
+    "@inkeep/open-knowledge-core": "0.20.0",
+    "@inkeep/open-knowledge-desktop": "0.20.0",
+    "@inkeep/md-conformance": "0.0.12",
     "@inkeep/open-knowledge-plugin": "0.3.1",
-    "@inkeep/open-knowledge-server": "0.19.2"
+    "@inkeep/open-knowledge-server": "0.20.0"
   },
   "changesets": []
 }