Repository navigation
Fix workspace validation and request resource completeness - #21
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.
Preflight could report a workspace ready even though restore rejected a normalized file/descendant collision. Workspace deltas could delete excluded descendants, and request projection omitted resources referenced only by selected tools. Fix all three behaviors in both Python and TypeScript.
Add shared positive and negative regression cases, update the continuation parity corpus, and exercise tool-resource projection through both CLIs. ASIF stays at 0.4, the package at 0.4.0, continuation/profile reports at 0.2, and request projection at 0.1.
Validation passed:
These remain locally authored reference implementations and synthetic checks; independent or live-runtime interoperability is not established by this PR.
Closes #12
Closes #13
Closes #14
The remaining backlog is tracked separately in #15–#20; #6 links its two deliverables (#16 and #17). Existing #5 and #7 remain open.