| English | 中文 |
Apply the workflow prompt and generate generated_regression.py plus the explicit public task config/examples/ml-regression/workflow-synthetic.json for the following bounded task:
assets/data/03_atmospheric_transport/SyntheticCausal/v1/rows.csv; do not inspect original research data or personal settings.outcome from x1, x2 and treatment; the name treatment is a synthetic predictor here, not a causal-effect request. Use the released dataset labels and all 400/100/100 train/validation/test rows, with id as the key.ToolRunnerService.run('ml_regression_workflow', ...), using explicit result_scope='workflow'. Default to preflight; execution requires --execute. No project ID, arbitrary command, automatic installation or network access.Expected deliverables: an inspectable program, schema-valid task, negative engineering checks and actual synthetic execution evidence. The agent authors/reviews code in the task session; no extra code-generation service is implied.
Follow the common execution/process-record contract. New runs use a compact YYYYMMDDHHmm timestamp plus a public task name; the internal run ID only correlates receipts. Preserve gen_script/, events.jsonl, paired retrospective documents and overall workflow.json. No new source_snapshot/ is created; verified redundant synthetic batches are cleaned only with explicit authorization. Generation basis is an explicit design summary, not an uncaptured historical generation transcript.