[codex] Fix PyCharm core test run configs

[jpmorard]

Summary

Fix three tracked PyCharm core pytest run configurations that were bound to the uv (agi-cluster) SDK but had an empty working directory. The generated CLI wrappers were regenerated so the shell launchers now run from the same src/agilab/core/agi-cluster directory.

Repro

PyCharm test base_worker, test dag_worker, and test work_dispatcher launched with an empty WORKING_DIRECTORY, unlike the sibling core pytest configs for pandas, polars, and distributor tests.

Root Cause

The affected tracked run configurations did not set the agi-cluster project working directory, so PyCharm could resolve the test target with the right SDK but run from the wrong/default directory.

Regression Test

test/test_setup_pycharm.py::test_tracked_run_configs_use_valid_uv_sdk_bindings now rejects agi-cluster pytest configs targeting src/agilab/core/test/ unless their working directory is $PROJECT_DIR$/src/agilab/core/agi-cluster.

Validation

• uv --preview-features extra-build-dependencies run python tools/generate_runconfig_scripts.py
• uv --preview-features extra-build-dependencies run pytest -q -o addopts='' test/test_setup_pycharm.py::test_tracked_run_configs_use_valid_uv_sdk_bindings
• uv --preview-features extra-build-dependencies run python tools/impact_validate.py --staged
• uv --preview-features extra-build-dependencies run pytest -q -o addopts='' test/test_setup_pycharm.py
• pre-push guard passed

Review Evidence

Not used.

Agent Metadata

• Tokki version: tokki 1.0.19
• Agent/runtime: Codex CLI, version unavailable
• Model: GPT-5 Codex
• Reasoning effort: unknown
• /fast mode: no