What is the recommended method for purging inconsistent build states after a failed Meteor update?

Build Environment Consistency

When executing meteor update, the build tool modifies the package manifest and updates the local runtime environment, including specific Node.js and MongoDB versions. If the upgrade process is interrupted or fails, the .meteor/local directory may enter an inconsistent state that persists even after reverting the .meteor/versions file via version control.

While reverting the manifest restores the targeted version, residual build artifacts or cached dependencies in the local directory can cause runtime errors or build failures during the recovery process.

Technical Constraints

• Version control handles the manifest and version files but does not track the .meteor/local directory.
• Manual purges of build artifacts are often necessary to ensure a clean state.

Which specific directories within .meteor/local must be removed to fully reset the build environment without losing application-specific local configuration? Does a full deletion of the local directory impact the stability of the MongoDB instance managed by the Meteor tool?