From 2f583e176e118df5794b8bb34f61b0196873dad5 Mon Sep 17 00:00:00 2001
From: Hermes <hermes@nousagent.com>
Date: Mon, 13 Jul 2026 13:22:57 -0700
Subject: [PATCH] DC-038: claim for Hermes

---
 BACKLOG.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/BACKLOG.md b/BACKLOG.md
index 0c0d3ff..7cce976 100644
--- a/BACKLOG.md
+++ b/BACKLOG.md
@@ -190,8 +190,8 @@
 ## P2 — Polish & DX
 
 ### DC-038: Backup trigger.json + result.json in dashcaddy-update.sh — enable one-command rollback
-- **status:** todo
-- **owner:** unclaimed
+- **status:** in-progress
+- **owner:** hermes
 - **details:** During the DC-033 fix, recovering from the failed v1.14.4 update required manually mv'ing `trigger.json.processing` back to `trigger.json`, manually running `start.sh`, etc. — because the backup mechanism in `dashcaddy-update.sh` (lines 318-327) only backs up code + data, not the trigger/result state. Fix: in the `backup_data_dir` function (or new `backup_update_state` function), also copy `${UPDATES_DIR}/trigger.json` and `${UPDATES_DIR}/result.json` into the versioned backup directory so rollback tooling can restore them. Effort: ~15 min.
 - **impact:** Faster incident recovery. Currently takes 5-10 manual steps to roll back a failed update; would take 1.