docs: align SubmitQueue workflow terminology with land - #691
Open
behinddwalls wants to merge 1 commit into
Open
Conversation
This was referenced Sep 8, 2026
behinddwalls
marked this pull request as ready for review
September 8, 2026 05:22
## Summary ### Why? The implementation now distinguishes SubmitQueue's land workflow from Runway's merge execution contract, but stale documentation and API comments would continue to blur that boundary for maintainers and users. ### What? Update guides, RFCs, package documentation, interface comments, protobuf comments, and generated protobuf documentation to use land terminology within SubmitQueue while retaining merge terminology for Runway and generic merge operations. ## Test Plan - ✅ `make proto` - ✅ `make gazelle` - ✅ `make lint`
behinddwalls
force-pushed
the
preetam/land-terminology-docs
branch
from
September 8, 2026 05:30
e15a929 to
3fd4150
Compare
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
1 participant
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.
Summary
Why?
The implementation now distinguishes SubmitQueue's land workflow from Runway's merge execution contract, but stale documentation and API comments would continue to blur that boundary for maintainers and users.
What?
Update guides, RFCs, package documentation, interface comments, protobuf comments, and generated protobuf documentation to use land terminology within SubmitQueue while retaining merge terminology for Runway and generic merge operations.
Test Plan
make protomake gazellemake lintIssues