dolt/tmp keeps growing after enabling automatic GC

## Summary

I'm running Dolt **v1.81.7** on a database of about **30 GB**.

Earlier today I ran a **manual GC** (`CALL dolt_gc()`) but did not wait for it to finish — I had to interrupt it midway. After that, I enabled **automatic GC** in the Dolt SQL Server config.

Since then, I have observed that the **`.dolt/tmp` directory keeps growing continuously**, and it is now about **38 GB** in size even though the main database directory remains about **30 GB**.

## Environment

- **Dolt version:** v1.81.7
- **Database size:** ~30 GB
- **Automatic GC:** enabled via config.yaml
- **Manual GC:** attempted earlier and was interrupted
- **Observed `.dolt/tmp` size:** ~38 GB

## What I Observed

I have **not seen any automatic GC completion logs** in the server log. I believe GC is still ongoing because the size of the .dolt/tmp directory is still increasing rapidly. and the main database size remains ~30 GB

## Questions

1. Is it **expected** that `.dolt/tmp` keeps increasing under these conditions?
2. Should `.dolt/tmp` be automatically cleaned up once GC completes (either manual or automatic)?
3. How can I tell if an automatic GC job is currently running or whether it has finished?
4. Is it safe to **manually delete** files in `.dolt/tmp` ?

Thank you for your help!