docs: plan PR #145 restructuring - #508
Draft
ajroetker wants to merge 3 commits into
Draft
Conversation
ajroetker
force-pushed
the
docs/restructure-prs
branch
from
August 19, 2026 16:54
cc94ef9 to
af66e76
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.
What changed
Adds a concrete restructuring plan for #145 with:
Why
The combined PR spans independent SQL, relational, graph, storage, algebraic, object-store, catalog, and lake concerns. Recording the intended landing order prevents hidden dependencies from being reintroduced during extraction.
Impact
No runtime behavior changes. This is the coordination document for the replacement PR series.
Validation
git diff --checkpassed