Classic298 9189033c37 fix: seed a note's collaborative document from its stored content ... A note written outside the editor (the write_note tool, or any POST to /api/v1/notes/create) has no Yjs update history, so the first client to open it received an empty document and the save that followed wrote that emptiness back over the note. The content was still in the database up to that moment, then gone, with only the title left. The server now builds the Yjs document from the note's stored ProseMirror json when there is no update history yet, so a client opens the note with its real content instead of a blank document. The client id is derived from the content, which makes two workers seeding the same note a no-op rather than a duplication. Notes that only carry markdown still rely on the editor's own seeding, since building ProseMirror json from markdown server-side would mean reimplementing the editor's schema in Python. That path was also gated on being the only session joined to the note, so a second viewer disabled it entirely; it now elects the lowest joined session, which keeps a single seeder without giving up on seeding.		2026-08-13 13:28:10 +02:00
..
main.py	fix: seed a note's collaborative document from its stored content	2026-08-13 13:28:10 +02:00
utils.py	fix: seed a note's collaborative document from its stored content	2026-08-13 13:28:10 +02:00