Repository navigation
Delete backend relocation modules and unify their behavior owners - #2665
Merged
1 commit merged intoOct 23, 2026
Merged
1 commit merged into
1 commit merged into
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
This was referenced Oct 23, 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.
Remove the three relocation modules introduced by #2635 and put their behavior on the existing Thread, registry-privacy and Pi event owners. Deletes 296 lines and adds 198 (net -98).
ThreadRename,PlainRenameandPrivateOwnerRenameare deleted, including their privacy-to-handler map and registration hook.RegistryPrivacy.renamedispatches on the existing public/private owners;ThreadManagementapplies the shared title, activity, runtime, ledger and catalog updates. The private owner retains the SQL/registry intent, compensation and completion behavior.RenameThreadResultlives beside its producing operation.ThreadProvenancelives withThreadas its existing parent. Session-file, title, tags and backend registration metadata/defaults are inherited once; the repeated child declarations are deleted. Archived provenance still has no execution state. All Core consumers and test imports target the owner directly.PiEventowns both declaration registration and phase transition behavior. The forwarding-onlyPiTurnPhaseparent is deleted. Existing MRO start precedence, end-event union and specialized compaction/tool hooks are retained. The two remaining derived phase maps are still tracked as unfinished roster work; moving them does not mark that phase complete.RegistryPrivacy,PiEvent). No aliases or re-exports remain for the deleted modules.Validation is assigned to the single integrator under Tristan's current order: no worker tests, debt scans or census runs. The attempted broad inventory was stopped without a completed current-head census; no global AST completeness or runtime equivalence claim is made. The migration used exact AST declaration spans for source edits and the source/import trace retained from the existing ownership work.
Integrator touched checks:
tests/test_operations.py,tests/test_acp_private_nk_delivery.py,tests/test_importing.py,tests/test_historical_views.py,tests/test_pi_rpc_nominal.py,tests/test_phase_evidence.py, andtests/guards/test_source_proof_ownership.py. Integrate this head into the singleintegrationbranch; do not launch a separate worker suite.Assumed: the integrator owns import/runtime and behavioral qualification at the combined head. No install or live verification is claimed.