[AmriteshKhare]

Summary

artemis run --verification-level and --explorer-pro-mode were accepted by the CLI, but the default daemon dispatch never sent them. A Pro task scheduled through the daemon therefore ran with the configured Checker preset and Explorer tier instead of the flags on the command line.

submit_task_to_daemon already accepts verification_level and explorer_mode, and the worker turns those fields back into --verification-level and --explorer-pro-mode. artemis batch and artemis run --standalone already forwarded both knobs. This change passes the same fields from artemis run on the daemon path.

Fixes #199

Test plan

• uv run pytest tests/unit/test_cli.py::test_cli_run_forwards_pro_tuning_to_daemon tests/unit/test_cli.py::test_cli_run_forwards_pro_tuning_in_standalone_mode
• Daemon dispatch keeps both flags together, and each flag when it is set alone
• --standalone still passes verification_level and explorer_pro_mode into embedded execution
• uv run ruff check and uv run ruff format --check on the touched files
• Run artemis run --profile pro --verification-level strict --explorer-pro-mode ultra "<goal>" against a live daemon and confirm the worker command includes both flags

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.