Ruben FiszelandClaude Opus 5 ccea81f5e9 refactor: the server follows a moved draft through a move record, not client-sent row ids ...

A move writes old path -> new path (per workspace and kind, per owner for a
draft-only move) in its transaction; a draft save or discard addressed to a
path the caller has no draft at resolves through it and keeps the moved
draft's path keys. Creating an item at a path drops the records leaving it.
Every writer (edit routes, sessions, chat, CLI, the tab-close flush) follows
without passing an id, so the id plumbing is gone.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-14 19:14:26 +02:00

..

flows.rs

refactor: the server follows a moved draft through a move record, not client-sent row ids

2026-09-14 19:14:26 +02:00

lib.rs

chore: split api-scripts and api-flows

2026-02-11 13:27:00 +00:00