Repository navigation
fix: stabilize Windows safety qualification - #68
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.
Windows junction writes now stage through canonical in-root paths and refuse swapped ancestors before opening scratch. Windows doctor fixtures use resolved junction targets. The B04 oracle measures child event-loop duration, excluding process startup. Publisher-budget fixtures retain all 400 files while batching writes. Live-qualification hook limits reflect the measured 34.6-second Windows runtime.\n\nValidation: npm run check passed (189 files; 2,982 tests). npm run verify:package passed (115 tests). npm run test:artifact passed (15 tests). npm audit --omit=dev --audit-level=high found zero vulnerabilities. No live-model calls were made.