Temp Directory (/tmp) not cleaned after run, causing errors

[NeoMod]

BUG Description:

The issue has been mentioned before (#418) and it is still present: the container does not clean up the /tmp directory after execution. This leads to recurring ENOTEMPTY errors when attempting to remove Puppeteer-related profile directories, which in turn causes failures in downstream logic (e.g., starting the claim process, sending ntfy notifications, running again after first run). (verified using the "debian" image)

Logs extract:

WARN: Unable to delete folder
    file: "puppeteer_dev_profile-UY4tej"
    err: {
      "type": "Error",
      "message": "ENOTEMPTY: directory not empty, rmdir '/tmp/puppeteer_dev_profile-UY4tej/segmentation_platform'",
      "stack":
          Error: ENOTEMPTY: directory not empty, rmdir '/tmp/puppeteer_dev_profile-UY4tej/segmentation_platform'
      "errno": -39,
      "code": "ENOTEMPTY",
      "syscall": "rmdir",
      "path": "/tmp/puppeteer_dev_profile-UY4tej/segmentation_platform"
    }

WARN: Unable to delete folder
  file: "puppeteer_dev_profile-TiaNkd"
  err: {
    "message": "ENOTEMPTY: directory not empty, rmdir '/tmp/puppeteer_dev_profile-TiaNkd/GrShaderCache'"
  }
...
ERROR: Error sending Ntfy message. Please check your configuration
status: 404
message: "Request failed with status code 404"

Additional context

To resolve the issue, I implemented a cleanup routine that runs between container executions to clear the /tmp mount. This resolved the issue and restored full functionality, including successful notification dispatch. Longer testing is needed to ascertain if this is enough to handle the error, but I would suggest anyone having the same issue to test if this workaround solves it.