Do we want to pass env name, task id etc. to miner deployments?

[Shr1ftyy]

When running some end-to-end tests, I noticed these logs from a miner deployment:

INFO:     10.42.6.101:33730 - "POST /act HTTP/1.1" 200 OK
INFO:     10.42.4.189:48566 - "POST /act HTTP/1.1" 200 OK
INFO:     10.42.6.101:36888 - "POST /act HTTP/1.1" 200 OK
{"timestamp": "2026-02-03T06:38:21+0000", "level": "INFO", "logger": "kinitro.policy", "message": "reset completed", "operation"
: "reset", "duration_ms": 0.06, "env_id": "metaworld/door-open-v3", "task_id": 2092368852}
INFO:     10.42.4.189:54808 - "POST /reset HTTP/1.1" 200 OK
INFO:     10.42.3.164:56274 - "POST /act HTTP/1.1" 200 OK
INFO:     10.42.5.174:47184 - "POST /act HTTP/1.1" 200 OK

should we be passing env_id to the miner? could this be used to game the env somehow? requires further analysis.