Skip to content

Beautiful, AI-native markdown IDE and LLM wiki

main reset: post-stable v0.10.0 (#1716)

inkeep-internal-ci[bot]e9937e808870
diff --git a/.changeset/asset-link-opens-preview.md b/.changeset/asset-link-opens-preview.md
deleted file mode 100644
index 0bebdec93..000000000
--- a/.changeset/asset-link-opens-preview.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@inkeep/open-knowledge": patch
----
-
-Clicking a link to a non-markdown file (HTML, archives, Office docs, and other non-viewable types) now opens the same in-app preview the sidebar shows when you select that file, instead of handing the file straight to the operating system.
-
-Previously, once these links resolved, a bare click immediately delegated to the OS (or, for HTML and other scripted types the desktop app refuses to open directly, revealed the file in Finder). A click now lands on the file's preview screen — for non-viewable types that screen offers "Open file" and "Open with built-in text editor" — so the behavior matches selecting the file in the sidebar. Cmd/Ctrl/middle-click still opens the file in the OS default app (desktop) or a new tab (web) as an escape hatch.
diff --git a/.changeset/asset-link-resolution-non-markdown.md b/.changeset/asset-link-resolution-non-markdown.md
deleted file mode 100644
index 44dd01cf3..000000000
--- a/.changeset/asset-link-resolution-non-markdown.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": patch
----
-
-Fix links to non-markdown files rendering as "non-existent" (red) links even when the file exists.
-
-Links to HTML, GPX, XML, archive (`.7z`/`.tar`/`.rar`/…), legacy Office (`.doc`/`.xls`/`.ppt`), OpenDocument, iWork, and e-book files now resolve and serve like any other asset. The editor treats every non-markdown link target as an asset, but the set that governs indexing, serving, and link resolution previously omitted these types, so their links always showed as broken.
-
-`ASSET_EXTENSIONS` is now a superset of everything you can embed or link, enforced by a runtime guard so the two sets can't drift apart again. Newly admitted types are served as downloads (and open in the OS default app on desktop). HTML files are served inside a sandboxed, opaque origin (`Content-Security-Policy: sandbox allow-scripts; connect-src 'none'`): their scripts run so interactive documents work, but they can't read your knowledge base's cookies or storage, and `connect-src 'none'` blocks them from reaching the local API or exfiltrating over the network. On desktop, clicking an HTML link reveals it in Finder rather than failing silently.
diff --git a/.changeset/command-palette-new-project.md b/.changeset/command-palette-new-project.md
deleted file mode 100644
index 8d0b5c355..000000000
--- a/.changeset/command-palette-new-project.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@inkeep/open-knowledge-app": patch
----
-
-Add a "New project" command to the Cmd+K command palette. It opens the same create-new-project dialog reachable from the File → Create New Project… menu and the project switcher. Desktop-only — hidden in the web host.
diff --git a/.changeset/desktop-dmg-install-window.md b/.changeset/desktop-dmg-install-window.md
deleted file mode 100644
index fc4161cf7..000000000
--- a/.changeset/desktop-dmg-install-window.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@inkeep/open-knowledge-desktop": patch
----
-
-Custom DMG install window: the mounted disk image now shows the standard "drag the app onto Applications" layout, with the app icon and the `/Applications` alias positioned over a background image.
-
-Configured via electron-builder's `dmg` block (installer-window size, icon coordinates, `background`). The committed background is a schematic placeholder; final branded artwork drops into `packages/desktop/build/dmg-background.png` + `[email protected]` (540x380 / 1080x760). Iterate on the layout locally with `bun run build:mac:unsigned`.
diff --git a/.changeset/entity-vault-gbrain-compatible-rename.md b/.changeset/entity-vault-gbrain-compatible-rename.md
deleted file mode 100644
index dcba9f91d..000000000
--- a/.changeset/entity-vault-gbrain-compatible-rename.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": patch
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge-app": patch
-"@inkeep/open-knowledge-desktop": patch
----
-
-Rename the `gbrain` starter pack to **Entity vault (GBrain-compatible)** and reposition it as a human cockpit for GBrain-style Markdown brains rather than a GBrain reimplementation. This is a breaking pre-release rename: the canonical pack ID is now `entity-vault` with no `gbrain` alias, so `ok seed --pack gbrain` no longer resolves — use `ok seed --pack entity-vault`. The pack picker, seed dialog, toast, and CLI list now show "Entity vault (GBrain-compatible)". Generated dossier templates are tightened for GBrain-compatible parsing — document-level `title:` frontmatter, an explicit `--- timeline ---` sentinel, and parseable `- **YYYY-MM-DD** | source | @author — … Confidence: …` timeline bullets with path-qualified `[[folder/slug|Label]]` links. The workflow doc moved from `/workflows/gbrain` to `/workflows/entity-vault`. OK edits and reviews the Markdown; Garry Tan's `gbrain`, if installed, can still import/sync the same vault — interop is Markdown + Git, with no deep integration implied.
diff --git a/.changeset/exec-stdout-dedup-cap.md b/.changeset/exec-stdout-dedup-cap.md
deleted file mode 100644
index 2a9b8a74d..000000000
--- a/.changeset/exec-stdout-dedup-cap.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@inkeep/open-knowledge-server": patch
----
-
-Fix `exec` MCP results overflowing the client's per-result token limit on mid-size reads. The visible body was serialized up to 3× per result — `content[].text`, `structuredContent.text` (the load-bearing cross-client mirror that Claude-class clients read when they drop `content[].text`), and a redundant `structuredContent.stdout` raw copy — while the soft cap budgeted only one copy. A markdown file comfortably under the cap (so `exec` reported `stdoutTruncated: false`) could still produce a result large enough that the client rejected it and spilled to a file, silently degrading an in-budget read.
-
-Two changes: (1) drop the `structuredContent.stdout` field. It was the original Claude-Desktop `content[].text`-drop workaround, fully superseded by the `structuredContent.text` mirror it predates; its bytes are a strict subset of `text` and nothing consumed it. (2) Recalibrate the soft cap to budget the realized 2× body duplication (`content[].text` + `structuredContent.text`) rather than a single copy — the per-string cap is now ~25 KB (`RESULT_BODY_BUDGET_BYTES / WIRE_BODY_COPIES`), so the doubled payload stays well under the client ceiling. Oversized reads now truncate with the existing `<truncated: … re-run with a more-specific query>` marker instead of silently overflowing. The cross-client `content[].text` + `structuredContent.text` mirror is unchanged.
diff --git a/.changeset/fix-boundary-space-overescape.md b/.changeset/fix-boundary-space-overescape.md
deleted file mode 100644
index 603f7ac45..000000000
--- a/.changeset/fix-boundary-space-overescape.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@inkeep/open-knowledge-core": patch
----
-
-fix(markdown): stop over-escaping phrasing-boundary whitespace character references
-
-A space or tab at a phrasing boundary (the edge of a paragraph, list item, or blockquote's inline content) was serializing to a backslash-escaped character reference (`\&#x20;` / `\&#x9;`) instead of a bare `&#x20;` / `&#x9;`. Per CommonMark the escaped form renders as the literal visible text `&#x20;` in GitHub, the docs site, and Open Knowledge's own re-parsed editor. `escapeEntityAmpersands` now leaves character references that `mdast-util-to-markdown` synthesizes for boundary-whitespace preservation un-escaped, while continuing to escape user-authored entities.
diff --git a/.changeset/fix-cli-repository-url-provenance.md b/.changeset/fix-cli-repository-url-provenance.md
deleted file mode 100644
index 06b804349..000000000
--- a/.changeset/fix-cli-repository-url-provenance.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@inkeep/open-knowledge": patch
----
-
-Restore the `repository` field on the published CLI package, pointing at `inkeep/open-knowledge`. It was dropped when the mirror was re-pointed off `open-knowledge-legacy`, which left npm Trusted Publishing unable to verify provenance and failed every release publish with `E422 ... "repository.url" is ""`.
diff --git a/.changeset/fix-desktop-epipe-crash-dialog.md b/.changeset/fix-desktop-epipe-crash-dialog.md
deleted file mode 100644
index 53be6310c..000000000
--- a/.changeset/fix-desktop-epipe-crash-dialog.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@inkeep/open-knowledge": patch
----
-
-Desktop: the main process no longer crashes with a recurring "A JavaScript error occurred in the main process — Error: write EPIPE" dialog after every window is closed. On macOS the main process outlives its windows, and the auto-updater's periodic timer keeps writing to the stdout/stderr inherited from the launching terminal; once that terminal closes, each write throws `EPIPE`, which — with no stream `error` listener — escalated to an uncaught exception and Electron's fatal-error modal, reappearing every few minutes until the process was killed. A broken-pipe guard installed at the earliest point of main-process boot now handles these benign writes at the stream boundary so they never become an uncaught exception, while genuine (non-broken-pipe) stream errors are still surfaced to the file log. The guard is logger-agnostic, so it covers every stdout/stderr writer in the main process, not just the updater.
diff --git a/.changeset/fix-frontmatter-digit-leading-tags.md b/.changeset/fix-frontmatter-digit-leading-tags.md
deleted file mode 100644
index e7d234c5f..000000000
--- a/.changeset/fix-frontmatter-digit-leading-tags.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-app": patch
----
-
-Allow digit-leading tags (like the year `2026`) in a document's frontmatter `tags:` field. The property panel previously rejected them with "Tags must start with a letter…", even though a year is a legitimate tag. The frontmatter tag grammar is now more permissive than the inline `#tag` grammar: a frontmatter tag may start with a letter or a digit, while inline `#tag` in prose still requires a leading letter (so `#123` stays plain text and does not collide with issue-reference conventions).
diff --git a/.changeset/fix-open-with-ai-modal-trap.md b/.changeset/fix-open-with-ai-modal-trap.md
deleted file mode 100644
index 6a33c0c6a..000000000
--- a/.changeset/fix-open-with-ai-modal-trap.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": patch
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge-app": patch
-"@inkeep/open-knowledge-desktop": patch
----
-
-Fix the editor toolbar's "Open with AI" menu freezing the rest of the app in the macOS desktop app. Once the menu became openable on the desktop host, its default modal behavior disabled pointer events on everything outside the menu while it was open. Because the menu lives in the macOS title-bar drag region — where the outside-click that normally dismisses a modal doesn't reliably reach the menu — the only way to close it was to pick an agent, and meanwhile the rest of the chrome (notably the bottom-left project switcher) couldn't be clicked. The menu is now non-modal: opening it no longer blocks the rest of the UI, and clicking anywhere outside dismisses it. Browsers (`ok ui`) are unaffected.
diff --git a/.changeset/fix-project-switcher-click-open-dismiss.md b/.changeset/fix-project-switcher-click-open-dismiss.md
deleted file mode 100644
index 178b09c27..000000000
--- a/.changeset/fix-project-switcher-click-open-dismiss.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": patch
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge-app": patch
-"@inkeep/open-knowledge-desktop": patch
----
-
-Fix the sidebar project switcher not opening, and not dismissing on outside click, in the macOS desktop app. Radix's DropdownMenu opens on `pointerdown`, but the desktop renderer does not receive real `pointerdown` events (only `mousedown`/`click`), so clicking the trigger did nothing; and because the menu was modal, clicking outside could not dismiss it either. The trigger now also opens from the `click` event on the desktop host (mirroring the editor's "Open with AI" menu), and the menu is non-modal so outside-click dismissal works and the rest of the UI stays interactive while it's open — matching the Cloud/Sync popover. Browsers are unaffected.
diff --git a/.changeset/fix-project-switcher-dropdown-open.md b/.changeset/fix-project-switcher-dropdown-open.md
deleted file mode 100644
index 44b3c915f..000000000
--- a/.changeset/fix-project-switcher-dropdown-open.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": patch
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge-app": patch
-"@inkeep/open-knowledge-desktop": patch
----
-
-Fix the project switcher in the sidebar footer not opening in the macOS desktop app. Clicking it showed a press state but the dropdown never opened. A Radix tooltip recently added to the trigger (to show the project path on hover) interfered with the menu on the desktop host: once the tooltip had opened on hover, clicking the trigger raced the tooltip's teardown against the menu's open, so the menu never stayed open. The trigger no longer uses a Radix tooltip — the full project path is shown via a native tooltip instead — and the menu opens reliably.
diff --git a/.changeset/fix-source-table-indent.md b/.changeset/fix-source-table-indent.md
deleted file mode 100644
index 1681dea02..000000000
--- a/.changeset/fix-source-table-indent.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-"@inkeep/open-knowledge": patch
----
-
-fix(open-knowledge): source-view tables no longer render indented left of surrounding text
-
-GFM table rows in the Markdown source view rendered roughly 2ch to the left of the
-surrounding prose, headings, and lists. The source-polish view-plugin set the
-`.cm-table-row` / `.cm-table-header` line classes but never set the `--list-hang`
-variable that the base `.cm-line` rule consumes, so the base `!important`
-`padding-inline-start` overrode the standalone table `padding` while the table's
-negative `text-indent` still applied, pulling table lines into the gutter. Tables
-now participate in the same hanging-indent mechanism as lists and fenced code, so
-they line up with body text. (PRD-6922)
diff --git a/.changeset/fix-sync-per-operation-errors.md b/.changeset/fix-sync-per-operation-errors.md
deleted file mode 100644
index c98b0386b..000000000
--- a/.changeset/fix-sync-per-operation-errors.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-"@inkeep/open-knowledge": patch
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge-app": patch
-"@inkeep/open-knowledge-desktop": patch
----
-
-fix(sync): track push and pull errors separately so a sync error stops flashing in the popover
-
-The sync status popover would show a sync error (e.g. a failed push) for only a split second before it vanished. The engine stored the last failure in a single shared `error` field, so a successful fetch on the pull leg cleared a still-unresolved push error — and `trigger('sync')` runs push then pull, so the push error was wiped by the immediately-following fetch within the same "Sync now". The same alternation happened continuously under auto-sync.
-
-Push and pull errors are now tracked independently (`pushError`/`pushErrorCode` and `pullError`/`pullErrorCode`). A success on one leg only clears that leg's error, so a real push failure stays visible until a push actually succeeds (or sync is toggled).
-
-When both legs fail with the same root cause (e.g. an auth failure that blocks fetch and push alike) the popover collapses them into a single neutral line instead of repeating two near-identical messages. When the two legs fail for different reasons, each line is labeled "Push:" / "Pull:" so it's clear which direction failed. A lone failure renders unlabeled, with pull-specific copy for read-side auth failures.
diff --git a/.changeset/fix-update-relaunch-banner-nondismissible.md b/.changeset/fix-update-relaunch-banner-nondismissible.md
deleted file mode 100644
index 1ba00e602..000000000
--- a/.changeset/fix-update-relaunch-banner-nondismissible.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": patch
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge-app": patch
-"@inkeep/open-knowledge-desktop": patch
----
-
-Remove the dismiss X from the "Relaunching to install the update…" banner. That card is a terminal in-progress state shown the instant Relaunch is clicked — there is nothing to dismiss, and the card already disappears when the app restarts, so a manual close would only hide live progress. The armed "Version X ready to install" card keeps its X (the user can still close it and relaunch later); only the post-click in-progress swap is now non-dismissible, via a new `dismissible` flag on the update-notice shape.
diff --git a/.changeset/gplv3-license-adoption.md b/.changeset/gplv3-license-adoption.md
deleted file mode 100644
index 9c35bdf06..000000000
--- a/.changeset/gplv3-license-adoption.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-"@inkeep/open-knowledge": minor
-"@inkeep/open-knowledge-desktop": minor
----
-
-Adopt GPL-3.0-or-later. Open Knowledge is now licensed under the GNU General Public License v3.0 or later: every package declares the `license` field, the GPLv3 LICENSE text ships in the npm tarball and the desktop app bundle, `ok --version` prints the standard GPL notice (copyright, free software, no warranty), and the desktop About panel carries the same notice.
diff --git a/.changeset/hide-ds-store-show-all-files.md b/.changeset/hide-ds-store-show-all-files.md
deleted file mode 100644
index 8a267fab4..000000000
--- a/.changeset/hide-ds-store-show-all-files.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@inkeep/open-knowledge": patch
----
-
-Stop surfacing macOS Finder metadata files (`.DS_Store`, `.localized`) in the file sidebar's "Show All Files" mode.
-
-These files were already hidden in the normal sidebar (they're seeded into `.gitignore` on `ok init`), but "Show All Files" deliberately bypasses `.gitignore` / `.okignore` to surface gitignored content like `dist/` and `build/` — which re-surfaced `.DS_Store` as a sidebar asset row. They are now pruned by an always-on junk-file floor, the file-level analogue of the existing directory floor that keeps `.git/`, `node_modules/`, and `.ok/` hidden even under Show All Files. Legitimate gitignored content still shows.
diff --git a/.changeset/inline-image-doc-relative-src.md b/.changeset/inline-image-doc-relative-src.md
deleted file mode 100644
index c0f281822..000000000
--- a/.changeset/inline-image-doc-relative-src.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@inkeep/open-knowledge-app": patch
----
-
-Fix inline markdown images with a doc-relative path (`![](./assets/x.jpg)` mid-prose) resolving against the SPA root instead of the document's folder. The inline image node-view now applies the same doc-folder base resolution the block image render path already uses, so a relative `src` no longer 404s until a hard reload.
diff --git a/.changeset/local-sinks-anchor-on-projectdir.md b/.changeset/local-sinks-anchor-on-projectdir.md
deleted file mode 100644
index 63c349398..000000000
--- a/.changeset/local-sinks-anchor-on-projectdir.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge": patch
----
-
-Fix the log and telemetry file-sinks writing into a second `.ok/` when `content.dir` is a sub-folder. Both per-machine sinks (`.ok/local/logs/server-current.jsonl`, `.ok/local/telemetry/spans-current.jsonl`) now anchor on the project root like `server.lock` / `principal.json` / `state.json`, so a project with e.g. `content.dir: docs` keeps a single `.ok/` at the root instead of growing a second one buried inside the content sub-folder where backups, git, sync, and visual inspection wouldn't expect it. `ok diagnose bundle` reads the sinks and `server.lock` from the same project-root-anchored `.ok/local/` so it keeps harvesting them after the move.
diff --git a/.changeset/mcp-semantic-search-openai-embeddings.md b/.changeset/mcp-semantic-search-openai-embeddings.md
deleted file mode 100644
index a624b5043..000000000
--- a/.changeset/mcp-semantic-search-openai-embeddings.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": minor
----
-
-Add opt-in semantic search to the MCP `search` tool, powered by a remote OpenAI-compatible embeddings API. When enabled, an embeddings signal is fused into `full_text` ranking so an agent's query surfaces conceptually-related pages even when they share no keywords (e.g. "auth retries" → a page titled "Session Token Refresh"). It is additive and **off by default**: with the flag off, search is byte-for-byte today's lexical ranking, and the cmd-K omnibar always stays purely lexical and instant.
-
-**Privacy / egress.** When the feature is enabled **and** a key is set, the search query and matching page content are sent to the configured embeddings provider. Egress is explicit and scoped: only corpus content is embedded — anything excluded by `.okignore` / `.gitignore` is never sent — embedding is lazy (nothing leaves the machine until an agent actually runs a semantic search), and the key lives only in a 0600 `~/.ok/secrets.yml` file (never in config, logs, or telemetry). If the key is missing, the provider errors, or you're offline, search silently degrades to lexical and never blocks.
-
-Setup (per machine): `ok embeddings set-key` stores the provider key in `~/.ok/secrets.yml` (0600); set `search.semantic.enabled: true` in project-local config. `ok embeddings status` shows capability. Provider base URL / model / dimensions are configurable (Azure / self-hosted / other). Vectors cache incrementally under `.ok/local/` (content-addressed, keyed by provider + model + dimensions). See the "Semantic search" section of the configuration reference for full setup.
diff --git a/.changeset/open-base-canvas-as-text.md b/.changeset/open-base-canvas-as-text.md
deleted file mode 100644
index bb6f0be11..000000000
--- a/.changeset/open-base-canvas-as-text.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": patch
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge-app": patch
-"@inkeep/open-knowledge-desktop": patch
----
-
-Open `.base` and `.canvas` files (Obsidian Bases / Canvas) directly in the read-only text viewer. Previously, clicking a `[[file.base]]` or `[[file.canvas]]` wiki-link opened a chooser pane; clicking "Open file" from the chooser then replaced the editor view with a raw `415` JSON error envelope from the API. Now both file types open immediately in the built-in text viewer (`.canvas` with JSON syntax highlighting) — no chooser, no broken "Open file". The "Open file" affordance for all other downloadable types (`.docx`, `.zip`, etc.) is also hardened: it now routes through the sanctioned asset-dispatch path (OS-handoff on desktop, new tab on web) instead of a same-frame navigation to the asset API.
diff --git a/.changeset/open-with-ai-electron-click.md b/.changeset/open-with-ai-electron-click.md
deleted file mode 100644
index 3bb354042..000000000
--- a/.changeset/open-with-ai-electron-click.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@inkeep/open-knowledge": patch
-"@inkeep/open-knowledge-core": patch
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge-app": patch
-"@inkeep/open-knowledge-desktop": patch
----
-
-Fix the editor toolbar's "Open with AI" menu not opening in the macOS desktop app. The header sits in a macOS title-bar drag region (`-webkit-app-region: drag`), and macOS swallows the `pointerdown` event on its children — even on the `no-drag` button — before the DOM sees it. Radix's dropdown opens on `pointerdown`, so clicking the button did nothing. The synthesized `click` still fires, so on the desktop host the menu now opens from the click instead. Browsers (`ok ui`) are unaffected and keep Radix's default behavior. This regressed when the button's redundant hover tooltip was removed, which had incidentally kept pointer events flowing to the trigger.
diff --git a/.changeset/prd-6832-beta-disk-authority.md b/.changeset/prd-6832-beta-disk-authority.md
deleted file mode 100644
index 26ee266de..000000000
--- a/.changeset/prd-6832-beta-disk-authority.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-"@inkeep/open-knowledge-server": patch
-"@inkeep/open-knowledge": patch
----
-
-fix(open-knowledge): MCP writes reflect on-disk truth — reconcile out-of-band edits instead of silently clobbering them (PRD-6832)
-
-An OK MCP read could authoritatively return content older than the bytes on disk, with no warning. The root cause was upstream of the read: a doc loaded in the server holds stale in-memory CRDT state, an out-of-band edit (a script, `git pull`, manual edit) makes disk newer, and the next MCP write serializes the stale CRDT over the newer file — making disk itself stale, so the next read faithfully returns bad bytes. In one incident this gave an agent a stale spec scope and cost a multi-file revert.
-
-This change makes disk authoritative on the write/reconcile path:
-
-- **Reconcile-before-apply (L1).** Before a content write (`write_document` / `edit_document` / `edit_frontmatter`) or a `rename` applies, the server compares the on-disk bytes to the last-synced base and, on divergence, ingests the disk edit first (through the existing sanctioned file-watcher path) so the agent's edit lands on top of current reality. Both edits survive.
-- **Store-time backstop (L3).** For the residual few-millisecond window where disk changes between the reconcile check and the store, the store re-checks disk before overwriting. On divergence it aborts the overwrite (disk wins) and the handler returns a hard `urn:ok:error:disk-divergence` (409) — the agent's edit was NOT applied; re-read and retry (a retry re-applies exactly once). This is the only guard for `undo` / `rollback`, which have no L1.
-- **Heads-up on reconcile.** When a write reconciles an out-of-band edit, the success response carries a `disk-edit-reconciled` warning (`structuredContent.contentDivergence`) so the agent re-reads to see the combined result. Observational — the write still landed and both edits are on disk.
-
-Human-editor (browser) writes are unaffected: the backstop only fires on agent-triggered stores, so in-progress typing is never reverted.
diff --git a/.changeset/pre.json b/.changeset/pre.json
index efee78798..03b49a86f 100644
--- a/.changeset/pre.json
+++ b/.changeset/pre.json
@@ -3,12 +3,12 @@
"tag": "beta",
"initialVersions": {
"@inkeep/open-knowledge-docs": "0.0.1",
- "@inkeep/open-knowledge-app": "0.9.1",
- "@inkeep/open-knowledge": "0.9.1",
- "@inkeep/open-knowledge-core": "0.9.1",
- "@inkeep/open-knowledge-desktop": "0.9.1",
+ "@inkeep/open-knowledge-app": "0.10.0",
+ "@inkeep/open-knowledge": "0.10.0",
+ "@inkeep/open-knowledge-core": "0.10.0",
+ "@inkeep/open-knowledge-desktop": "0.10.0",
"@inkeep/open-knowledge-plugin": "0.3.1",
- "@inkeep/open-knowledge-server": "0.9.1"
+ "@inkeep/open-knowledge-server": "0.10.0"
},
"changesets": []
}
diff --git a/.changeset/preview-open-network-policy.md b/.changeset/preview-open-network-policy.md
deleted file mode 100644
index 143156ae9..000000000
--- a/.changeset/preview-open-network-policy.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-"@inkeep/open-knowledge-core": minor
-"@inkeep/open-knowledge-app": minor
-"@inkeep/open-knowledge-server": minor
----
-
-Preview embeds can now reach the network. The code-block `html preview` iframe runs with an open network CSP, so embeds that load external stylesheets, `fetch` live data, pull map tiles / remote images, use web fonts, or embed third-party iframes (over `https:`/`wss:`/`data:`/`blob:`) render — Leaflet maps, live-data charts, and the like work out of the box. `'unsafe-eval'` is not granted (the common libraries don't need it), and `*` / plaintext `http:`/`ws:` schemes are excluded.
-
-The iframe stays a sandboxed null-origin frame (`sandbox="allow-scripts"`, no `allow-same-origin`), so an embed can reach the network but can never read the knowledge base, cookies, or auth — it widens network reach, not document access.
-
-Breaking: the `preview.scriptSrc` config field is removed — the preview network policy is no longer configurable. A stale `preview.scriptSrc` key is rejected loudly on config load with a migration message (and handled by `ok config migrate`), not a silent no-op. A future multi-tenant host that needs to lock the preview network down will do so with an operator-level control (an env / build flag the tenant can't edit), not a content-editable config field.
diff --git a/.changeset/release-notes-multi-window-dismiss.md b/.changeset/release-notes-multi-window-dismiss.md
deleted file mode 100644
index 063f16d8a..000000000
--- a/.changeset/release-notes-multi-window-dismiss.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-"@inkeep/open-knowledge-desktop": patch
----
-
-feat(ok-desktop): show the release-notes update notice on every open project window
-
-The "Updated to Version X" release-notes notice previously appeared on only one project window when several projects were open together, so a user looking at a different project never saw it. It now appears on every open window, and the "Relaunch now" update banner does too.
-
-Dismissing the release-notes notice on one window (or letting it auto-expire after its one-minute window) now clears it on all of them, so the same FYI no longer needs swatting once per window. A project opened shortly after an update, while the notice is still live, also shows it.
-
-When both a "new version ready to install" banner and the release-notes notice are armed at once, the single-card behavior is unchanged: the relaunch banner takes precedence and the release-notes notice waits behind it.
diff --git a/.changeset/selection-aware-document-stats.md b/.changeset/selection-aware-document-stats.md
deleted file mode 100644
index 8285d1e6b..000000000
--- a/.changeset/selection-aware-document-stats.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-"@inkeep/open-knowledge-app": patch
----
-
-feat(open-knowledge): editor footer counts scope to the selection
-
-The footer word / character / token counts now reflect the current text
-selection. When you select a passage in either edit mode, the counts switch to
-that passage and gain a "Selected" indicator; collapsing the selection reverts
-to the whole-document counts. Selection counts use the same visible-text
-semantics as the document counter (markdown syntax stripped), so the same
-passage counts identically whether selected in WYSIWYG or source mode.
diff --git a/.changeset/share-dialog-polish-and-md-sidebar-icon.md b/.changeset/share-dialog-polish-and-md-sidebar-icon.md
deleted file mode 100644
index 4abe7496f..000000000
--- a/.changeset/share-dialog-polish-and-md-sidebar-icon.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-"@inkeep/open-knowledge-app": patch
----
-
-Sidebar + share-dialog polish:
-
-- Custom Markdown sidebar icon (M↓) for `.md` and `.mdx` files, replacing Pierre's default glyph. Colored via the existing `--trees-file-icon-color-markdown` CSS variable so it tracks light/dark and selected-row treatment.
-- ShareBranchSwitchDialog: align Cancel button styling with the other dialog Cancel buttons (outline + font-mono uppercase). Give the secondary "Open in current branch" button the same uppercase font-mono treatment as the primary "Open in <branch>" button.
-- ShareBranchSwitchDialog: move the repository/file/branch metadata block from the dialog header into the body so it groups visually with the explanation paragraph.
-- ShareBranchSwitchDialog: fix a spurious scrollbar caused by inline `<code>` pills whose `py-0.5` extends past the surrounding line-box (`leading-6` on the variant paragraphs absorbs the inline padding).
-- ShareMetadataRows: bump value rows to `text-1sm` and label cells to `text-xs` for tighter hierarchy (affects both share dialogs that use this component).
-- ShareReceiveDialog: tighten the inline-`<code>` corner radius to `rounded-sm`.
diff --git a/.changeset/single-file-open.md b/.changeset/single-file-open.md
deleted file mode 100644
index e0ea718ce..000000000
--- a/.changeset/single-file-open.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-"@inkeep/open-knowledge": minor
-"@inkeep/open-knowledge-server": minor
-"@inkeep/open-knowledge-core": minor
-"@inkeep/open-knowledge-app": minor
-"@inkeep/open-knowledge-desktop": minor
----
-
-Add `ok <file>` — open a single markdown file in the editor with zero project setup. Run `ok notes.md` (or `ok open notes.md`) on any `.md` / `.mdx` file and it opens in the WYSIWYG ↔ source editor.
-
-- **Project-aware.** When the file lives inside an existing Open Knowledge project (an ancestor `.ok/`), it opens that project focused on the file — the path is realpath-resolved first, so a symlink into a project routes correctly.
-- **No-project mode.** For a loose file, it opens an ephemeral single-file session: a throwaway server scoped to just that one file, with git, MCP, and agents off. Edits save straight back to your original file. **No `.ok/` or other state is written into your directory** — all session state lives in a temporary directory that's removed when you close the window.
-- **Opening never reformats.** A file you open but don't edit is left byte-for-byte identical, even when it has an unstable markdown round-trip.
-- **Desktop-first with a browser fallback.** Opens in the Open Knowledge desktop app when it's installed; otherwise serves the editor in your browser (Ctrl-C to end the session). Launching from a closed app goes straight to the file in a single window — it doesn't reopen your last project alongside it.
-- **Focused chrome.** No-project sessions hide the file sidebar, tabs, project switcher, and Settings — just the file and the editor.
-
-Discoverable via `ok --help`.
diff --git a/.changeset/telemetry-shutdown-drain-file-sink-first.md b/.changeset/telemetry-shutdown-drain-file-sink-first.md
deleted file mode 100644
index 54dc7e426..000000000
--- a/.changeset/telemetry-shutdown-drain-file-sink-first.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@inkeep/open-knowledge-server": patch
----
-
-Fix telemetry shutdown losing local spans when the OTLP collector is unreachable. `shutdownTelemetry()` now drains the local file-sink exporter on its own awaited promise before the provider-wide teardown, instead of relying on `tracerProvider.shutdown()`. The provider fan-out is `Promise.all(...).then(resolve, reject)`, which short-circuits the moment the OTLP push processor rejects (a fast ECONNREFUSED when no collector is listening) — pre-empting the file pipeline's still-in-flight disk write. That dropped the very spans `ok diagnose bundle` exists to harvest and caused the intermittent `Telemetry > Gate combination 4` failure. Draining the file sink first makes on-disk span capture independent of the push pipeline's fate; the whole sequence still rides the existing shutdown-timeout race, so a pathological filesystem stall cannot deadlock teardown.
diff --git a/.changeset/textviewer-large-file-error-message.md b/.changeset/textviewer-large-file-error-message.md
deleted file mode 100644
index 9772117e8..000000000
--- a/.changeset/textviewer-large-file-error-message.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@inkeep/open-knowledge": patch
----
-
-Show a human-readable message when a file is too large for the built-in text editor, instead of a bare "Failed to load file (HTTP 413)".
-
-The built-in text editor caps the file it will load at 1 MB. Opening a larger file (a long GPS track `.gpx`, a big `.csv`, a verbose `.log`) previously surfaced only the raw status code. It now explains that the file exceeds the 1 MB limit and points to the "Open file" action to open it in another app. Other load failures map to plain-language messages too; unexpected statuses keep the code appended so they stay diagnosable.
diff --git a/bun.lock b/bun.lock
index ae9518dd4..001d7576b 100644
--- a/bun.lock
+++ b/bun.lock
@@ -65,7 +65,7 @@
},
"packages/app": {
"name": "@inkeep/open-knowledge-app",
- "version": "0.9.1",
+ "version": "0.10.0",
"dependencies": {
"@codemirror/autocomplete": "^6.20.1",
"@codemirror/commands": "^6.10.3",
@@ -203,7 +203,7 @@
},
"packages/cli": {
"name": "@inkeep/open-knowledge",
- "version": "0.9.1",
+ "version": "0.10.0",
"bin": {
"open-knowledge": "dist/cli.mjs",
"ok": "dist/cli.mjs",
@@ -245,7 +245,7 @@
},
"packages/core": {
"name": "@inkeep/open-knowledge-core",
- "version": "0.9.1",
+ "version": "0.10.0",
"dependencies": {
"@handlewithcare/remark-prosemirror": "0.1.5",
"@opentelemetry/api": "^1.9.0",
@@ -314,7 +314,7 @@
},
"packages/desktop": {
"name": "@inkeep/open-knowledge-desktop",
- "version": "0.9.1",
+ "version": "0.10.0",
"dependencies": {
"@inkeep/open-knowledge": "workspace:*",
"@inkeep/open-knowledge-core": "workspace:*",
@@ -347,7 +347,7 @@
},
"packages/server": {
"name": "@inkeep/open-knowledge-server",
- "version": "0.9.1",
+ "version": "0.10.0",
"dependencies": {
"@hocuspocus/server": "4.0.0-rc.1",
"@inkeep/open-knowledge-core": "workspace:*",
diff --git a/packages/app/package.json b/packages/app/package.json
index 02f2d8ff3..ac5565d4e 100644
--- a/packages/app/package.json
+++ b/packages/app/package.json
@@ -1,6 +1,6 @@
{
"name": "@inkeep/open-knowledge-app",
- "version": "0.9.1",
+ "version": "0.10.0",
"license": "GPL-3.0-or-later",
"private": true,
"type": "module",
diff --git a/packages/cli/package.json b/packages/cli/package.json
index 55e7b0e54..6d8225817 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -1,6 +1,6 @@
{
"name": "@inkeep/open-knowledge",
- "version": "0.9.1",
+ "version": "0.10.0",
"license": "GPL-3.0-or-later",
"private": false,
"type": "module",
diff --git a/packages/core/package.json b/packages/core/package.json
index 885cdabaf..8eae8b353 100644
--- a/packages/core/package.json
+++ b/packages/core/package.json
@@ -1,6 +1,6 @@
{
"name": "@inkeep/open-knowledge-core",
- "version": "0.9.1",
+ "version": "0.10.0",
"license": "GPL-3.0-or-later",
"private": true,
"type": "module",
diff --git a/packages/desktop/package.json b/packages/desktop/package.json
index 5d6191a94..56e32a4b9 100644
--- a/packages/desktop/package.json
+++ b/packages/desktop/package.json
@@ -1,7 +1,7 @@
{
"name": "@inkeep/open-knowledge-desktop",
"productName": "Open Knowledge",
- "version": "0.9.1",
+ "version": "0.10.0",
"license": "GPL-3.0-or-later",
"private": true,
"type": "module",
diff --git a/packages/server/assets/skills/discovery/SKILL.md b/packages/server/assets/skills/discovery/SKILL.md
index 7b3b286e1..1b6537206 100644
--- a/packages/server/assets/skills/discovery/SKILL.md
+++ b/packages/server/assets/skills/discovery/SKILL.md
@@ -3,7 +3,7 @@ name: open-knowledge-discovery
description: "Read when the user asks what Open Knowledge is, wants to install it on a repository, wants to share an Open Knowledge project with collaborators, or asks how `ok init` / `ok install-skill` / OK Desktop set up a project. Do NOT load to perform Open Knowledge reads/writes — the runtime guidance for editing markdown inside an initialized OK project ships as a separate project-local skill at `.claude/skills/open-knowledge/` whenever `ok init` runs. If the user appears to be editing markdown inside a `.ok/` project and this is the only OK skill loaded, advise them to re-run `ok init` to install the project-local skill."
compatibility: "Any agent host — no MCP server required. Pure discovery + install guidance."
metadata:
- version: "0.9.1"
+ version: "0.10.0"
author: "Inkeep"
repository: "https://github.com/inkeep/open-knowledge"
---
diff --git a/packages/server/assets/skills/project/SKILL.md b/packages/server/assets/skills/project/SKILL.md
index a34241232..fc11c6533 100644
--- a/packages/server/assets/skills/project/SKILL.md
+++ b/packages/server/assets/skills/project/SKILL.md
@@ -3,7 +3,7 @@ name: open-knowledge
description: "MUST invoke before reading or editing any `.md` / `.mdx` file, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, and the rest). This skill is installed into the repository by `ok init`, so its presence alone means this is an Open Knowledge project — its runtime contract governs every markdown file here, with no need to probe for a `.ok/` directory. Authoritative agent-runtime contract; supersedes the overlapping MCP server `instructions` echo."
compatibility: "Claude Code, Claude Desktop, Claude Cowork, Claude.ai web. Requires Open Knowledge MCP server + code execution."
metadata:
- version: "0.9.1"
+ version: "0.10.0"
author: "Inkeep"
repository: "https://github.com/inkeep/open-knowledge"
---
diff --git a/packages/server/package.json b/packages/server/package.json
index d114b533d..3c0021b73 100644
--- a/packages/server/package.json
+++ b/packages/server/package.json
@@ -1,6 +1,6 @@
{
"name": "@inkeep/open-knowledge-server",
- "version": "0.9.1",
+ "version": "0.10.0",
"license": "GPL-3.0-or-later",
"private": true,
"type": "module",