Temp folder fills up with mongodb-memory-server data (hundreds of GB)

[Mediainvita]

Problem

When using AutoForge with projects that use mongodb-memory-server for testing, the Windows temp folder (%TEMP%\mongodb-memory-server) accumulates hundreds of gigabytes of MongoDB binary downloads that are never cleaned up.

I have to manually delete this folder twice a day - it grows to 950GB+ and fills the entire drive.

Steps to reproduce

1. Create a project that uses mongodb-memory-server for tests (e.g., a Node.js backend with Jest)
2. Run the AutoForge agent multiple times
3. Check %TEMP%\mongodb-memory-server* folder size

Expected behavior

Temporary test files should be cleaned up after agent runs, or use a persistent cache location that doesn't grow unbounded.

Suggested fixes

1. Add cleanup hook - Delete mongodb-memory-server temp folders after agent completion/crash
2. Configure cache - Set MONGOMS_DOWNLOAD_DIR environment variable to a persistent location
3. Document workaround - Add note in docs for projects using mongodb-memory-server

Current workaround

Manually delete %TEMP%\mongodb-memory-server* or use a cleanup script.

Environment

• OS: Windows 11
• Python: 3.14.0
• Node.js: 24.11.1
• AutoForge: commit 486979c (tested), now updated to latest master
• Affected: Projects using mongodb-memory-server for tests

[chrislangston]

@Mediainvita Can you submit a PR for this? Seems like a good candidate for claude code to outline the necessary changes.

[Mediainvita]

Works for my setup now. However after thinking about the issue and fix a little more, I decided to go a little different way from what Claude proposed here. It´s more plausible. Delete is triggered by startup of maestro.