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
1 participant
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.
Adds --unpacker support for frontier-LLM workflows by embedding the reconstruction helper at build time and appending a self-describing unpacker appendix to full exports. The export format now includes explicit file-section markers so metadata and helper sections are unambiguous, and the unpacker parser was tightened to preserve unknown escapes and ignore non-file sections safely.
This PR also hardens several lower-level paths: resolved-mode validation for --no-default-ignore, narrower sensitive-file detection, safer short-read handling, warning-clean binary/shebang/process-exec code, bounded Git output capture, stronger temp-file durability, and clearer reporting when unreadable directories are skipped. make test passes, and the code also builds cleanly with -Wcast-qual.