v0.3.1

Bugfixes

• Emit the exact seven-field CMS contract envelope from installed Salesforce CLI subprocesses, including partial and blocked results.
• Resolve the plugin version from the installed runtime so command envelopes and exported package provenance report the published version.
• Preserve deterministic import command exit state across repeated command execution.
• Publish completed workspace export directories atomically without replacing a destination created concurrently.
• Retry only transient Windows EPERM and EBUSY atomic rename failures with bounded delays while preserving the original error.
• Use uniquely owned sibling temporary directories and preserve destination and temporary artifact safety when cleanup fails.
• Adapt the native Linux and macOS no-replace binding to its parent-directory file descriptor contract.

Testing

• Validate packed plugin subprocess output from an isolated Salesforce CLI installation.
• Add real no-clobber filesystem tests across Linux glibc, Linux musl, macOS, and Windows.
• Stabilize packed-install verification on Windows with a bounded setup timeout and cleanup retry.
• Bind plugin-version assertions to package metadata so release version bumps are verified rather than hard-coded.

Dependencies

• Raise the minimum Node.js version to 22.19 and retain support below Node.js 25.
• Pin platform-specific atomic no-replace native packages to 0.5.0-beta.1.
• Include the approved npm audit lockfile refresh.

Full Changelog: v0.3.0...v0.3.1