docs(runway): state the merge target atomicity guarantee in the contract - #722
Merged
Merged
Conversation
A committing merge has always been all-or-nothing against its merge target by construction of the Git merger, but the property was only written down in the Git merger's own README. This documents it as part of the Merger interface contract, the published wire contract README, and the Runway workflow RFC, so callers and future backends can rely on it without reading the Git implementation. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
|
sbalabanov
marked this pull request as ready for review
September 17, 2026 18:03
behinddwalls
approved these changes
Sep 17, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Writes down, as part of the written contract, a property that has always been true of Runway's committing merge by construction of the Git merger: it updates the merge target at most once per request, and afterwards either every step is reachable from the target or the target is unchanged. Adds this to the
Merger.Mergedoc comment, theapi/runway/messagequeuewire contract README, and the Runway workflow RFC.🤖 Generated with Claude Code