Repository navigation
Migrate current-owner legacy install claims without runtime writes - #200
Merged
Merged
Conversation
… revisions Compute desired coverage for migrate-legacy like adopt-legacy, record it in the plan digest, and refuse entries the graph no longer installs unless --allow-undesired is passed. Refuse an orphan destination graph lock, re-check source and destination revisions after the apply re-read, and treat already-migrated --path selections as a no-op. Harden the snapshot copy check and include --reason in the printed apply command.
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.
Requested by Joseph · project thread
Legacy ownership handoffs can leave entries owned by the current workspace in an old state-key manifest. Install then treats their destinations as unmanaged because it reads the current state key.
Add
ownership migrate-legacy, a read-only plan by default with explicit source selection, a digest, and expected source/destination/inventory revisions. Applying moves only verified current-owner metadata through guarded journals, including complete merge contributions and managed instruction blocks. Drift, overlapping claims and pending journals are refused. Destination-first commits support recovery and exact-duplicate retirement without runtime writes.Includes CLI, lifecycle and confined-worker coverage plus a disposable-snapshot operator checker and documentation. Validation runs in CI. The shared integration projection has a pre-existing replay conflict in another stack; it was not resolved for this change. No merge or live runtime operation is part of this PR handoff.
Validation on head
b417ca0: CI passed release metadata checks, typecheck, build, the real isolated service-user transport smoke, CLI fleet install/update/recovery smoke, and all 1,215 tests across 95 files. Independent source review found no remaining blocking issues after corrections to fixture schema, explicit state-key compatibility and durable recovery. The operator's real-snapshot copy check is still pending; the PR remains open and must not be merged as part of this handoff.