Repository navigation
Handle inspection comparisons and release v0.6.3 - #16
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.
Commit inspection can display ordinary comparison differences as failures and leave JSON snapshots at shared temporary paths. Teach the prompt to handle documented comparison status 1 at the command boundary, preserve real comparison/pipeline/validation/test errors, and keep necessary temporary files in one unique task-owned directory with cleanup on success and failure. The renderer continues to preserve nonzero command diagnostics.
Prepare v0.6.3 metadata and download examples. Regression coverage runs real shell comparisons for equal/different inputs, missing inputs, validation failures, and pipeline failures; it also verifies unique scratch directories, cleanup, and preservation of neighboring files.
Validation: formatting and workspace Clippy; all 97 tests; package publish dry-run and inspection of the 17 expected package files; independent review with no findings. Two live Codex smoke tests verified canonical JSON inspection without a false failure, rejection of invalid JSON without a commit, unchanged file contents, preserved neighboring data, and no comparison files left behind. Both runs chose in-memory comparison; owned-directory cleanup on success and failure is covered by the real-shell integration test.