Repository navigation
Reduce CLI overhead and protect checkout updates - #77
Merged
Merged
Conversation
Mathih13
marked this pull request as ready for review
October 12, 2026 09:43
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.
Checkout updates could discard clean local commits, while package commands performed module builds and publication for changes that did not need them. This change protects local work and narrows those operations.
updaterefuses commits absent fromorigin/main. Explicit--reset-mirrorretains the prior revision on a recovery branch; both modes protect tracked edits and conflicting untracked/ignored files across the entire repository. Existing recovery branches are never overwritten.lyracore-ops service reconcile. It uses the selected Core checkout without fetching or resetting it. The old developer command returns migration guidance.--all, and clarify that re-enabling source does not restore torn-down data.Compatibility: host operators must install the separate ops binary (documented in
docs/operations.md). Rewritten mirror history now requires the explicit reset flag. No dependencies were added.Retained checks: artifact canonicalization, detailed import assertions and the Loot Roll upgrade guard remain. Removing them safely requires replacement Core interfaces and an upgrade-support decision;
docs/contract-ownership.mdrecords those prerequisites. This PR does not claim to complete that cross-repository extraction. Rust publication remains inventory-wide because an offline disable leaves no remote teardown record and may still require code removal.Validation: 804 unit tests and 9 integration tests pass, including actual CLI execution against disposable local Git repositories and focused help outside a checkout.
cargo +1.93.0 fmt --all --check, Clippy with-D warnings, Rust 1.85 all-target checking, the prune shell tests, and all 15 Python deployment tests pass. No live realm or host service was changed.Adversarial review: two independent review passes plus direct Git probes identified and resolved recovery-branch overwrite, nested-workspace ignored-file loss, and skipped publication after offline Rust-package disable. Regression coverage exercises each case.
Integrated the generated-bindings command from main into the shared help catalogue and concise README. The combined tree passes 813 Rust tests, formatting, strict Clippy and Rust 1.85 checks; independent integration review found no remaining regressions.