Repository navigation
IR-736: add distributed Git lock coherence command - #133
Merged
Merged
Conversation
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.
Implements the reviewed FR-027 developer gate as
quire check-lock <Cargo.lock>.... It parses real TOML and Git URLs, rejects duplicate agent-ix package names and split resolved revisions within each canonical repository, and reports all affected locks deterministically through the existing diagnostic and outcome contract. It reads locks without fetching or changing them.Focused validation: format check and targeted Clippy pass; nine command-level integration tests plus the existing help snapshot pass. Tests exercise normalization, malformed inputs, multiple locks, stream formatting, permission/output failures, unchanged inputs, and actual strace evidence for no child or network invocation. The original IR, CG, and RT AWK checkers each accept the retained split fixture (exit 0); the new command refuses that same fixture (exit 2).
Titan candidate installation passed using the normal Git Cargo installation route at the exact reviewed candidate head. The installed executable, resolved through PATH, passes aligned/split checks (0/2); independent strace runs each show one initial execve and no inet sockets. No release publication, remote-host qualification, or consumer Makefile/script migration is claimed. IR-641 owns subsequent consumer adoption. The code lead owns the final aggregate gate after independent review.
Refs IR-736.