Single crdt cutover

.changeset/document-retries-its-first-sync.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+A document that fails its first sync now retries itself, at most three times, as soon as the connection reports it in sync, instead of holding the error screen for the life of the window. The stalled-sync warning also names the document it is about.

.changeset/external-link-cue-marks-the-end.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+An external link now shows its leaves-the-workspace arrow once, at its end, even while a collaborator's caret sits inside it. A caret in the middle of a URL used to split the link on screen and give every piece its own arrow until you switched to Markdown source and back.

.changeset/large-documents-stay-responsive.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+Pausing while typing in a large document no longer freezes the editor: the word count is computed off the main thread, and lint markers update only the blocks that changed.

.changeset/markdown-bridge-removed.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+The markdown bridge is gone from the server, so agent writes, disk saves and rollbacks do less work. Its four switches — `bridge.deferGuard`, `fixedPoint`, `preDrain` and `lossDetector` — are removed; `ok config migrate` strips them from an existing config. Eight bridge counters remain in the metrics payload at rest.

.changeset/migrate-prunes-emptied-parent.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+`ok config migrate` no longer leaves an empty parent behind. Clearing the last key under a mapping wrote back a husk — `bridge: {}` once the retired bridge switches were stripped — which validates but leaves a dead stanza in your config file.

.changeset/one-undo-history.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+Undo and redo now run one history across the rich-text and Markdown views, so a step taken in one view can be taken back from the other. Replacing a whole document — an agent rewrite, a Timeline restore — clears that history in both views.

.changeset/server-names-dropped-upgrades.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+The server now says when it drops a WebSocket upgrade. A request no handler claimed was closed without a word in the log, so a routing fault on the server and a connection fault in the browser looked identical. It is now logged with the paths the collaboration host serves.

.changeset/single-source-of-truth.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+The rich-text and Markdown views now read one copy of your document, derived on your own machine. An edit writes only the bytes of the blocks you changed, and collaborators' carets now show across the two views: someone typing in Markdown appears in rich text, and the reverse.

.changeset/slash-command-undo-clears-its-query.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+Undoing a slash command no longer leaves its query behind. Taking back a heading inserted from `/he` put the literal `/he` back into the paragraph, so you had to delete it by hand. The query and the block it produced are now retracted together.

.changeset/trailing-space-saves-with-the-next-word.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+A space typed at the end of a line is no longer saved on its own: it is kept while your caret sits after it, and written to the file with the next word you type. Moving the caret away first drops it.

.changeset/undo-outside-the-editors.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+Undo and redo now reach the app's own history when focus sits outside both editors, after clicking the mode toggle for instance, and from the desktop Edit menu. They previously reached the browser's undo, which could skip an edit or put a deleted one back.

.changeset/undo-survives-writes-while-away.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+Returning to Markdown source keeps your undo history when something else wrote to the document while you were away — a collaborator typing, a change on disk, or a field in the **Properties** panel.

.changeset/version-history-batches-rapid-writes.md

@@ -0,0 +1,5 @@
+---
+"@inkeep/open-knowledge": patch
+---
+
+Two writes to one file landing back-to-back can now share a single version-history entry, because the write path is fast enough that both fall inside the same save window. Nothing is lost: the file holds every write, and edits made seconds apart still get their own entry.

.gitignore

@@ -12,6 +12,8 @@ tmp/
 .source/
 .idea/
 *.tsbuildinfo
+__pycache__/
+*.pyc
 .vercel/
 packages/content/
 test-results/
@@ -29,6 +31,11 @@ blob-report/
 .mirror-output/
 /test-doc.md
 
+# Local-only working notes for the single-CRDT migration. Not part of the public
+# mirror and deliberately kept out of branch history; see the archive branch
+# single-crdt-specs-archive for the versioned copy.
+/feature-specs/
+
 # Env files (keep .env.example committed)
 .env
 .env.local

docs/content/features/assets-and-embeds.mdx

