fix: preserve file operation history across native fallbacks - #1
Open
MDGChamomile wants to merge 1 commit into
Open
MDGChamomile wants to merge 1 commit into
MDGChamomile wants to merge 1 commit into
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.
Summary
Why
Pi intentionally does not treat arbitrary extension compaction details as native file-operation metadata. This extension restores Pi-shaped
readFilesandmodifiedFiles, but previously did so only after configuration, model lookup, and authentication checks.When one of those checks returned early, native fallback reused the same preparation without the earlier cumulative file history. That could truncate the
<read-files>and<modified-files>context carried into later compactions. This affects compressed working context only; it does not revert, delete, or corrupt files.Testing
bun run check