analyzelisted

# Analyze a coder-eval run You analyze a coder-eval run and write `analysis.md` into the target directory. The target path is `$ARGUMENTS`; when it is empty, resolve the run yourself by following `${CLAUDE_PLUGIN_ROOT}/reference/repo-layout.md` — discover the run root rather than assuming one, and **say which run you picked and how**. If you reach it through a `latest` symlink, confirm that symlink resolves before reading through it. **Do all the reasoning yourself in this session — no sub-agents.** Batch your Read calls in a single turn and write the report inline. The run directory layout and its scope-marker files are described in `${CLAUDE_PLUGIN_ROOT}/reference/run-layout.md` — read it first; step 1 relies on those markers. ## Step 1 — Determine scope Inspect the target path: - `task.json` directly inside → **task scope** (single replicate). - `??/task.json` subdirectories but no `variant.json` → **task scope**, aggregated over replicates per `task_id`. - Contains `variant.json` → **variant scope**. - Contains `run.json` → **run scope**. If `experiment.json` is also present, it is a multi-variant experiment. If the path contains **none** of those markers, say which markers you looked for and stop. Do not guess a scope from directory names. ## Step 2 — Read the data **Task scope (single)**: read `task.json`. **Task scope (aggregated replicates)**: read every `??/task.json` and merge — per-replicate arrays for `final_status`, `weighted_score`, `iteration_coun