fix: run restored workspace binaries - #99
Merged
Merged
Conversation
Resolve explicit terminal targets against workspace files and load their exact bytes, avoiding stale cached artifacts after a project is reopened.\n\nFixes #98
2 tasks
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.
Closes #98. Terminal ./path commands now resolve matching workspace files after a project is reopened and load the exact file bytes for execution. Explicit targets cannot fall back to stale cached artifacts; toolbar/default runs retain their current-session cache. Coverage includes restored nested targets, missing targets, and stale-cache avoidance. Verified with npm run test:e2e, npm run lint, and npm run build.