Third review round on field-merge sending: - A successor names its change from the predecessor's payload when it is made, while it is known whether the canvas drew the predecessor, and is saved that way, so a change set back in flight survives a restart. Promotion only keeps a whole write or delete on the revision it was made from. - A send that failed drops its live status, so its retry is checked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dara Adedeji committed on 10/10/2026, 6:57:15 AMparentf052e6c
Checks
- SuccessfulCodeRabbitGitHub
Review completed
- Skippedlinux-buildGitHub
- Skippedwindows-buildGitHub
- Skippedpresence-workerGitHub
- Skippednative-replayGitHub
- SkippedconvexGitHub
- Skippednative-bridgeGitHub
- Skippedwindows-testGitHub
- Successfulclient-contractGitHub
- Successfultest (shard 1)GitHub
- Successfultest (shard 0)GitHub
- SuccessfulwebGitHub
- SuccessfulanalyzeGitHub
- SuccessfulchangesGitHub
2 files changedLine totals unavailable