Reconcile rebuilds interrupted before replacement creation

2026-10-08 14:24:52 -04:00
parent e01b143a09
commit c4e2ff4384
11 changed files with 571 additions and 14 deletions
@@ -415,6 +415,16 @@ Otherwise the result remains **Unknown** and holds dependent work. Running alone
 is insufficient evidence that a particular restart happened. EC neither assumes
 an unreachable server stopped nor launches a duplicate replacement elsewhere.

+An interrupted rebuild can settle as **Failed** when its last checkpoint is
+`disrupting`, Docker confirms both the old and replacement containers are absent,
+and any existing generation marker still matches the original instance. The agent removes
+only the partial replacement files, preserves the old generation's files and
+marker, and retains the original diagnostic in its failure report. It does not
+replay the interrupted rebuild. A separately queued rebuild can then proceed
+through normal eligibility checks. A later creation checkpoint, a changed
+generation, an inspection error, or failed partial-file cleanup leaves the result
+**Unknown** and keeps dependent work waiting.
+
 ### Player checks and activation

 Campaign bytes are staged and verified while players remain connected. Only