human-eval-handoff-repair

# Human Eval Handoff Repair Use this skill when the user asks to inspect, repair, migrate, or validate human-evaluation packages or filled annotation CSVs, especially when multiple package versions exist. ## First Principle Never trust row number, filename, or visible ID alone. Treat a filled CSV as usable only after it is aligned to the target public package by stable task-specific keys and its editable labels pass schema checks. Do not fix labels by guessing. If a row cannot be matched safely, leave its annotation fields blank and produce a refill/import template plus an unmatched reference file. ## Inputs To Locate - Target public handoff package folder or ZIP. - Filled CSVs from annotators. - Any older package claimed as the source version. - Current task schemas from the target UI data or target task CSVs. - If relevant, QC reports from the target package. Prefer a user-specified output directory. If none is specified, write generated reports and repaired files under `codex_outputs/` in the current workspace. Avoid synced personal document folders unless the user explicitly asks for them. ## Task Types And Stable Keys Use these stable keys before copying any labels: - Claim Warrant Audit: `item_id`, `tradition`, `medium`, `period`, `layer`, `dimension_id`, `claim_text`. - Release Suitability Audit: `item_id`, `source_bucket`, `pipeline_mode`, `option_a_source`, `option_b_source`, `governed_option`, `option_a_text`, `option_b_text`. - Card Faithfulness Spot Audi...