[P1.15] Crashed/killed task subprocess must be retryable (currently records terminal "RUNNING")

[frankbria]

Severity: medium | Category: data-integrity | Phase: P1.15

Problem

_execute_task_subprocess returns the active run's status even when the child crashed/was SIGTERMed before updating the row (still RUNNING), so the batch records results[task_id]="RUNNING" as terminal. resume_batch only re-runs FAILED/BLOCKED/missing, so the task is permanently skipped, and the stale RUNNING run makes the next start_task_run raise "already has an active run".

Evidence

codeframe/core/conductor.py:2156

Acceptance criteria

• On nonzero exit with the run still RUNNING, the run is reconciled to FAILED before returning.
• "RUNNING" is retryable on resume.

Dependencies

None

---

_{Filed from the SaaS launch-readiness audit. Atomic: one developer, one session. Work order: strictly P0.1 → P3.12 (no forward dependencies).}

[coderabbitai]

🔗 Related PRs

#382 - fix: return non-zero exit codes from work retry and batch run [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!