On Windows, path.resolve returns whatever case the caller supplied while
fs.realpathSync.native returns the OS-canonical case. These produce
different SHA-1 hashes and therefore different session tmpdir slots —
the test checks one slot while the implementation writes to another,
causing pointer lifecycle assertions to always fail.
Fix: use realpathSync.native with a fallback to path.resolve when the
planning directory does not yet exist.
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
40fc681b28