Uh oh!
There was an error while loading. Please reload this page.
feat: recover read-only static inspection protocol - #270
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 freeto 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.
Recovery scope
Recover exact local commit
fbb1e8bb1bf840bb45f83e1c2eb4cf1de39d4c3b, which existed only in a Codex worktree and saved patch after publication was previously blocked.The commit adds a read-only
zed inspect --workspace PATH --jsonimplementation, static manifest/lock/materialization/Git/mise/Nix findings, structured recommendations, explicit network opt-in, documentation, and tests matching zed-cli issues #191 and #192.Validation
git diff --checkpassed.cargo fmt --all -- --checkpassed.token; no credential value or private key was found.Reconciliation boundary
This is a draft recovery candidate based on
bf1dc05e05900748a44ee02e7c507fd65bab4c7a. Currentmainhas evolved substantially, and another saved worktree implements a competing command/schema shape. Preserve this exact work for semantic reconciliation; do not merge or resolve conflicts mechanically.Refs #191 and #192.