Reconcile protected library merges into TreeDX - #161
Merged
Conversation
This was referenced Sep 1, 2026
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.
Outcome
Protected library branch merges are detected automatically, fetched into TreeDX, promoted to the current logical view, fully reindexed, and queued for the canonical R2 file mirror.
Work authority
Contributor mode (select one):
Plan
Poll ready GitHub library bindings for protected-branch movement, enqueue an idempotent control-plane operation, use assignment-scoped credential delivery to fetch the exact head into TreeDX, promote the logical branch, refresh graph and search, update binding evidence, and enqueue the existing R2 mirror operation. Status: implemented and verified.
Changes and commits
Verification
Risk and rollback
Risk is limited to background reconciliation of ready GitHub-backed TreeDX libraries. Each exact remote head uses a deterministic idempotency key; promotion uses expected-head concurrency control; indexing must verify the exact resolved commit before the binding advances. Roll back by reverting 3411303; no destructive schema migration is involved.
Completion summary
The missing GitHub-to-TreeDX direction is implemented. Existing TreeDX-to-GitHub/R2 replication remains intact, and the new operation hands the reconciled exact head to that established mirror path.
AGPL committer authorization
The authenticated PR author is checked by the repository-owned authorization workflow.
Submission checklist