Repro Record Workflow

4. Execute subtask:

• Apply environment/config/code changes.
• For training launchers or checkpoint logic, also apply exact-training-resume-guard.
• Run minimal verification.

5. Update record immediately:

• Use scripts/update_codex_record.py.
• One entry per completed/failed subtask.
• Include blockers and next action if failed.

6. Repeat:

• Never batch many subtasks into one record entry.

Record Rules

1. Use timestamped entries (script default).
2. Include these fields:

• Task
• Status
• Summary
• Evidence
• Next

3. Keep entries short and factual.
4. Use absolute paths/job ids in Evidence.
5. If a training run is only restartable from model weights rather than exactly resumable, record that limitation explicitly instead of calling it a resume checkpoint.

Commands

Create or append entry:

python ~/.codex/skills/repro-record-workflow/scripts/update_codex_record.py \
  --record /path/to/repo/CODEX_RECORD.md \
  --task "Run smoke preflight on A100 node" \
  --status failed \
  --summary "Import failed in trainer package" \
  --evidence "Job 10087183; log: /path/gui_g2_smoke-10087183.out" \
  --next "Patch missing import and resubmit smoke test"

Create record file if missing:

cp ~/.codex/skills/repro-record-workflow/references/record-template.md /path/to/repo/CODEX_RECORD.md