@@ -16,7 +16,7 @@ AI agents add assets through the MCP [`write`](/docs/reference/mcp) tool's `asse
 
 - **Images render inline** with click-to-zoom. Select one to align it left / center / right from the bubble menu, or set alt text and dimensions in its settings.
 - **Video and audio render native players.** The video block also takes YouTube, Vimeo, and Loom URLs and renders each host's own player.
-- **PDFs and other documents** (`.docx`, `.zip`, `.csv`, …) insert a file attachment row — icon, name, size — linking to the file. To render pages in the doc, use the **PDF** block instead: a multi-page viewer with thumbnails, page navigation, and zoom; set `page=3` in its `anchor` setting to open at that page.
+- **PDFs and other documents** (`.docx`, `.zip`, `.csv`, …) insert a file attachment row — icon and name — linking to the file. To render pages in the doc, use the **PDF** block instead: a multi-page viewer with thumbnails, page navigation, and zoom; set `page=3` in its `anchor` setting to open at that page.
 
 In the markdown source, dropped media serializes as `<img>` / `<video>` / `<audio>` and file attachments as wiki-style embeds (`![[report.pdf]]`). You can author the wiki form directly: `![[diagram.png]]` on its own line follows the type rules above, inside a sentence it stays a link, a fragment (`![[report.pdf#page=3]]`) is preserved on the rendered link, and an alias on an image embed sets its alt text (`![[diagram.png|Diagram]]`). Standard `![alt](./chart.png)` image syntax works too. Inside a table cell, escape the alias separator: `![[diagram.png\|Diagram]]` resolves identically to the unescaped form. Byte-for-byte preservation has narrow exceptions, none of them reached by authoring the escape — see [Tables](/docs/features/editor#tables) for what they are.
 

docs/content/features/editor.mdx

@@ -32,13 +32,15 @@ A doc written before this behavior may still carry a blank line at the end that
 
 Markdown problems (hard tabs, heading increments, and the rest) are flagged inline as you write, with a **Problems** panel in the document panel for the whole doc or project. See [Content rules](/docs/advanced/content-rules/overview).
 
-### Undo in source mode
+### Undo
 
-This section is about the Markdown source pane only. The visual editor keeps its own undo history, and none of what follows changes it.
+The Markdown source pane and the visual editor share one undo history. An edit you made in either view can be undone from the other, most recent first. Undo only ever takes back your own edits, never a collaborator's, an agent's, or a change on disk.
 
-Undo in source mode covers the editing you did there. Switching to the visual editor for a look and coming straight back leaves that history intact. But if you leave source mode, by switching to the visual editor or by moving to another tab, and anything writes to the document while you are away, source-mode undo and redo start fresh when you come back. Many things count as a write, not only the obvious ones: your own edits in the visual editor, an agent, a collaborator, a change on disk, a field you change in the **Properties** panel, a fix applied from the **Problems** panel or from the visual editor, or the tail of a large paste you started in source mode that was still landing as you flipped away. Restoring an earlier version from the [Timeline](./timeline-and-recovery.mdx) counts as a write too, so if you restore while you are out of source mode, undo there starts fresh when you come back. Source-mode undo history belongs to the current document session: navigating through enough other documents to evict it, or closing and reopening the app, starts it fresh even if no one rewrote the file.
+Edits by others leave your history as it is. A collaborator typing in another paragraph, a change on disk, or a field you change in the **Properties** panel does not reset it, whichever view you are in.
 
-No text is removed when that happens. One case is still not covered. If a rewrite lands while you are sitting in Markdown source rather than away from it, the history is left as it is, so a single undo can still take back more than you expect.
+Your history starts fresh when the whole document is rewritten at once: an agent replacing the document's content, restoring an earlier version from the [Timeline](./timeline-and-recovery.mdx), or a generated page being regenerated. None of your earlier steps can be applied correctly to a document rewritten from scratch, so they are dropped rather than putting text back in the wrong place. No text is removed when that happens. Undo history also belongs to the current document session: navigating through enough other documents to evict it, or closing and reopening the app, starts it fresh.
+
+One case is still not covered. If a collaborator rewrites a passage you had deleted text from, undoing that deletion can put the text back beside their version.
 
 To go further back, the [Timeline](./timeline-and-recovery.mdx) keeps earlier versions of the whole document. Each entry is a snapshot of the whole document. Agent edits, human edits, and file-system changes are batched into an entry once activity settles. Upstream syncs get their own entry when the sync lands. Restoring an entry brings back that version's content. Restoring is append-only, so the edits you made since then stay on the timeline and you can restore back to them.
 
@@ -366,7 +368,7 @@ Toggling the menu checkboxes flips the underlying config field, which propagates
 
 ## Real-time collaboration
 
-Everything in the editor (body, frontmatter, sidebar toggles) is backed by a CRDT. You and multiple AI agents writing through MCP can edit the same doc concurrently. Per-user presence is shown in the editor header; the **agent activity** view ([Agent activity](./agent-activity.mdx)) groups every burst of agent edits with per-burst diffs and selective undo.
+Everything in the editor (body, frontmatter, sidebar toggles) is backed by a CRDT. You and multiple AI agents writing through MCP can edit the same doc concurrently. Per-user presence is shown in the editor header, and each collaborator's caret is drawn in the text itself, labelled with their name. The **agent activity** view ([Agent activity](./agent-activity.mdx)) groups every burst of agent edits with per-burst diffs and selective undo.
 
 For recovery + history, see [Timeline and recovery](./timeline-and-recovery.mdx).
 

docs/content/features/timeline-and-recovery.mdx

@@ -23,7 +23,7 @@ Project-wide checkpoints saved by agents via the [`checkpoint` MCP tool](/docs/r
 
 OpenKnowledge also saves recovery entries itself. When it detects an external file change on its own and has no acknowledged base to merge the change against, the disk version replaces the document and the pre-change version is preserved as a **Recovered content** entry, which you can restore like any other timeline entry. When an agent write collides with an unmergeable external change instead, the write is refused as a conflict: your current content is kept, the disk change is not applied, and no entry is saved.
 
-The timeline is not the editor's undo history. Each timeline entry is a snapshot of the whole document, while undo steps back through your own recent edits in the pane where you are working. Agent edits, human edits, and file-system changes are batched into an entry once activity settles. Upstream syncs get their own entry when the sync lands. For when source-mode undo starts fresh, see [Editor → Undo in source mode](/docs/features/editor#undo-in-source-mode).
+The timeline is not the editor's undo history. Each timeline entry is a snapshot of the whole document, while undo steps back through your own recent edits, in either view. Agent edits, human edits, and file-system changes are batched into an entry once activity settles. Upstream syncs get their own entry when the sync lands. For when your undo history starts fresh, see [Editor → Undo](/docs/features/editor#undo).
 
 The timeline is per branch: it shows the branch's own edits, plus history from before the branch diverged from `main`. History is stored in a shadow git repo inside your project, so entries and attribution survive app restarts and agent sessions — see [Attribution and collaboration](/docs/reference/core-concepts#attribution-and-collaboration).
 

knip.config.ts

@@ -141,12 +141,12 @@ export default {
       entry: ['src/**/*.test.{ts,tsx}'],
     },
     'packages/server': {
-      entry: ['src/**/*.test.ts', 'src/parse-worker.ts'],
+      entry: ['src/**/*.test.ts'],
       project: 'src/**',
       ignoreDependencies: ['@types/shell-quote'],
     },
     'packages/cli': {
-      entry: ['src/**/*.test.ts', 'scripts/*.ts', 'tests/**/*.ts', 'src/parse-worker.ts'],
+      entry: ['src/**/*.test.ts', 'scripts/*.ts', 'tests/**/*.ts'],
       ignoreDependencies: ['yjs'],
     },
     'packages/desktop': {

package.json

@@ -38,7 +38,6 @@
     "measure:stress": "cd packages/app && pnpm run measure:stress",
     "measure:sweep": "cd packages/app && pnpm run measure:sweep",
     "measure:generated-index-sweep": "pnpm --dir packages/server run measure:generated-index-sweep",
-    "measure:observer-a-drain": "pnpm --dir packages/server run measure:observer-a-drain",
 
     "prepare": "bash scripts/husky-prepare.sh",
     "changeset": "changeset",