fix: add automatic temp folder cleanup at Maestro startup

[Mediainvita]

Summary

Adds automatic cleanup of stale temporary files at Maestro (orchestrator) startup to prevent temp folder bloat.

Problem: When AutoForge runs agents that use Playwright for browser testing or mongodb-memory-server for database tests, temporary files accumulate in the system temp folder. These files are never cleaned up automatically and can consume hundreds of GB over time.

Solution: New temp_cleanup.py module that runs at every Maestro startup (Play button click or auto-restart after rate limits).

What gets cleaned up

Pattern	Description
playwright_firefoxdev_profile-*	Playwright Firefox browser profiles
playwright-artifacts-*	Playwright test artifacts
playwright-transform-cache	Playwright transform cache
mongodb-memory-server*	MongoDB Memory Server binaries
ng-*	Angular CLI temp directories
scoped_dir*	Chrome/Chromium temp directories
.78912*.node	Node.js native module cache (~7MB each!)
claude-*-cwd	Claude CLI working directory temp files
mat-debug-*.log	Material/Angular debug logs

Safety

• Only deletes files older than 1 hour - safe for running processes
• Uses ignore_errors=True for graceful handling of locked files
• Non-blocking: errors are logged but don't stop the agent

Changes

• New file: temp_cleanup.py - Cleanup module with cleanup_stale_temp() function
• Modified: autonomous_agent_demo.py - Calls cleanup at orchestrator startup (not in subprocess agents)

Testing

Manual test:

python temp_cleanup.py

Output: Cleanup complete: X dirs, Y files, Z MB freed

Integration test:

1. Create test files with old timestamps:

   mkdir -p "$TEMP/playwright-artifacts-TESTDIR"
   touch -d "2 hours ago" "$TEMP/playwright-artifacts-TESTDIR"
   touch -d "2 hours ago" "$TEMP/.78912TEST-00000000.node"

2. Start Maestro (click Play button in UI)
3. Press D to open Debug panel
4. Look for: [CLEANUP] Removed X dirs, Y files (Z MB freed)

Verified working:

Screenshot shows cleanup running at Maestro startup:

00:21:15 [ENTRY] autonomous_agent_demo.py starting...
00:21:15 [CLEANUP] Removed 1 dirs, 9 files (33.2 MB freed)
00:21:15 [ORCHESTRATOR] run_parallel_orchestrator called with max_concurrency=1

Why cleanup at Maestro startup?

• Reliable hook point - runs every time Play is clicked or agent auto-restarts
• No background timers needed - no extra complexity
• Frequent enough - rate limit restarts happen every ~5 hours minimum
• Safe timing - cleanup runs before new temp files are created

Closes #155

Co-Authored-By: Claude Opus 4.5 noreply@anthropic.com

[leonvanzyl]

Thanks