fix(onset): landing again never lands twice; API edits keep what others landed
Radin committed
- Author
- Radin · radin@coline.appOct 31, 2026 at 20:36
- Committer
- Radin · radin@coline.appOct 31, 2026 at 21:27
- Parents
- 115913154a49
fix(onset): landing again never lands twice; API edits keep what others landed A land whose answer was lost (dropped connection, client gave up) used to land again when retried, and could silently undo versions that landed in between. Both hosts now answer a landed change's repeat with the first answer, keep its record as it landed, and reopen it only through on undo (the take-back land names the version it undoes). A change whose edits main already has is refused instead of adding an empty version. Edits over HTTP and MCP replaced files whole on the latest main, dropping what others landed to them since. Editing a file that's on main now needs base (onset_read says which version it read), and the same edits sent again answer as the first time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8 files changed+247−10